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,168 skills from 2,325 repositories · updated 18 hours ago
48,168 skills
- kiro-steeringgotalab/cc-sddManage {{KIRO_DIR}}/steering/ as persistent project knowledgeOtherNo warnings★ 3.7K↓ —
- cargo-fuzztrailofbits/skillsSets up and runs cargo-fuzz, the standard fuzzing tool for Cargo-based Rust projects. Covers cargo fuzz init, the nightly toolchain requirement, fuzz_target! harnesses, Arbitrary-derived structured inputs, sanitizer options, cargo fuzz coverage, and reproducing a crash artifact. Use when fuzzing a Rust crate, writing a fuzz_target!, exercising unsafe blocks or FFI in Rust, or triaging a cargo fuzz crash.WritingNo warnings★ 7.9K↓ —
- ossfuzztrailofbits/skillsEnrolls a project in OSS-Fuzz, Google's free continuous fuzzing service for open source, and drives it locally. Covers project.yaml, Dockerfile and build.sh setup, the helper scripts, reproducing OSS-Fuzz crash reports, and the acceptance criteria. Use when setting up continuous fuzzing for an open-source project, reproducing an OSS-Fuzz bug report, or testing an OSS-Fuzz build before submitting it.TestingNo warnings★ 7.9K↓ —
- implement-patchtrailofbits/skillsUse when a confirmed local bug needs an invariant-level fix, variant search, tests, and one local commit.TestingNo warnings★ 7.9K↓ —
- whybacknotprop/pstackUse for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.DevOpsNo warnings★ 3.3K↓ —
- kiro-spec-requirementsgotalab/cc-sddGenerate comprehensive requirements for a specificationPlanningNo warnings★ 3.7K↓ —
- kiro-validate-designgotalab/cc-sddInteractive technical design quality review and validation. Use when reviewing design before implementation.DesignNo warnings★ 3.7K↓ —
- reproduce-bugtrailofbits/skillsUse when a named runtime or compiler bug in a local repository needs independent reproduction.OtherNo warnings★ 7.9K↓ —
- patching-bugstrailofbits/skillsUse when a known bug or falsifiable bug hypothesis in a local codebase needs a patch commit and reviewable proof report.EngineeringNo warnings★ 7.9K↓ —
- kiro-steering-customgotalab/cc-sddCreate custom steering documents for specialized project contexts. Use when creating domain-specific steering files.PlanningNo warnings★ 3.7K↓ —
- ena-databaseforyourhealth111-pixel/Vibe-SkillsAccess European Nucleotide Archive via API/FTP. Retrieve DNA/RNA sequences, raw reads (FASTQ), genome assemblies by accession, for genomics and bioinformatics pipelines. Supports multiple formats.DataNo warnings★ 3.8K↓ —Also in 1 other repo
- validate-bugtrailofbits/skillsUse when a bug PoC package needs an independent rerun and judgment before patching.OtherNo warnings★ 7.9K↓ —
- prove-patchtrailofbits/skillsUse when a local security patch commit needs independent scoped and three-arm proof.SecurityNo warnings★ 7.9K↓ —
- dwarf-experttrailofbits/skillsAnalyzes DWARF debug information in compiled binaries. Use when inspecting .debug_* sections, DIE trees, or DW_TAG_/DW_AT_ entries with dwarfdump/llvm-dwarfdump or readelf, verifying debug info with llvm-dwarfdump --verify, answering DWARF standard questions, or writing code that parses DWARF (libdwarf, pyelftools, gimli).WritingNo warnings★ 7.9K↓ —
- cursor-multi-repojeremylongshore/tons-of-skills-marketplaceWork with multiple repositories in Cursor: multi-root workspaces, monorepo patterns, selective indexing, and cross-project context. Triggers on "cursor multi repo", "cursor multiple projects", "cursor monorepo", "cursor workspace", "multi-root workspace".ProductivityNo warnings★ 2.9K↓ —
- ruzzytrailofbits/skillsSets up and runs Ruzzy, Trail of Bits' coverage-guided Ruby fuzzer and the only production-ready one for the language. Covers harness structure, fuzzing pure Ruby and the native C extensions in gems, and sanitizer builds. Use when fuzzing a Ruby library or gem, testing a Ruby C extension for memory safety, or asking how to fuzz Ruby at all.TestingNo warnings★ 7.9K↓ —
- rust-reviewtrailofbits/skillsPerforms comprehensive Rust security review for safe/unsafe boundary issues, memory safety in unsafe blocks, concurrency hazards, panic-induced DoS, FFI safety, and async runtime mistakes. Use when auditing Rust crates, services, or libraries — particularly those with `unsafe`, FFI, or concurrent code.EngineeringNo warnings★ 7.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↓ —
- replay-regressiontrailofbits/skillsUse when independently verifying a supplied PoC against fresh live before/after deployments.DevOpsNo warnings★ 7.9K↓ —
- prepare-regressiontrailofbits/skillsUse when pinning before/after sources and collecting PR or commit context for a regression investigation.FinanceNo warnings★ 7.9K↓ —
- aflpptrailofbits/skillsSets up and runs AFL++ for multi-core fuzzing of C/C++ projects built with afl-clang-fast or afl-gcc-fast. Covers instrumentation modes, parallel main and secondary campaigns, persistent mode, corpus minimization, and crash triage. Use when scaling fuzzing across cores, fuzzing a mature C/C++ codebase, reading the afl-fuzz status screen, or moving on after libFuzzer has plateaued.OtherNo warnings★ 7.9K↓ —
- kiro-debuggotalab/cc-sddInvestigate implementation failures using root-cause-first debugging. Use when an implementer is blocked, verification fails, or repeated remediation does not converge.EngineeringNo warnings★ 3.7K↓ —Also in 7 other repos
- terms-generatorjeremylongshore/tons-of-skills-marketplaceDraft service-specific terms from confirmed features, business decisions and scoped applicability review, with clear assumptions and a separate review record. Use when preparing or revising website or app terms. Trigger with "terms-generator" or "create terms of service".PlanningNo warnings★ 2.9K↓ —
- hermes-tweetdavepoon/buildwithclaudeUse Hermes Tweet when a Claude Code workflow needs a source-aware handoff to Hermes Agent for X/Twitter research, account context, monitoring, or approval-gated actions through the native Hermes Agent plugin.ScienceNo warnings★ 3.7K↓ —
doca-version
NVIDIA/skills
From the author
DOCA version handling: detect the installed release and validate the four-way match across pkg-config doca-common, applications/VERSION, doca_caps --version, and bfver/mlnx-release on BlueField; reason about NGC tags; look up whether a capability exists on this release; diagnose build-vs-runtime drift. Use this skill alongside doca-debug when a symptom smells of version skew: "built but nothing on the wire", "undefined reference to a symbol the docs claim exists", "DOCA_ERROR_NOT_SUPPORTED at runtime", "what does latest mean for this tag", or "is my LTS still supported". Once all four sources match, the component's build / run workflow belongs to its own library, service or tool skill. Refuse install / package choice (doca-setup), per-library API questions (matching library skill), DOCA_ERROR_* taxonomy (doca-programming-guide), and the general debug ladder (doca-debug).
Install
npx skills add NVIDIA/skills --skill doca-version -a claude-code
Installs to .claude/skills/doca-version/ · 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 90
Files (7)
- BENCHMARK.md
- CAPABILITIES.md
- SKILL.md
- TASKS.md
- evals/evals.json
- skill-card.md
- skill.oms.sig