Agent skills you can check before you install
Public SKILL.md skills from GitHub repositories with 50+ stars and from the vendors themselves, scanned and scored. Install any of them with one command in Claude Code, Cursor, Codex, GitHub Copilot or Gemini CLI.
43,705 skills from 2,070 repositories · updated 5 minutes ago
42,997 skills
- hermes-ephemeral-delegationGentleman-Programming/gentle-aiTrigger: a mapping need, parallel units, context backstop, high-risk verify, fresh review, or multi-step debug. Delegate via delegate_task for a named reason.EngineeringNo warnings★ 8K↓ —
- work-unit-commitsGentleman-Programming/gentle-aiPlan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.TestingNo warnings★ 8K↓ —
- skill-improverGentleman-Programming/gentle-aiTrigger: improve skills, audit skills, refactor skills, skill quality. Audit and upgrade existing LLM-first skills.EngineeringNo warnings★ 8K↓ —
- issue-creationGentleman-Programming/gentle-aiTrigger: issue creation, bug reports, feature requests, or issue approval. Create and triage GitHub issues from repository evidence.OtherNo warnings★ 8K↓ —
- chinese-code-reviewjnMetaCode/superpowers-zh中文 review 沟通参考——话术模板、分级标注(必须修复/建议修改/仅供参考)、国内团队常见反模式应对。仅在用户显式 /chinese-code-review 时调用,不要根据上下文自动触发。EngineeringNo warnings★ 8.4K↓ —
- skill-creatorGentleman-Programming/gentle-aiTrigger: new skills, agent instructions, documenting AI usage patterns. Create LLM-first skills with valid frontmatter.OtherNo warnings★ 8K↓ —
- judgment-dayGentleman-Programming/gentle-aiTrigger: judgment day, dual review, adversarial review, juzgar. Run explicit blind dual review with at most two scoped fix/re-judgment rounds.EngineeringNo warnings★ 8K↓ —
- go-testingGentleman-Programming/gentle-aiTrigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.TestingNo warnings★ 8K↓ —
- chained-prGentleman-Programming/gentle-aiTrigger: PRs over 400 lines, stacked PRs, review slices. Split oversized changes into chained PRs that protect review focus.EngineeringNo warnings★ 8K↓ —
- gentle-ai-collab-perfectGentleman-Programming/gentle-aiTrigger: contributing to Gentleman-Programming/gentle-ai as an external collaborator. Strict issue-first workflow, honest PR bodies, contributor-vs-maintainer scope, chained-PR strategy, verification protocol, docstring coverage. Load whenever the active repo is Gentleman-Programming/gentle-ai and any part of the contribution flow is in scope: opening an issue, drafting or editing a PR body, splitting a change into chained/stacked PRs, or auditing a PR before requesting review.WritingNo warnings★ 8K↓ —
- cognitive-doc-designGentleman-Programming/gentle-aiDesign docs that reduce cognitive load. Trigger: writing guides, READMEs, RFCs, onboarding, architecture, or review-facing docs.DesignNo warnings★ 8K↓ —Also in 1 other repo
- debugnanocoai/nanoclawDebug container agent issues. Use when things aren't working, container fails, authentication problems, or to understand how the container system works. Covers logs, session DBs, mounts, and common issues.EngineeringNo warnings★ 31K↓ —
- gentle-ai-benchGentleman-Programming/gentle-aiTrigger: bench, journey, journeys, driven mode, gentle-ai-bench, journey corpus, j-numbers, bench axis. Author and verify gentle-ai bench journeys; go test ./bench never proves driven execution.TestingNo warnings★ 8K↓ —Also in 1 other repo
- work-unit-commitsGentleman-Programming/gentle-aiPlan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.TestingNo warnings★ 8K↓ —
- issue-root-resolutionGentleman-Programming/gentle-aiTrigger: root audit, atacar la raíz, issue roots, backlog roots, mechanism map, deletion-driven fix, resolver issues de raíz, close outdated issues. Audit and resolve issue clusters by verified root cause.OtherNo warnings★ 8K↓ —
- agent-operated-workflowsmvschwarz/openrigUse when a bounded real-world procedure has a deterministic happy path but brownfield, variable, or partially knowable state; when an operation must resume from verified evidence; or when deciding whether agent judgment or ordinary code should own a procedure's control loop.EngineeringNo warnings★ 8.1K↓ —
- agent-operated-softwaremvschwarz/openrigUse when designing, building, operating, or diagnosing an ongoing application whose live backend or control loop includes OpenRig agents, including applications with a Markdown, YAML, or JSON agent control plane or a thin surface over specialist agent roles.PlanningNo warnings★ 8.1K↓ —
- vault-usermvschwarz/openrigUse when checking the health of this rig's HashiCorp Vault or writing, reading, listing, deleting or explaining its secrets.WritingNo warnings★ 8.1K↓ —
- software-for-agentsmvschwarz/openrigUse when older OpenRig instructions name software-for-agents or describe agent-in-the-middle or studio software under the former skill name.OtherNo warnings★ 8.1K↓ —
- mission-slice-sopmvschwarz/openrigUse when starting, building, handing off, restoring, or closing a mission or slice under the default lightweight SDLC.OtherNo warnings★ 8.1K↓ —
- delegating-workmvschwarz/openrigUse when you have a task and must decide WHO does it — yourself, a spawned subagent, or another agent in the topology that already holds the context — or how to brief the agent you hand it to, which depends on the model it runs. The rule: how much would a blank slate have to read in to do this correctly? A lot → route to a context-holding agent; a little → subagent; unsure → a real agent or yourself. NOT the mechanics of fanning out (that's dispatching-parallel-agents / subagent-driven-development) — this is the who/whether decision, and the failure mode that makes teams abandon subagents.ProductivityNo warnings★ 8.1K↓ —
- sred-work-summarygetsentry/skillsGo back through the previous year of work and create a Notion doc that groups relevant links into projects that can then be documented as SRED projects.OfficialProductivityNo warnings★ 1.1K↓ —
- queue-handoffmvschwarz/openrigUse when ending a turn, finishing a slice, blocked on another agent's work, or escalating to a human — durable work handoff via queue items so the system keeps moving across compactions, missed messages, and interruptions. Covers the hot-potato terminal-turn-rule (active work ends by passing the ball, not by going idle), default-nudge semantics, and when `--no-nudge` is appropriate for intentional cold park or human gate.OtherNo warnings★ 8.1K↓ —
- oversight-teammvschwarz/openrigUse when you are a seat on the oversight pod (a standing monitor-mode rig that keeps OTHER rigs healthy), configuring or running the drift detectors, or choosing whether to intervene vs escalate. Covers the pull-not-poll posture, the v0 detectors (premature-park, process-drift, off-task, token-burn), the intervention ladder (orchestrator-ping -> refocus -> human escalation), and the cheap+deep model economics. NOT for orchestrating your OWN rig (orchestration-team) and NOT the intervention primitive mechanics (watchdog).ProductivityNo warnings★ 8.1K↓ —Also in 1 other repo
offensive-reporting
SnailSploit/Claude-Red
From the author
Penetration test and red team report writing methodology. Covers executive summary structuring (risk-led narrative for non-technical readers), technical finding format (title, severity, affected scope, narrative, reproduction steps, impact, remediation, references), CVSS v3.1 / v4.0 scoring with vector justification, OWASP risk rating, evidence hygiene (redacting credentials, hashing client data, time-stamping every action), screenshot and PoC artifact management, finding chain narratives, scope/limitations/assumptions documentation, retest evidence and remediation tracking, deliverable formats (PDF, DOCX, HTML, JSON for SIEM ingestion), client-customer-deliverable separation, and common report mistakes (over-CVSSing, undermining the triager, missing the 'so what'). Use at the end of an engagement when authoring a deliverable, when restructuring a draft for executive readability, or when establishing a reusable report template for a consulting practice.
Install
npx skills add SnailSploit/Claude-Red --skill offensive-reporting -a claude-code
Installs to .claude/skills/offensive-reporting/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
What it can touch
Safety checks on SKILL.md
No warnings.
Why 92
Files (1)
- SKILL.md