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.
48,622 skills from 2,355 repositories · updated 12 hours ago
48,622 skills
- fathom-hello-worldjeremylongshore/tons-of-skills-marketplaceRetrieve meeting transcripts and summaries from the Fathom API. Use when fetching meeting data, testing API access, or learning Fathom API response structure. Trigger with phrases like "fathom hello world", "fathom first api call", "get fathom transcript", "fathom meeting data".TestingNo warnings★ 2.9K↓ —
- observeplugin87/ux-ui-agent-skillsShow whether the agent followed the kit's rules in recent sessions: pages edited and measured, Stop hook blocks, findings left open. Reads local hook events only.WritingNo warnings★ 3.1K↓ —
- golang-how-tosamber/cc-skills-golangGolang skills orchestrator — always active on any Golang coding, review, debug, or setup task. Reads the task context and loads the most relevant skills from samber/cc-skills-golang, often multiple at once: writing a gRPC service loads golang-grpc + golang-testing + golang-error-handling; debugging a panic loads golang-troubleshooting + golang-safety; auditing security loads golang-security + golang-lint + golang-safety. Also: disambiguates competing clusters when two skills seem to overlap (performance vs benchmark vs troubleshooting, samber/lo vs mo vs ro, DI cluster, safety vs security), and configures the project's agent-config file (CLAUDE.md, AGENTS.md, GEMINI.md, Cursor rules, or Copilot instructions) to force-trigger skills in a project (/golang-how-to configure).SecurityNo warnings★ 3.7K↓ —
- golang-uber-fxsamber/cc-skills-golangGolang application framework using uber-go/fx — fx.New, fx.Provide, fx.Invoke, fx.Module, fx.Lifecycle hooks, fx.Annotate (name/group/As), fx.Decorate, fx.Supply, fx.Replace, fx.WithLogger, and signal-aware Run(). Apply when using or adopting uber-go/fx, when the codebase imports `go.uber.org/fx`, or when wiring services with fx.New. For raw DI without lifecycle, see `samber/cc-skills-golang@golang-uber-dig` skill.OtherNo warnings★ 3.7K↓ —
- golang-pkg-go-devsamber/cc-skills-golangGolang package and module lookup via `godig`, a pkg.go.dev API client (CLI + MCP server). Use for any Go/Golang library's documentation, API signatures, symbols, usage examples, which versions exist, licenses, whether a dependency has CVEs, or who imports a package — prefer this over Context7 for any Go package or module. Read-only, no auth. Not for upgrading dependencies (→ See `samber/cc-skills-golang@golang-dependency-management` skill), choosing a library (→ See `samber/cc-skills-golang@golang-popular-libraries` skill), or local symbols and an already-used dependency's resolved source, call sites, and generic instantiations (→ See `samber/cc-skills-golang@golang-gopls` skill).EngineeringNo warnings★ 3.7K↓ —
- design-componentplugin87/ux-ui-agent-skillsDesign a UI component spec to the house quality bar (anatomy, variants, sizes, the 8 states, token mapping, and accessibility). Use when the user wants to design or document a component (button, input, tabs, toast, combobox, date picker, modal, etc.) at the spec level before or alongside code. For generating framework code, use design-code.DesignNo warnings★ 3.1K↓ —
- golang-namingsamber/cc-skills-golangGo (Golang) naming conventions — covers packages, constructors, structs, interfaces, constants, enums, errors, booleans, receivers, getters/setters, functional options, acronyms, test functions, and subtest names. Use this skill when writing new Go code, reviewing or refactoring, choosing between naming alternatives (New vs NewTypeName, isConnected vs connected, ErrNotFound vs NotFoundError, StatusReady vs StatusUnknown at iota 0), debating Go package names (utils/helpers anti-patterns), or asking about Go naming best practices. Also trigger when the user mentions MixedCaps vs snake_case, ALL_CAPS constants, Get-prefix on getters, or error string casing. Do NOT use for general Go implementation questions that don't involve naming decisions.TestingNo warnings★ 3.7K↓ —
- 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.7K↓ —
- principle-subtract-before-you-addmichael-denyer/pstack-claudeApply when sequencing an addition, refactor, or rewrite. Remove dead code, redundant validators, and stub references first, then build on the simpler base.EngineeringNo warnings★ 3.7K↓ —
- principle-never-block-on-the-humanmichael-denyer/pstack-claudeApply when tempted to ask 'should I do X?' on reversible work.OtherNo warnings★ 3.7K↓ —
- reproduce-regressiontrailofbits/skillsUse when deploying before/after systems and building a live-system PoC for a regression candidate.DevOpsNo warnings★ 7.9K↓ —
- glass-shard-titleheygen-com/hyperframesGlass shards fly in through fog and tile themselves into the headline. HyperFrames block, 1920×1080, 12.16s, 19 variables.OfficialOtherNo warnings★ 76.9K↓ —
- principle-encode-lessons-in-structuremichael-denyer/pstack-claudeApply when you catch yourself writing the same instruction a second time, or notice a recurring correction. Encode the rule as a lint, metadata flag, runtime check, or script instead of more text.WritingNo warnings★ 3.7K↓ —
- principle-foundational-thinkingmichael-denyer/pstack-claudeApply before writing logic: choosing core types and data structures, sequencing scaffold-vs-feature work, asking what concurrent actors share. Get the data structures right so downstream code becomes obvious.WritingNo warnings★ 3.7K↓ —
- principle-migrate-callers-then-delete-legacy-apismichael-denyer/pstack-claudeApply when introducing a new internal API while old callers still exist. Migrate callers and delete the old API in the same wave instead of preserving compatibility layers.EngineeringNo warnings★ 3.7K↓ —
- principle-explain-the-numbermichael-denyer/pstack-claudeApply before you measure, and before you trust, report, or act on a number you measured: a speedup, a regression, a throughput, a latency, or an eval result. Find what limits it, and rule out that it measured something other than the work you think.OtherNo warnings★ 3.7K↓ —
- principle-type-system-disciplinemichael-denyer/pstack-claudeApply when designing types, reviewing a function signature, or writing code in any statically-typed language. Make illegal states unrepresentable, brand semantic primitives, parse external data at boundaries, exhaust variants, derive from authoritative schemas.WritingNo warnings★ 3.7K↓ —
- gsd:profile-userdavepoon/buildwithclaudeGenerate developer behavioral profile and create Claude-discoverable artifactsOtherNo warnings★ 3.7K↓ —
- audit-augmentationtrailofbits/skillsAugments Trailmark code graphs with external audit findings from SARIF static analysis results, weAudit annotation files, and version-gated Trailmark 0.4.x binary-analysis graph exports. Maps findings to graph nodes by file and line overlap, creates severity-based subgraphs, and enables cross-referencing findings with pre-analysis data (blast radius, taint, etc.). Use when projecting SARIF results onto a code graph, overlaying weAudit annotations, importing binary graph findings, cross-referencing Semgrep, CodeQL, or binary-analysis findings with call graph data, or visualizing audit findings in the context of code structure.EngineeringNo warnings★ 7.9K↓ —
- hunt-regressionstrailofbits/skillsUse when discovering possible regressions from a pinned change and its callers before reproduction.OtherNo warnings★ 7.9K↓ —
- doca-argusNVIDIA/skillsUse this skill when the user is deploying or operating the DOCA Argus Service — the packaged BlueField-side runtime-security container that watches the BlueField and attached host for suspicious activity, integrity violations, and operational anomalies, and forwards findings to a SIEM (Splunk / ELK / Sentinel / syslog). Covers the four-axis config (detection policy, forwarding, sampling, host coverage), running the NGC container on BlueField Arm, and wiring the forwarder. Trigger even without "DOCA Argus" by name — typical implicit phrasings: "container green but no findings arrive", "false-positive flood in Splunk", or "runtime security on a fleet of BlueField-3s". Refuse and route elsewhere for installing DOCA, SIEM-side ingest stanzas, pre-baked detection-rule packs, and metrics observability (DOCA Telemetry). Argus is NVIDIA's currently- promoted runtime-security framework, superseding the older App Shield library; name it first for new runtime-security work.SecurityNo warnings★ 3.8K↓ —
- mutation-testingtrailofbits/skillsConfigures mewt or muton campaigns, analyzes surviving mutants, and investigates bugs exposed by testing gaps. Use when setting up mutation testing, reviewing campaign results, identifying equivalent mutants, or finding bugs from surviving mutations.TestingNo warnings★ 7.9K↓ —
- principle-separate-before-serializing-shared-statemichael-denyer/pstack-claudeApply when concurrent actors might write to the same file, branch, key, or state object. Eliminate the sharing first; serialize structurally only when one shared writer is a real invariant.WritingNo warnings★ 3.7K↓ —
- apify-cost-tuningjeremylongshore/tons-of-skills-marketplaceOptimize Apify platform costs through memory tuning, compute unit management, and proxy budgeting. Use when analyzing Apify billing, reducing Actor run costs, or implementing usage monitoring and budget alerts. Trigger with "apify cost", "apify billing", "reduce apify costs", "apify pricing", "apify expensive", "apify budget", "compute units".ProductivityNo warnings★ 2.9K↓ —
cosmos-vulnerability-scanner
trailofbits/skills
SecurityUpdated 4 days ago
From the author
Scans Cosmos SDK blockchain modules and CosmWasm contracts for consensus-critical vulnerabilities — chain halts, fund loss, state divergence. 25 core + 16 IBC + 10 EVM + 3 CosmWasm patterns. Use when auditing custom x/ modules, reviewing IBC integrations, or assessing pre-launch chain security. Updated for SDK v0.53.x.
Install
npx skills add trailofbits/skills --skill cosmos-vulnerability-scanner -a claude-code
Installs to .claude/skills/cosmos-vulnerability-scanner/ · Each command fetches the skill straight from GitHub with the open skills CLI.
No download: this skill’s licence (CC-BY-SA-4.0) does not let us redistribute its files. The install commands fetch them from GitHub instead.
What it can touch
Instructions onlyNo network use seenLicence: CC-BY-SA-4.0
Safety checks on SKILL.md
No warnings.
Why 90
Security100
Provenance87
Maintenance100
Licence80
Adoption61
Files (11)
- CHANGELOG.md
- SKILL.md
- agents/openai.yaml
- assets/trail-of-bits-mark.svg
- resources/ADVANCED_VULNERABILITY_PATTERNS.md
- resources/COSMWASM_VULNERABILITY_PATTERNS.md
- resources/DISCOVERY.md
- resources/EVM_VULNERABILITY_PATTERNS.md
- resources/IBC_VULNERABILITY_PATTERNS.md
- resources/STATE_VULNERABILITY_PATTERNS.md
- resources/VULNERABILITY_PATTERNS.md