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 6 hours ago
48,168 skills
- nemo-rl-auto-researchNVIDIA/skillsAutonomous NeMo-RL research agent workflow for directed hypothesis testing and open-ended discovery. Guides agents through the full experiment lifecycle: understanding recipes and environments, wiring RL or NeMo-gym runs, launching reproducible baselines and iterations, analyzing results, preserving human oversight, and using git plus TSV logs as the research ledger. Do NOT use for: bug fixes, code review, documentation, refactoring, dependency updates, or single-file changes.ScienceNo warnings★ 3.8K↓ —
- review-workcode-yeongyu/oh-my-openagentPost-implementation gate review: run manual QA on the real surface yourself, then launch ONE gate reviewer (never a panel) to audit goal, constraints, code quality, security, missed context, and QA evidence. Use before a PR handoff or when the user explicitly asks to review completed work.EngineeringNo warnings★ 70.5K↓ —
- 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↓ —
- provider-configurationhashicorp/agent-skillsImplement Terraform provider configuration and authentication with the Plugin Framework: provider schema for credentials (Optional + Sensitive attributes), environment variable fallbacks, credential provider chains (static config, then environment variables, shared credentials file, and platform identity), unknown-value guards in Configure(), secret redaction, configure-time credential validation, and diagnostics that name every source tried. Use when implementing or reviewing a provider's Configure method or provider schema, adding authentication options (API keys, tokens, profiles, credentials files, assume-role), deciding how a provider should resolve credentials, debugging "no valid credential sources" or missing-credentials errors, or unit testing credential resolution.OfficialTestingNo warnings★ 910↓ —
- implement-patchtrailofbits/skillsUse when a confirmed local bug needs an invariant-level fix, variant search, tests, and one local commit.TestingNo warnings★ 7.9K↓ —
- cloudformation-to-pulumipulumi/agent-skillsConvert, migrate, or import AWS CloudFormation stacks or templates into Pulumi programs. Load this skill whenever a user wants to move from CloudFormation to Pulumi, convert a CFN template, import existing CloudFormation-managed resources into Pulumi, or asks about CloudFormation-to-Pulumi migration in any form. Also load when the user mentions cdk-importer in a migration context.OfficialDevOpsNo warnings★ 78↓ —
- recallbacknotprop/pstackReconstruct your recent working context from your own chat history, live state, and the shared record (user reports, prior fixes, incidents), then hand back a tight current-state brief. Use for 'recall my work on X', 'catch me up', 'what have I been working on', 'where did I leave off', before starting or resuming work.ProductivityNo warnings★ 3.3K↓ —
- pulumi-debug-failed-operationpulumi/agent-skillsDebug a Pulumi update or preview that failed: read the failure Pulumi already recorded, find what caused it, and fix it. Load this skill when the user asks to debug, diagnose, or fix a failed update or preview, or points at a failing `pulumi up` or `pulumi preview`. Don't load it for authoring new infrastructure, migrations, or provider upgrades; those have their own skills.OfficialEngineeringNo warnings★ 78↓ —
- code-improvertrailofbits/skillsRuns an autonomous review-and-fix improvement loop over any code target — a skill, plugin, module, or directory — using a reviewer the user names: any installed skill or agent. Keeps a cross-round findings ledger, escalates when fixes stop converging, and guards scope mechanically. Use when asked to 'improve this code until review passes', 'run an improvement loop with <reviewer>', or to iterate review-and-fix with a specific reviewer. For skills prefer the skill-improver entry; for a branch prefer pr-improver.EngineeringNo warnings★ 7.9K↓ —
- unslopbacknotprop/pstackCut AI tells from any writing.WritingNo warnings★ 3.3K↓ —Also in 1 other repo
- hive.terminal-tools-pty-sessionsaden-hive/hiveUse when you need state across calls — building env vars, navigating with cd, driving REPLs (python -i, mysql, psql, node), or responding to interactive prompts (sudo password, ssh host-key confirmation, mysql connection). Teaches the prompt-sentinel exec pattern (default mode), raw I/O for REPLs (raw_send=True then read_only=True), the one-in-flight-per-session rule, and the close-or-leak-against-the-cap discipline. Bash on macOS — never zsh; explicit shell=/bin/zsh is rejected. Read before calling terminal_pty_open.DataNo warnings★ 11.1K↓ —
- linear-hello-worldjeremylongshore/tons-of-skills-marketplaceProve Linear authentication and workspace visibility with the smallest read-only GraphQL or SDK query. Use when establishing a new integration baseline without creating test issues. Trigger with "test Linear connection", "Linear hello world", or "verify Linear API key".TestingNo warnings★ 2.9K↓ —
- instrument-data-to-allotropeanthropics/knowledge-work-pluginsConvert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full ASM JSON, flattened CSV for easy import, and exportable Python code for data engineers. Common triggers include converting instrument files, standardizing lab data, preparing data for upload to LIMS/ELN systems, or generating parser code for production pipelines.OfficialDataNo warnings★ 34.1K↓ —
- nvshmem-enable-tmaNVIDIA/skillsPrepare or review NVSHMEM CUDA kernels for TMA SMEM registration and direct-SMEM transfers. Do not use for unrelated CUDA tuning.EngineeringNo warnings★ 3.8K↓ —
- lindy-sdk-patternsjeremylongshore/tons-of-skills-marketplaceLindy integration patterns for webhook handling, HTTP actions, and Run Code. Use when building integrations, calling Lindy agents from code, or implementing the Run Code action with Python/JavaScript. Trigger with phrases like "lindy integration patterns", "lindy best practices", "lindy webhook patterns", "lindy Run Code", "lindy HTTP Request".EngineeringNo warnings★ 2.9K↓ —
- canva-hello-worldjeremylongshore/tons-of-skills-marketplaceVerify a Canva Connect integration with a minimal read-only identity request and a redacted receipt. Use when proving OAuth, endpoint reachability, and response shape before any design or asset mutation. Trigger with: "test Canva connection", "Canva hello world", "verify Canva auth".TestingNo warnings★ 2.9K↓ —
- visualization-best-practicesforyourhealth111-pixel/Vibe-SkillsReview chart choice, labeling, accessibility, and storytelling quality for existing visualizations. Use as an explicit/manual helper for critique and cleanup, not as the main owner for scientific figure production or general chart generation.ScienceNo warnings★ 3.8K↓ —
- 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↓ —
- adobe-data-handlingjeremylongshore/tons-of-skills-marketplaceAnalyze and enforce classification, minimization, signed-URL custody, retention, deletion, content provenance, and privacy-request boundaries for Adobe workflows. Use when the task requires adobe data custody and privacy review. Trigger with "Adobe data handling", "PDF privacy", or "Firefly content policy".DocumentsNo warnings★ 2.9K↓ —
- cudaq-importingNVIDIA/skillsUse when porting circuits from another framework (e.g. Qiskit) into CUDA-Q kernels while preserving the source algorithm and validation fidelity.OtherNo warnings★ 3.8K↓ —
- jetson-init-sourceNVIDIA/skillsSet up the BSP source workspace: Linux_for_Tegra overlay tracker, bsp_sources, Crosstool-NG toolchain. Use after jetson-init-image; not for fetching inputs.MediaNo warnings★ 3.8K↓ —
- in-your-own-wordsbacknotprop/pstackRestate in your own words what you think the user's goals are and what problem they're trying to solve. Use for /in-your-own-words.OtherNo warnings★ 3.3K↓ —
- reflectbacknotprop/pstackSpawn three parallel review subagents over the active transcript, surface learnings, and route each to a concrete edit on an existing skill. Use when the user says reflect.WritingNo warnings★ 3.3K↓ —
- exa-load-scalejeremylongshore/tons-of-skills-marketplaceValidate Exa capacity with synthetic workload models, endpoint-specific budgets, bounded queues, and stop conditions. Use when operating or reviewing this Exa boundary. Trigger with "Exa load scale", "review Exa load scale", or "fix Exa load scale".PlanningNo warnings★ 2.9K↓ —
doca-firefly
NVIDIA/skills
From the author
Use this skill when the user is operating the DOCA Firefly Service container on BlueField — picking the four PTP configuration axes (role / profile / domain / interface), wiring the BlueField PHC + host follower + consumer workload pairing, deciding whether PTP-grade time is even needed (vs. chrony / NTP), or debugging a Firefly deployment where PTP isn't syncing or the host clock isn't following. Trigger even when the user does not explicitly mention "DOCA Firefly" or "PTP" — typical implicit phrasings include "container green but PTP never advances past LISTENING", "Firefly says synced but the host clock still drifts", "sync acquired but offset is tens of microseconds", "my Rivermax SMPTE workload needs PTP", or "is chrony good enough". Refuse and route elsewhere for installing DOCA, host-side chrony / ptp4l config bodies, PTP topology / boundary-clock design, building DOCA apps that read the disciplined PHC, or other DOCA services (DMS, Flow-Inspector, HBN) — those belong to other skills.
Install
npx skills add NVIDIA/skills --skill doca-firefly -a claude-code
Installs to .claude/skills/doca-firefly/ · 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 (8)
- BENCHMARK.md
- CAPABILITIES.md
- SKILL.md
- SKILLCARD.yaml
- TASKS.md
- evals/evals.json
- skill-card.md
- skill.oms.sig