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.
8,489 skills from 242 repositories · updated 3 minutes ago
517 skills
- gsd:graphifydavepoon/buildwithclaudeBuild, query, and inspect the project knowledge graph in .planning/graphs/PlanningNo warnings★ 3.7K↓ —
- gsd:add-phasedavepoon/buildwithclaudeAdd phase to end of current milestone in roadmapPlanningNo warnings★ 3.7K↓ —
- gsd:from-gsd2davepoon/buildwithclaudeImport a GSD-2 (.gsd/) project back to GSD v1 (.planning/) formatPlanningNo warnings★ 3.7K↓ —
- gsd:mvp-phasedavepoon/buildwithclaudePlan an MVP-mode phase — captures an "As a / I want to / So that" user story, runs SPIDR splitting, then delegates to plan-phasePlanningNo warnings★ 3.7K↓ —
- gsd:pr-branchdavepoon/buildwithclaudeCreate a clean PR branch by filtering out .planning/ commits — ready for code reviewPlanningNo warnings★ 3.7K↓ —
- gsd:autonomousdavepoon/buildwithclaudeRun all remaining phases autonomously — discuss→plan→execute per phasePlanningNo warnings★ 3.7K↓ —
- gsd:plan-phasedavepoon/buildwithclaudeCreate detailed phase plan (PLAN.md) with verification loopPlanningNo warnings★ 3.7K↓ —
- gsd:plant-seeddavepoon/buildwithclaudeCapture a forward-looking idea with trigger conditions — surfaces automatically at the right milestonePlanningNo warnings★ 3.7K↓ —
- gsd:spec-phasedavepoon/buildwithclaudeSocratic spec refinement — clarify WHAT a phase delivers with ambiguity scoring before discuss-phase. Produces a SPEC.md with falsifiable requirements locked before implementation decisions begin.PlanningNo warnings★ 3.7K↓ —
- gsd:ingest-docsdavepoon/buildwithclaudeScan a repo for mixed ADRs, PRDs, SPECs, and DOCs and bootstrap or merge the full .planning/ setup from them. Classifies each doc in parallel, synthesizes a consolidated context with a conflicts report, and routes to new-project or merge-milestone depending on whether .planning/ already exists.PlanningNo warnings★ 3.7K↓ —
- gsd:map-codebasedavepoon/buildwithclaudeAnalyze codebase with parallel mapper agents to produce .planning/codebase/ documentsPlanningNo warnings★ 3.7K↓ —
- gsd:remove-phasedavepoon/buildwithclaudeRemove a future phase from roadmap and renumber subsequent phasesPlanningNo warnings★ 3.7K↓ —
- tycanadavepoon/buildwithclaudePersistent task management and productivity intelligence via MCP. Captures tasks from conversation, plans your day, tracks patterns, and gives personalized recommendations that improve over time.PlanningNo warnings★ 3.7K↓ —
- gsd:execute-phasedavepoon/buildwithclaudeExecute all plans in a phase with wave-based parallelizationPlanningNo warnings★ 3.7K↓ —
- gsd:new-milestonedavepoon/buildwithclaudeStart a new milestone cycle — update PROJECT.md and route to requirementsPlanningNo warnings★ 3.7K↓ —
- gsd:new-workspacedavepoon/buildwithclaudeCreate an isolated workspace with repo copies and independent .planning/PlanningNo warnings★ 3.7K↓ —
- architecturedavepoon/buildwithclaudeArchitecture design skill with ADR records, system design checklists, scalability assessment, and architecture patternsPlanningNo warnings★ 3.7K↓ —
- golang-samber-rosamber/cc-skills-golangReactive streams and event-driven programming in Golang using samber/ro — ReactiveX implementation with 150+ type-safe operators, cold/hot observables, 5 subject types (Publish, Behavior, Replay, Async, Unicast), declarative pipelines via Pipe, 40+ plugins (HTTP, cron, fsnotify, JSON, logging), automatic backpressure, error propagation, and Go context integration. Apply when using or adopting samber/ro, when the codebase imports github.com/samber/ro, or when building asynchronous event-driven pipelines, real-time data processing, streams, or reactive architectures in Go. Not for finite slice transforms (→ See `samber/cc-skills-golang@golang-samber-lo` skill).PlanningNo warnings★ 3.5K↓ —
- golang-error-handlingsamber/cc-skills-golangIdiomatic Golang error handling — creation, wrapping with %w, errors.Is/As, errors.Join, custom error types, sentinel errors, panic/recover, the single handling rule, structured logging with slog, HTTP request logging middleware, and samber/oops for production errors. Built to make logs usable at scale with log aggregation 3rd-party tools. Apply when creating, wrapping, inspecting, or logging errors in Go code. For samber/oops specifics → See `samber/cc-skills-golang@golang-samber-oops` skill; for slog handler ecosystem → See `samber/cc-skills-golang@golang-samber-slog` skill.PlanningNo warnings★ 3.5K↓ —
- golang-dependency-injectionsamber/cc-skills-golangComprehensive guide for dependency injection (DI) in Golang. Covers why DI matters (testability, loose coupling, separation of concerns, lifecycle management), manual constructor injection, and DI library comparison (google/wire, uber-go/dig, uber-go/fx, samber/do). Use this skill when designing service architecture, setting up dependency injection, refactoring tightly coupled code, managing singletons or service factories, or when the user asks about inversion of control, service containers, or wiring dependencies in Go. For a specific DI library, → See `samber/cc-skills-golang@golang-google-wire`, `samber/cc-skills-golang@golang-uber-dig`, `samber/cc-skills-golang@golang-uber-fx`, or `samber/cc-skills-golang@golang-samber-do` skills.PlanningNo warnings★ 3.5K↓ —
- solve-challengeljagiello/ctf-skillsSolves CTF challenges by performing first-pass triage, identifying the dominant category, and routing execution to the right specialized ctf-* skill. Use when the user gives you a challenge bundle, a remote service, a suspicious file, or only a vague challenge description and you must determine where to start. Do not use it when the category is already clear and a specialized skill can be invoked directly; this is the dispatcher and recon entrypoint, not the deepest reference for category-specific techniques.PlanningNo warnings★ 3.5K↓ —
- howmichael-denyer/pstack-claudeUse for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions ("where should this live", "which package owns this", "is this the right layer"). Explains subsystem architecture, runtime flow, onboarding mental models. Use why for motivation.PlanningNo warnings★ 3.2K↓ —
- sharpenmichael-denyer/pstack-claudeSharpen a task before starting: the expert approach, what the user is really after, and the right level of specification. Use for /sharpen.PlanningNo warnings★ 3.2K↓ —
- architectmichael-denyer/pstack-claudeSketch types, signatures, and module structure before code, then stay in the loop while implementation fills in. Use for /architect, 'architect this', 'design this', or non-trivial work where jumping to code would lock in the wrong shape.PlanningNo warnings★ 3.2K↓ —