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 2 hours ago
48,622 skills
- gsd:session-reportdavepoon/buildwithclaudeGenerate a session report with token usage estimates, work summary, and outcomesProductivityNo warnings★ 3.7K↓ —
- nvidia-appNVIDIA/skillsNVIDIA App MCP: drivers, games, laptops, overlay. Check drivers, manage and optimize games, configure laptop features.OtherNo warnings★ 3.8K↓ —
- skyverndavepoon/buildwithclaudeAI-powered browser automation — navigate sites, fill forms, extract structured data, log in with stored credentials, and build reusable multi-step workflows using natural language. Install: pip install skyvern && skyvern setupBrowserNo warnings★ 3.7K↓ —
- testingdavepoon/buildwithclaudeTesting strategies and methodologies including TDD, E2E testing, and multi-framework supportTestingNo warnings★ 3.7K↓ —
- gsd:research-phasedavepoon/buildwithclaudeResearch how to implement a phase (standalone - usually use /gsd:plan-phase instead)ScienceNo 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↓ —
- gsd:autonomousdavepoon/buildwithclaudeRun all remaining phases autonomously — discuss→plan→execute per phasePlanningNo warnings★ 3.7K↓ —
- reasoningjeremylongshore/tons-of-skills-marketplaceUse BEFORE answering analytical, diagnostic, planning, or multi-step reasoning questions. Trigger phrases include "should I X or Y", "why is X happening", "what's the best approach", "what are the tradeoffs", "help me think through", "diagnose", "root cause", "plan/design X", "what are the implications of", "compare these approaches". Also fires on cross-domain analysis, strategy questions, architecture decisions, or anything requiring multiple factors to be weighed before responding. The skill calls the reasoning MCP tool to retrieve a cognitive scaffold (named failure pattern, executable procedure, suppression vectors, falsification test) the model absorbs internally before generating its response. Catches causal shortcuts, premature conclusions, generic templates, and surface pattern matching that produce confidently-wrong answers. Do NOT trigger for simple factual lookups, syntax questions, file reads, code execution, or restating the user's input.TestingNo warnings★ 2.9K↓ —
- gsd:plan-phasedavepoon/buildwithclaudeCreate detailed phase plan (PLAN.md) with verification loopPlanningNo warnings★ 3.7K↓ —
- vercel-hello-worldjeremylongshore/tons-of-skills-marketplaceCreate a minimal working Vercel deployment with a serverless API route. Use when starting a new Vercel project, testing your setup, or learning basic Vercel deployment and API route patterns. Trigger with phrases like "vercel hello world", "vercel example", "vercel quick start", "simple vercel project", "first vercel deploy".TestingNo warnings★ 2.9K↓ —
- gsd:forensicsdavepoon/buildwithclaudePost-mortem investigation for failed GSD workflows — analyzes git history, artifacts, and state to diagnose what went wrongSecurityNo warnings★ 3.7K↓ —
- gsd:review-backlogdavepoon/buildwithclaudeReview and promote backlog items to active milestoneEngineeringNo warnings★ 3.7K↓ —
- speak-install-authjeremylongshore/tons-of-skills-marketplaceSet up Speak language learning API integration and authentication. Use when configuring Speak API access, setting up OAuth with OpenAI Realtime API for speech, or initializing a language tutoring application. Trigger with phrases like "install speak", "setup speak", "speak auth", "configure speak API", "speak language learning setup".EngineeringNo warnings★ 2.9K↓ —
- influencer-discoveryaaron-he-zhu/aaron-marketing-skillsUse when the user asks to "find influencers", "build an influencer list", or "discover creators in [niche]"; produces a multi-platform candidate pool, per-influencer evidence profiles, authenticity red-flag screening, and a Fit-readiness queue without action ranking. Not for STAR scoring or ranking a known shortlist — use fit-scorer. 达人挖掘/找达人/创作者名单OtherNo warnings★ 3K↓ —
- ci-pipeline-synthesizerkajisho5/ffmpeg-skillGenerate GitHub Actions CI/CD pipeline configurations for automated building and testing of library and package projects. Use when creating or updating CI workflows for npm packages, Python packages, Go modules, Rust crates, or other library projects that need automated build and test pipelines. Includes templates for common package ecosystems with best practices for dependency caching, matrix testing, and artifact publishing.TestingNo warnings★ 4.2K↓ —
- sentry-hello-worldjeremylongshore/tons-of-skills-marketplaceCapture your first test error with Sentry and verify it appears in the dashboard. Use when testing a new Sentry integration, verifying error capture works after install-auth, or learning how to enrich events with user context, tags, and breadcrumbs. Trigger with phrases like "test sentry", "sentry hello world", "verify sentry", "first sentry error", "sentry capture test".TestingNo warnings★ 2.9K↓ —
- stock-liquidityhimself65/finance-skillsAnalyze how liquid a stock is using Yahoo Finance data (yfinance): bid-ask spreads, volume and dollar volume (ADTV), top-of-book and options depth, square-root market impact and slippage estimates, turnover ratio, and Amihud illiquidity, rolled into a liquidity grade. Use this skill whenever the user asks about liquidity or trading costs — how easily a position can be entered or exited, what a large order would do to the price, spread or execution-cost estimates, order book depth, volume patterns, or liquidity comparisons — especially for small caps, penny stocks, and thinly traded names.FinanceNo warnings★ 3.5K↓ —
- kiro-validate-implgotalab/cc-sddValidate feature-level integration after all tasks are implemented. Checks cross-task consistency, full test suite, and overall spec coverage.TestingNo warnings★ 3.7K↓ —
- hormuz-straithimself65/finance-skillsCheck the live status of the Strait of Hormuz from the Hormuz Strait Monitor dashboard: open, restricted, or closed status, tanker transits vs normal, stranded vessels, Brent price impact, war-risk insurance levels, cargo throughput, tanker freight rates, diplomatic developments, and global trade impact. Use this skill whenever the user asks about the Strait of Hormuz or the Persian Gulf in the context of oil, shipping, or geopolitical risk — whether Hormuz is open, chokepoint or transit disruption, Gulf tanker traffic, war-risk premiums, Middle East shipping routes, or energy supply-chain risk.ProductivityNo warnings★ 3.5K↓ —
- yfinance-datahimself65/finance-skillsFetch financial and market data with the yfinance Python library (Yahoo Finance). Use this skill whenever the user wants stock data: current quotes and price history, financial statements (income statement, balance sheet, cash flow), options chains, dividends and splits, earnings and analyst estimates, price targets and ratings, institutional and insider holdings, news, multi-ticker comparisons, stock screens, or sector and industry data. Use it even when the user gives only a ticker symbol (AAPL, MSFT, TSLA) and the intent has to be inferred. For earnings previews or recaps, estimate revisions, valuation, correlation, liquidity, or ETF premium analysis, prefer the dedicated skill.FinanceNo warnings★ 3.5K↓ —
- gsd:debugdavepoon/buildwithclaudeSystematic debugging with persistent state across context resetsEngineeringNo warnings★ 3.7K↓ —
- sentry-cost-tuningjeremylongshore/tons-of-skills-marketplaceOptimize Sentry costs, reduce event volume, and manage quota spend. Use when analyzing Sentry billing, reducing error/transaction volume, configuring sampling rates, or preventing overage charges. Trigger: "reduce sentry costs", "sentry billing optimization", "sentry quota management", "optimize sentry spend", "sentry sampling".OtherNo warnings★ 2.9K↓ —
- gsd:audit-uatdavepoon/buildwithclaudeCross-phase audit of all outstanding UAT and verification itemsOtherNo warnings★ 3.7K↓ —
- doca-aes-gcmNVIDIA/skillsUse this skill when the user is doing hands-on DOCA AES-GCM work on a BlueField DPU or ConnectX NIC — configuring `doca_aes_gcm_task_encrypt` / `_task_decrypt`, querying `doca_aes_gcm_cap_*` for per-key-type (only `DOCA_AES_GCM_KEY_128` / `_256` — AES-192 not supported) and per-task support, sizing plaintext against the max-buf cap, setting source / destination mmap permissions, validating with a NIST GCMVS or RFC 5288 vector, or debugging DOCA_ERROR_* including the security-critical tag-verification-failed outcome on decrypt. Trigger even when the user does not explicitly mention "DOCA AES-GCM" or "AEAD" — typical implicit phrasings: "decrypt completion IO_FAILED", "auth tag isn't verifying", "NOT_PERMITTED on my encrypt buffer", "is AES-192-GCM on this BlueField" (no), or "encrypted record came back tampered". Refuse and route elsewhere for non-GCM AES modes (CBC / CTR / XTS — CPU OpenSSL), key management (KMS / HSM / rotation), SHA (doca-sha), or general AEAD background.SecurityNo warnings★ 3.8K↓ —
doca-debug
NVIDIA/skills
From the author
Use this skill when the user is debugging any DOCA symptom — a build that won't compile, a link step that can't resolve a doca_* symbol, a runtime call returning DOCA_ERROR_*, a silent service or tool, or a stack trace / valgrind / core dump — and needs the layered ladder (install → version → build → link → runtime → program → driver), verbosity controls (--sdk-log-level, DOCA_LOG_LEVEL, the doca-{lib}-trace flavor), container-debug constraints, or how to capture state for a Developer Forum post. Trigger even when the user does not say "DOCA debug" — implicit phrasings include "undefined reference to doca_*", "how do I get more logs", "packets aren't reaching the wire", "doca_caps returned nothing", or "hugepages empty in the container". Refuse and route elsewhere for library-specific debug (Flow pipe trace, RDMA QP, Comch stats), env-class pkg-config or hugepages symptoms, the DOCA_ERROR_* taxonomy and lifecycle interpretation, and performance or incident-response work — those belong to other skills.
Install
npx skills add NVIDIA/skills --skill doca-debug -a claude-code
Installs to .claude/skills/doca-debug/ · 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