Skill-uri pentru agenți pe care le poți verifica înainte să le instalezi
Skill-uri SKILL.md publice din depozite GitHub cu peste 50 de stele și de la producători, scanate și evaluate. Instalează oricare dintre ele cu o singură comandă în Claude Code, Cursor, Codex, GitHub Copilot sau Gemini CLI.
49.105 skill-uri din 2.358 de depozite · actualizat acum 3 ore
48.055 de skill-uri
- cold-emailmohitagw15856/pm-claude-skillsWrite a cold sales/B2B outreach email that earns a reply. Use when asked to write a cold email, a sales outreach email, a prospecting email, or a cold email sequence to a business prospect. Produces a short, personalised email — subject, a relevant opener, one clear value-led ask, and a low-friction CTA — plus 2 follow-ups, written to be replied to, not deleted.ProductivitateFără avertismente★ 1,5 K↓ —
- creating-claude-rulesAgentWorkforce/relayUse when creating or fixing .claude/rules/ files - provides correct paths frontmatter (not globs), glob patterns, and avoids Cursor-specific fields like alwaysApplyPlanificareFără avertismente★ 1,1 K↓ —
- planning-with-filesOthmanAdi/planning-with-filesPersistent file-based planning for multi-step AI-agent work. Keeps task_plan.md, findings.md, and progress.md on disk; lifecycle hooks inject selected project planning context. Automatic recovery reads project planning files only. Explicit session-catchup.py --metadata reads same-project local agent session records and emits aggregate counts only; --replay may emit bounded nonce-framed excerpts. Optional gated mode can request continuation only when the host supports it and never runs commands declared in Markdown. The skill has no network upload path. Use for research or work needing 5+ tool calls.PlanificareFără avertismente★ 27,8 K↓ —
- create-user-storyhuytieu/COG-second-brainCreate user stories with duplicate checking across any project tracker (Linear, GitHub Issues, Jira)AlteleFără avertismente★ 1,3 K↓ —
- stoc-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning a STOC (ACM Symposium on Theory of Computing) project calendar — backward planning to the early-November deadline, the STOC/FOCS alternating two-deadline year that theory groups schedule around, full-version and camera-ready milestones, and the June TheoryFest endpoint.ProductivitateFără avertismente★ 1,4 K↓ —
- press-releasemohitagw15856/pm-claude-skillsWrite a professional press release for any announcement. Use when asked to write a press release, media announcement, news release, or press statement. Produces a structured press release with headline, dateline, body, boilerplate, and media contact — ready to send to journalists.RedactareFără avertismente★ 1,5 K↓ —
- deploying-to-staging-environmentAgentWorkforce/relayUse when deploying changes to staging across relay, relay-dashboard, and relay-cloud repos - coordinates multi-repo branch syncing using git worktrees, automatically triggers staging deployments via GitHub ActionsDevOpsFără avertismente★ 1,1 K↓ —
- focs-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning a FOCS (IEEE Symposium on Foundations of Computer Science) cycle end to end — working backward from the April 1 deadline, managing the live post-submission summer of the 2026 cycle, coordinating with the STOC beat, preparing the November conference, and scheduling a FOCS 2027 attempt.ProductivitateFără avertismente★ 1,4 K↓ —
- podc-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning an ACM PODC campaign end to end — running the single annual cycle backward from the February deadline through abstract registration, lightweight double-blind review, the late-April notification, the May camera-ready, and the arXiv full version — and coordinating the regular-paper-vs-Brief-Announcement decision along the way.ProductivitateFără avertismente★ 1,4 K↓ —
- icml-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning or sequencing an ICML manuscript workflow end to end - from topic selection and drafting through OpenReview submission, double-blind review, author response, camera-ready, PMLR publication, public original-submission release, and rerouting decisions. Use when you need the next ICML skill, the official page to reopen, or the blocking gap for the current stage.ProductivitateFără avertismente★ 1,4 K↓ —
- simplifyfcakyon/claude-codex-settingsThis skill should be used when the user asks to "simplify", "clean up the diff", "run simplify", "simplify the changes", "review changed code for cleanup", explicitly invokes "/simplify", or asks to "commit without simplify", "skip simplify for this commit", or "commit this but skip simplify". Reviews changed code across reuse, simplification, efficiency, and altitude, or grants an explicit one-commit bypass. Not for correctness bugs.InginerieFără avertismente★ 1,2 K↓ —
- agentlas-networkagentlas-ai/Agentlas-OSUse when the user types /agentlas-network, /agentlas network, $hephaestus-network, or /hep-network to staff a durable goal from registered Local, owner Cloud, and public Hub agents or teams.AlteleFără avertismente★ 1,6 K↓ —Apare și în 1 alt depozit
- jetson-build-sourceNVIDIA/skillsUse when you need to rebuild the BSP overlay — DT, OOT modules, or kernel — from changes under bsp_sources/. Triggers: build bsp, rebuild dtb, rebuild kernel.AlteleFără avertismente★ 3,8 K↓ —
- brooks-reviewhyhmrright/brooks-lintPR code review that surfaces decay risks, design smells, and maintainability issues with concrete Symptom → Source → Consequence → Remedy findings, drawing on twelve classic engineering books. Triggers when: user asks to review code, check a PR, shares a diff or pastes code asking "does this look right?" / "any issues here?" / "ready to merge?", or asks for feedback on a function, class, or file. Also triggers when user mentions: code smells / refactoring / clean architecture / DDD / SOLID principles / Hyrum's Law / deep modules / tactical programming / conceptual integrity / Brooks's Law / Mythical Man-Month / second system effect. Do NOT trigger for: questions about how to write code from scratch, language syntax questions, or framework/tool questions where no existing code is shared.InginerieFără avertismente★ 1,6 K↓ —
- brooks-harnesshyhmrright/brooks-lintMaintenance orchestrator for the brooks-lint plugin itself. Runs a sequential subagent pipeline — author → eval → QA → trigger-audit → release — to add or edit a skill, refresh the eval suite, keep the four manifests + all README translations + CHANGELOG + AGENTS/GEMINI in sync, audit trigger boundaries, and cut releases. Drives the five agents in .claude/agents/ (skill-author, eval-curator, consistency-qa, trigger-boundary-auditor, release-manager). Triggers when the maintainer asks to work ON brooks-lint itself: "add a new skill", "edit the brooks-debt guide", "update the eval suite", "fix the trigger descriptions", "make this change and validate it", "release brooks-lint", "bump and publish", and follow-ups: "re-run", "re-validate", "update that skill", "redo the audit", "do the X part again". Do NOT trigger for: USING the brooks-lint analysis skills on some target codebase (that's brooks-review / brooks-audit / brooks-debt / brooks-test / brooks-health / brooks-sweep); generic questions about brooks-lint TestareFără avertismente★ 1,6 K↓ —
- cell-rebuttalbrycewang-stanford/Awesome-Journal-SkillsUse after Cell reviews arrive to triage the decision, prioritize the (often substantial) new experiments by impact × feasibility, and draft a point-by-point response that is respectful, evidence-led, and closes the "completeness" gaps reviewers demand. Do not run before the experiments and revision are actually done.AlteleFără avertismente★ 1,4 K↓ —
- ecai-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when designing or auditing the evidence in an ECAI paper — choosing proof versus experiment by claim shape across ECAI's breadth (theory/KR, planning/search, ML, multi-agent, applied), fair baselines, seeds and spread, honest ablations, and provenance, all supporting a claim inside a 7-page body.ȘtiințăFără avertismente★ 1,4 K↓ —
- reviewhashgraph-online/awesome-codex-pluginsUse before merge, after subagents, or for spec/plan review.InginerieFără avertismente★ 1,5 K↓ —
- agentlas-networkagentlas-ai/Agentlas-OSUse when the user types /agentlas-network, /agentlas network, $hephaestus-network, or /hep-network to staff a durable goal from registered Local, owner Cloud, and public Hub agents or teams.AlteleFără avertismente★ 1,6 K↓ —
- requesting-code-reviewActualizatGanyuanRan/AegisUse when requesting independent code review, after implementation slices, before merging high-risk work, or when verification exposes evidence, baseline, architecture, compatibility, or retirement uncertainty.InginerieFără avertismente★ 1,4 K↓ —
- goal-testundefined-ui/second-brain-osTurn a vague task into a testable definition of done and generate an executable goal-test script for it, optionally with a bounded retry loop around a headless agent. Use when the user wants to run an agent in a loop, asks how to know when an agent task is finished, or says a goal like "improve X" needs to become checkable. Do NOT use for building eval suites over many cases — that is evals-bootstrap.TestareFără avertismente★ 1,2 K↓ —
- analyze-variantsmicrosoft/power-platform-skillsUse when investigating common or slow variants, repeated work, unusual paths, or a specific Process Mining case.FinanțeFără avertismente★ 1,1 K↓ —
- code-review-assistantalibaba/skill-upTriggered when the user submits code or requests a code review. Automatically analyzes code quality, identifies potential bugs, security vulnerabilities, and performance issues, and provides improvement suggestions. Trigger phrases include "take a look at this code", "review this", "is there a problem with this function".InginerieFără avertismente★ 1,4 K↓ —
- lancet-fitbrycewang-stanford/Awesome-Journal-SkillsUse when scoping a project and before any writing, to stress-test whether a study clears The Lancet's bar — clinically or public-health important, globally relevant, and likely to change practice or policy, often with an equity lens. Decides The Lancet vs a Lancet family title vs another general medical journal.TestareFără avertismente★ 1,4 K↓ —
fedramp
Sushegaad/Claude-Skills-Governance-Risk-and-Compliance
SecuritateActualizat 10 oct. 2026
De la autor
Expert guidance for FedRAMP certification and compliance under CR26 (FedRAMP Consolidated Rules for 2026). Use this skill whenever a user asks about FedRAMP authorization, ATO (Authority to Operate), cloud security for federal government, NIST SP 800-53 controls, CSP compliance, or any of the core FedRAMP document types: SSP, SAP, SAR, POA&M, CIS/CRM workbooks. Also trigger for questions about FedRAMP Certification Classes (A, B, C, D — new baseline labels: A = pilot/transitional, B = LI-SaaS/Low, C = Moderate, D = High, per NTC-0004), FedRAMP 20x (now the primary authorization pathway), OSCAL mandate (September 2026), 3PAO assessments, continuous monitoring (ConMon), gap assessments, system boundary definition, or architecture reviews for federal cloud. FedRAMP Ready retired July 28, 2026 (Legacy FedRAMP Ready). When in doubt, use this skill — it covers the full FedRAMP lifecycle from readiness through continuous monitoring.
Instalare
npx skills add Sushegaad/Claude-Skills-Governance-Risk-and-Compliance --skill fedramp -a claude-code
Se instalează în .claude/skills/fedramp/ · Fiecare comandă descarcă skill-ul direct de pe GitHub cu utilitarul open source skills.
Descarcă .zip
Identic octet cu octet cu commit-ul scanat, cu licența depozitului și un fișier SOURCE.txt.
La ce are acces
Doar instrucțiuniNu am văzut acces la rețeaLicență: MIT
Verificări de siguranță pe SKILL.md
Niciun avertisment.
De ce 88
Securitate100
Proveniență76
Întreținere100
Licență100
Adopție49
Fișiere (7)
- SKILL.md
- references/appendices-guide.md
- references/control-families.md
- references/poam-guide.md
- references/readiness-checklist.md
- references/sap-sar-guide.md
- references/ssp-guide.md