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 9 hours ago
48,168 skills
- jetson-set-targetNVIDIA/skillsSwitch the active Jetson target-platform pointer to an existing profile YAML. Use before customize/build/flash to change target; not for authoring profiles — use jetson-init-target instead.OtherNo warnings★ 3.8K↓ —
- keyword-researchnowork-studio/notfair-pluginDiscover, analyze, and prioritize keywords for SEO and GEO content strategies from a seed keyword or niche. Identifies high-value opportunities based on search volume, competition, intent, and business relevance. Generates topic clusters. For building a dated editorial calendar from your own Search Console data, use `content-planner` instead — this skill is seed-driven keyword discovery, not calendar scheduling. Use when asked to "find keywords", "keyword research", "keyword analysis", "search volume", "keyword difficulty", "content ideas from a seed", or any keyword discovery task.ScienceNo warnings★ 4.1K↓ —
- gsd:session-reportdavepoon/buildwithclaudeGenerate a session report with token usage estimates, work summary, and outcomesProductivityNo warnings★ 3.7K↓ —
- wiki-researchAr9av/obsidian-wikiPerform multi-round web research on a topic, synthesize the findings, and file structured results into the Obsidian wiki. Use for comprehensive web-sourced research intended to become wiki knowledge.ScienceNo warnings★ 3.6K↓ —
- earnings-previewhimself65/finance-skillsBuild a pre-earnings briefing for a stock from Yahoo Finance data (yfinance): the upcoming report date and timing, consensus EPS and revenue estimates with their range, the beat/miss track record, analyst ratings and price targets, and what to watch in the print. Use this skill whenever the user is preparing for an upcoming earnings report or asks what the street expects — consensus or whisper numbers, EPS expectations, whether a company will beat, an earnings setup, or an earnings-season preview — and whenever a ticker comes up in the context of upcoming earnings, even without the word "preview". For results that are already out, use earnings-recap.FinanceNo warnings★ 3.5K↓ —
- adobe-hello-worldjeremylongshore/tons-of-skills-marketplaceProve one Adobe API connection with a current, read-only or synthetic operation and a content-safe receipt. Use during onboarding before any production workflow. Use when the task requires adobe minimal access proof. Trigger with "Adobe hello world", "test Adobe connection", or "verify Adobe entitlement".TestingNo warnings★ 2.9K↓ —
- make-pr-easy-to-reviewmichael-denyer/pstack-claudePrepare PRs for review by cleaning noisy history, improving PR descriptions, and adding reviewer guidance without changing code behavior. Use for "make this easy to review", "tidy this PR", "clean up commits", or "annotate the diff".EngineeringNo warnings★ 3.7K↓ —
- hex-sdk-patternsjeremylongshore/tons-of-skills-marketplaceApply production-ready Hex SDK patterns for TypeScript and Python. Use when implementing Hex integrations, refactoring SDK usage, or establishing team coding standards for Hex. Trigger with phrases like "hex SDK patterns", "hex best practices", "hex code patterns", "idiomatic hex".EngineeringNo warnings★ 2.9K↓ —
- data-context-extractoranthropics/knowledge-work-pluginsGenerate or improve a company-specific data analysis skill by extracting tribal knowledge from analysts. BOOTSTRAP MODE - Triggers: "Create a data context skill", "Set up data analysis for our warehouse", "Help me create a skill for our database", "Generate a data skill for [company]" → Discovers schemas, asks key questions, generates initial skill with reference files ITERATION MODE - Triggers: "Add context about [domain]", "The skill needs more info about [topic]", "Update the data skill with [metrics/tables/terminology]", "Improve the [domain] reference" → Loads existing skill, asks targeted questions, appends/updates reference files Use when data analysts want Claude to understand their company's specific data warehouse, terminology, metrics definitions, and common query patterns.OfficialProductivityNo warnings★ 34.1K↓ —Also in 1 other repo
- apollo-cost-tuningjeremylongshore/tons-of-skills-marketplaceOptimize Apollo.io costs and credit usage. Use when managing Apollo credits, reducing API costs, or optimizing subscription usage. Trigger with phrases like "apollo cost", "apollo credits", "apollo billing", "reduce apollo costs", "apollo usage".EngineeringNo warnings★ 2.9K↓ —
- maintain-formal-verification-skillmichael-denyer/pstack-claudeBring a project's formal verification back in line with the code after the code changes: find the commits that touched verified code, update the model, harness, or properties to describe the code as it is now, rerun, and say whether each failure is drift in the verification or a bug in the code. Use for /maintain-formal-verification-skill, "is the model still true to the code", or after merges and refactors that touched verified code without rechecking it.EngineeringNo warnings★ 3.7K↓ —
- principle-outcome-oriented-executionmichael-denyer/pstack-claudeApply during planned rewrites and migrations with explicit phase boundaries. Converge on the target architecture; don't preserve smooth intermediate states with throwaway compatibility code.PlanningNo warnings★ 3.7K↓ —
- golang-dependency-managementsamber/cc-skills-golangDependency management for Golang projects — go.mod and go.sum, `go get` install and upgrade flows, Minimal Version Selection, conflict resolution with replace/exclude/retract, `govulncheck` scanning of the module tree, outdated dependency and binary size auditing, vendoring, `tool` directives, and go.work workspaces. Use when adding, removing, or upgrading Go dependencies, deciding whether to take on a package, resolving version conflicts, or auditing what a module pulls in. Covers choosing and upgrading dependency versions, not the surrounding tooling: do NOT use for fixing an exploitable vulnerability in code (→ See `samber/cc-skills-golang@golang-security` skill) or for wiring Dependabot/Renovate update bots into CI workflows (→ See `samber/cc-skills-golang@golang-continuous-integration` skill).SecurityNo warnings★ 3.7K↓ —
- property-based-testingforyourhealth111-pixel/Vibe-SkillsProperty-based testing with fast-check (TypeScript/JavaScript) and Hypothesis (Python). Generate test cases automatically, find edge cases, and test mathematical properties. Use when user mentions property-based testing, fast-check, Hypothesis, generating test data, QuickCheck-style testing, or finding edge cases automatically.TestingNo warnings★ 3.8K↓ —
- sharp-edgestrailofbits/skillsIdentifies error-prone APIs, dangerous configurations, and footgun designs that enable security mistakes. Use when reviewing API designs, configuration schemas, cryptographic library ergonomics, or evaluating whether code follows 'secure by default' and 'pit of success' principles. Triggers: footgun, misuse-resistant, secure defaults, API usability, dangerous configuration.SecurityNo warnings★ 7.9K↓ —
- doca-perftestNewNVIDIA/skillsUse this skill when the user is running DOCA Perftest (doca_perftest), the RDMA benchmark that measures bandwidth, message rate and latency for RDMA verbs, point-to-point or across a cluster, with an optional DOCA Verbs backend (-r dv) or GPUNetIO engine (--engine gpunetio). Trigger even when the user does not say "DOCA Perftest" — implicit phrasings include "how do I benchmark RDMA write bandwidth with DOCA", "run ib_write_bw but across 8 nodes", "perftest says the device is busy", "my latency numbers differ between client and server", "launch the server over SSH", or "run an all-to-all RDMA test from a JSON scenario". Refuse and route elsewhere for DOCA install (doca-setup), DOCA Bench (doca-bench), and application-level throughput.TestingNo warnings★ 3.8K↓ —
- golang-grpcsamber/cc-skills-golangProvides gRPC usage guidelines, protobuf organization, and production-ready patterns for Golang microservices. Use when implementing, reviewing, or debugging gRPC servers/clients, writing proto files, setting up interceptors, handling gRPC errors with status codes, configuring TLS/mTLS, testing with bufconn, or working with streaming RPCs.TestingNo warnings★ 3.7K↓ —
- helpdavepoon/buildwithclaudeOne-screen quick reference for the Origin plugin. Lists the daily verbs, the daily flow, where data lives, and how to view it without a GUI. Use when the user says "help", "what can I do", "list origin commands", "how do I use origin", or invokes `/help`.OtherNo warnings★ 3.7K↓ —
- reviewdavepoon/buildwithclaudePower-user audit of Origin's pending surfaces. Most users want `/brief` for revisions. That handles the daily flow. Use `/review` only for explicit deep-walk audits after bulk imports, or when you want to walk the full queue rather than the top 3 shown in /brief. Invoked as `/review captures` or `/review revisions`.EngineeringNo warnings★ 3.7K↓ —
- prompt-lookupforyourhealth111-pixel/Vibe-SkillsActivates when the user asks about AI prompts, needs prompt templates, wants to search for prompts, or mentions prompts.chat. Use for discovering, retrieving, and improving prompts.OtherNo warnings★ 3.8K↓ —
- task-observerrebelytics/one-skill-to-rule-them-allMonitors task execution for skill improvement opportunities: logs patterns, user corrections and methodology worth preserving to the workspace, turns them into skill updates in a weekly review, and flags repeating work as new skills. Use during ANY multi-step task, agentic workflow, or work session. Also triggers in post-task feedback discussions and when the user mentions skill observations, the observation log, or skill taxonomy. Also known as "One Skill to Rule Them All" — trigger on this phrase too. IMPORTANT: invoke this skill before the FIRST tool call of any session and before writing or proposing a plan — any turn that will involve a tool call counts. This sentence is the session-start trigger and the only activation layer that survives an unreachable config file; pair it with a CLAUDE.md instruction or a session-start hook (references/environments.md). A subagent dispatched by a session already running it does not run it: it writes nothing and puts its findings in its report.ProductivityNo warnings★ 3.7K↓ —
- exa-local-dev-loopjeremylongshore/tons-of-skills-marketplaceBuild and test an Exa adapter locally using schema fixtures, recorded content-free envelopes, and an explicit opt-in live lane. Use when operating or reviewing this Exa boundary. Trigger with "Exa local dev loop", "review Exa local dev loop", or "fix Exa local dev loop".TestingNo warnings★ 2.9K↓ —
- excel-pivot-wizardjeremylongshore/tons-of-skills-marketplaceCreate advanced Excel pivot tables with calculated fields and slicers. Use when building data summaries or creating interactive dashboards. Trigger with phrases like 'excel pivot', 'create pivot table', 'data summary'.DocumentsNo warnings★ 2.9K↓ —
- hubspot-automationdavepoon/buildwithclaudeAutomate HubSpot CRM operations (contacts, companies, deals, tickets, properties) via Rube MCP using Composio integration.OtherNo warnings★ 3.7K↓ —
api-contract
jeremylongshore/tons-of-skills-marketplace
From the author
Configure this skill should be used when the user asks about "API contract", "api-contract.md", "shared interface", "TypeScript interfaces", "request response schemas", "endpoint design", or needs guidance on designing contracts that coordinate backend and frontend agents. Use when building or modifying API endpoints. Trigger with phrases like 'create API', 'design endpoint', or 'API scaffold'.
Install
npx skills add jeremylongshore/tons-of-skills-marketplace --skill api-contract -a claude-code
Installs to .claude/skills/api-contract/ · 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)
- SKILL.md
- references/best-practices.md
- references/errors.md
- references/examples.md
- references/pagination.md
- references/typescript-interfaces.md
- references/writing-endpoints.md