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 17 hours ago
48,622 skills
- babysitmichael-denyer/pstack-claudeWatch an open PR — fix failing CI, handle the straightforward review comments, and drive it to a mergeable state. Claude Code analog of Cursor's built-in /babysit. Use after opening a PR when the user wants the agent to shepherd it without re-prompting.EngineeringNo warnings★ 3.7K↓ —
- adjudicate-regressiontrailofbits/skillsUse when deciding whether source and live reproduction evidence establish a new regression or an exclusion.OtherNo warnings★ 7.9K↓ —
- golang-troubleshootingsamber/cc-skills-golangTroubleshoot Golang programs systematically - find and fix the root cause. Use when encountering bugs, crashes, deadlocks, races, or unexpected behavior in Go code. Covers debugging methodology, common Go pitfalls, test-driven debugging, pprof setup and capture, Delve, race detection, GODEBUG tracing, and production debugging. Start here for any 'something is wrong' situation. Not for interpreting profiles or benchmarking (→ See `samber/cc-skills-golang@golang-benchmark` skill), applying optimization patterns (→ See `samber/cc-skills-golang@golang-performance` skill), or designing new code (→ See `samber/cc-skills-golang@golang-safety` skill for defensive coding, `samber/cc-skills-golang@golang-concurrency` skill for concurrency design).TestingNo warnings★ 3.7K↓ —
- verification-before-completionforyourhealth111-pixel/Vibe-SkillsCompletion-evidence route used before claiming work is complete, fixed, passing, committed, or PR-ready. Requires fresh verification output before success claims. Do not use for root-cause debugging, TDD implementation, test-report packaging, or review-feedback triage.TestingNo warnings★ 3.8K↓ —
- social-calendar-builderaaron-he-zhu/aaron-marketing-skillsUse when the user asks to "build our social posting calendar", "set weekly slots and queue depth per channel", or "plan the evergreen recycle rotation"; produces the always-on brand calendar — pillar allocation with hero/hub/help balance and give:ask targets (all labeled Estimated starting heuristics to calibrate against own analytics, never scored rules), per-channel recurring slots with queue depth, a batching workflow, an evergreen recycle cycle with freshness re-checks, deliberate open slots for realtime/trend moments fed by trend-spotter go/skip verdicts, and first-comment/publish-order ops — cadence commitments filed to the channel registry, and no batch ships to the queue without a SHIP verdict from social-quality-auditor pre-publish mode. Not for repurposing an existing asset or the paid-amplification calendar — use content-amplifier. 社媒排期/内容日历/栏目配比/常青循环复用ProductivityNo warnings★ 3K↓ —
- tiledbvcfforyourhealth111-pixel/Vibe-SkillsEfficient storage and retrieval of genomic variant data using TileDB. Scalable VCF/BCF ingestion, incremental sample addition, compressed storage, parallel queries, and export capabilities for population genomics.ScienceNo warnings★ 3.8K↓ —Also in 1 other repo
- tdd-guideforyourhealth111-pixel/Vibe-SkillsTest-first development route for TDD, writing failing tests first, RED -> GREEN -> REFACTOR, and behavior-changing feature/bug/refactor work. Do not use for already-failing test root-cause debugging, test-report packaging, or final completion evidence.TestingNo warnings★ 3.8K↓ —
- strategic-narrative-designeraaron-he-zhu/aaron-marketing-skillsUse when the user asks to "design our change narrative", "build the old-world-to-new-game story arc", or "frame the shift our category is undergoing"; produces a Raskin-style strategic narrative arc — old world → the undeniable shift → winners vs losers under the new rules → the promised land → proof the promised land is real — derived from the positioning truth set and the belief/objection map, feeding the TALE Architecture arc sub-item. Every proof beat is labeled Measured / User-provided / [needs source] and this skill never adjudicates a claim. Not for the message house hierarchy — use message-system-architect; not for the pitch deck narrative — use pitch-narrative-builder; not for claim substantiation — use offer-claims-registry. 变革叙事弧/旧世界/应许之地/战略叙事结构DocumentsNo warnings★ 3K↓ —
- provider-ephemeral-resourceshashicorp/agent-skillsImplement Terraform provider ephemeral resources with the Plugin Framework: the Open/Renew/Close lifecycle, ephemeral schema design, registration via EphemeralResources, renewal for expiring credentials, and how ephemeral values flow into write-only attributes and provider configuration. Use when adding an ephemeral resource, exposing secrets/tokens/certificates that must never persist in state or plan, deciding between an ephemeral resource and a data source, or wiring short-lived credentials from one provider into another.OfficialDevOpsNo warnings★ 911↓ —
- chrome-mcp-troubleshootingtrailofbits/skillsDiagnose and fix Claude in Chrome MCP extension connectivity issues. Use when mcp__claude-in-chrome__* tools fail, return "Browser extension is not connected", or behave erratically.BrowserNo warnings★ 7.9K↓ —
- schema-markup-generatornowork-studio/notfair-pluginGenerate JSON-LD structured data markup for rich results in Google Search. Supports FAQ, HowTo, Article, Product, LocalBusiness, and multi-type schemas. Validates against Google requirements and provides implementation guidance. Use when asked to "add schema markup", "generate structured data", "JSON-LD", "rich snippets", "FAQ schema", "product markup", "add structured data to my page", "how to get rich snippets", or any structured data task.WritingNo warnings★ 4.1K↓ —
- typescript-best-practicesmichael-denyer/pstack-claudeTypeScript best practices. Use when reading or editing any .ts or .tsx file.EngineeringNo warnings★ 3.7K↓ —
- docs-writeforyourhealth111-pixel/Vibe-SkillsWrite documentation following Metabase's conversational, clear, and user-focused style. Use when creating or editing documentation files (markdown, MDX, etc.).WritingNo warnings★ 3.8K↓ —Also in 1 other repo
- sales-enablement-kitaaron-he-zhu/aaron-marketing-skillsUse when the user asks to "build battle cards", "prep the sales team for launch", or "write the internal launch FAQ"; produces the internal enablement kit for a sales-led launch — battle cards vs each named alternative (where we win / where they win / trap questions, every fact traceable), a sales talk track derived from the PR-FAQ spine, an objection-handling table (objection → response → evidence), internal FAQ + CS macros, and an internal launch announcement with embargo discipline. Not for the external message house — use message-house-builder; not for competitor tracking itself — use competitor-tracker or competitor-analysis; not for outbound sequences — use cold-outbound-sequencer. 销售赋能/battle card/销售叙事/异议处理/内部FAQWritingNo warnings★ 3K↓ —
- principle-prove-it-worksmichael-denyer/pstack-claudeApply after completing a task, before declaring done. Verify against the real artifact (run the feature, read the actual value, inspect the diff), not a proxy, self-report, or 'it compiles.'ProductivityNo warnings★ 3.7K↓ —
- gsd:plan-phasedavepoon/buildwithclaudeCreate detailed phase plan (PLAN.md) with verification loopPlanningNo warnings★ 3.7K↓ —
- paid-ads-optimizenowork-studio/notfair-pluginDiagnose wasted paid-ad spend, pacing, and allocation, then propose safe evidence-backed optimizations. Use for waste, negatives, budgets, bid changes, poor CPA or ROAS, underpacing, overspend, or scaling decisions.MarketingNo warnings★ 4.1K↓ —
- navan-sdk-patternsjeremylongshore/tons-of-skills-marketplaceDesign an application-owned Navan adapter pinned to the tenant's actual integration contract. Use when wrapping Booking API, Expense API, SFTP, or direct integration behavior. Trigger with "build a Navan client", "wrap Navan API", or "type Navan responses".DesignNo warnings★ 2.9K↓ —
- variant-analysistrailofbits/skillsHunts for the other instances of a bug already found — the variants of one root cause across a codebase. Use immediately after a vulnerability, logic bug, or bad pattern turns up in a specific file and the question becomes where else it occurs, including the bare conversational form ("are there others like this?", "is this the same bug?"). Also for generalizing one known instance into a CodeQL or Semgrep query for its whole pattern family, and for triaging a set of look-alike candidates against a known root cause. Not for initial discovery with no bug in hand.SecurityNo warnings★ 7.9K↓ —
- reproduce-regressiontrailofbits/skillsUse when deploying before/after systems and building a live-system PoC for a regression candidate.DevOpsNo warnings★ 7.9K↓ —
- hunt-regressionstrailofbits/skillsUse when discovering possible regressions from a pinned change and its callers before reproduction.OtherNo warnings★ 7.9K↓ —
- cudaq-guideNVIDIA/skillsUse for CUDA-Q setup, simulation targets, QPU access, and @cudaq.kernel authoring guidance.OtherNo warnings★ 3.8K↓ —
- doca-commonNVIDIA/skillsUse this skill whenever the user is doing hands-on DOCA programming on a BlueField DPU or ConnectX NIC and needs the foundation primitives every per-library context rests on — walking the doca_ctx lifecycle, discovering doca_dev / doca_devinfo and gating on doca_*_cap_* before trusting a feature, wiring doca_mmap / doca_buf_inventory / doca_buf for zero-copy I/O across libraries, driving doca_pe for completions, or DOCA Log's two-tier (--sdk-log-level vs app-side) model. Trigger even when the user does not say "DOCA Common" — typical implicit phrasings include "my tasks submit but nothing completes", "DOCA_ERROR_BAD_STATE from doca_ctx_start", "--sdk-log-level does nothing for my DOCA_LOG_DBG lines", "share a buf between doca_dma and doca_rdma", or "crashes far from the offending line". Refuse and route elsewhere for per-library questions in isolation (load doca-flow / doca-rdma / doca-eth alongside), installing DOCA (doca-setup), or doc lookup (doca-public-knowledge-map).ProductivityNo warnings★ 3.8K↓ —
- splitting-datasetsjeremylongshore/tons-of-skills-marketplaceProcess split datasets into training, validation, and testing sets for ML model development. Use when requesting "split dataset", "train-test split", or "data partitioning". Trigger with relevant phrases based on skill purpose.TestingNo warnings★ 2.9K↓ —
nemo-relay-plugin-build
NVIDIA/skills
OtherUpdated 3 days ago
From the author
Use this skill when building or packaging reusable NeMo Relay runtime behavior as an embedded configuration component or a manifest-backed `rust_dynamic` native or `worker` gRPC plugin, with deterministic validation and rollback-safe registration.
Install
npx skills add NVIDIA/skills --skill nemo-relay-plugin-build -a claude-code
Installs to .claude/skills/nemo-relay-plugin-build/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Download .zip
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
What it can touch
Instructions onlyNo network use seenLicence: APACHE-2.0
Safety checks on SKILL.md
No warnings.
Why 90
Security100
Provenance83
Maintenance100
Licence100
Adoption57
Files (5)
- BENCHMARK.md
- SKILL.md
- evals/evals.json
- skill-card.md
- skill.oms.sig