write-api-reference
vercel/next.js/.agents/skills/write-api-reference/SKILL.md
Produces API reference documentation for Next.js APIs: functions, components, file conventions, directives, and config options.
1 project uses a version of this
Skills real projects publish on GitHub, most starred first. Each one says what it will make an agent do before you copy it.
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
vercel/next.js/.agents/skills/write-api-reference/SKILL.md
Produces API reference documentation for Next.js APIs: functions, components, file conventions, directives, and config options.
1 project uses a version of this
twbs/bootstrap/.cursor/skills/bootstrap-release/SKILL.md
Cuts a Bootstrap release from version preparation through npm, GitHub, NuGet, and documentation deployment. Use when a maintainer asks to release, publish, or ship Bootstrap, including prereleases such as v6.0.0-alpha.1.
microsoft/vscode/src/vs/sessions/skills/vscode-ui/SKILL.md
Present metrics, comparisons, tables, bar charts, and expandable details as native visuals inside an Agents window response. Use when numbers or a comparison are clearer shown than described. Not for diagrams, mockups, or standalone documents.
microsoft/vscode/.github/skills/otel/SKILL.md
OpenTelemetry guidance for VS Code agent experiences. Use when changing Agent Host telemetry, local Copilot Chat telemetry, provider-native spans or metrics, OTel settings and managed policy, trace persistence/export, or monitoring documentation.
ruvnet/RuView/.claude/skills/agentdb-vector-search/SKILL.md
Implement semantic vector search with AgentDB for intelligent document retrieval, similarity matching, and context-aware querying. Use when building RAG systems, semantic search engines, or intelligent knowledge bases.
32 projects use a version of this
Often used withagent-code-review-swarmV3 DDD Architectureagent-test-long-runner
deepseek-ai/deepseek-harness/.agents/skills/dsh-prose-standard/SKILL.md
Use when writing, reviewing, restoring, trimming, or auditing prose in the deepseek-harness repo, including deciding where documentation or comments are required across Markdown, JSDoc, code and test comments, prompts, descriptions, diagnostics, and CLI or UI strings.
Often used withdsh-doc-site-syncdsh-doc-standards
n8n-io/n8n/.agents/skills/spec-driven-development/SKILL.md
Keeps implementation and specs in sync. Use when working on a feature that has a spec in .agents/specs/, when the user says /spec, or when starting implementation of a documented feature. Also use when the user asks to verify implementation against a spec or update a spec after changes.
paperclipai/paperclip/.agents/skills/release-changelog-discord-message/SKILL.md
Write the Discord announcement for a stable Paperclip release from the release changelog. Use when a release issue needs a copy-pasteable dotta-voice Discord post or refreshed discord_announcement document.
Steady15 mentions in 2 weeks
2 projects use a version of this
addyosmani/agent-skills/skills/source-driven-development/SKILL.md
Grounds every implementation decision in official documentation. Use when you want to verify an approach against the official docs before implementing it, or when you want authoritative, source-cited code free from outdated patterns. Use when building with any framework or library where correctness matters.
68 projects use a version of this
Often used withconstraint-driven-developmentincremental-implementationperformance-optimization
paperclipai/paperclip/skills/paperclip/SKILL.md
Use for Paperclip-managed tasks and heartbeats: reading task context, delivering task documents or files, updating completion or blockers, coordinating or delegating work, and following company governance. Includes control plane API operations for assignments, comments, approvals, and routines.
n8n-io/n8n/.agents/skills/env-var-docs/SKILL.md
Writes and reviews the JSDoc on `@Env(...)` config properties. The docs team extracts these comments from source into the public environment variable reference, so they are user documentation, not code comments. Use when adding or changing an `@Env` property, a config class, or reviewing a PR that touches one.
Surging+18 stars this week
1 project uses a version of this
anthropics/skills/skills/canvas-design/SKILL.md
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.
Rising4 mentions in 2 weeks
197 projects use a version of this
Often used withskill-shareartifacts-builderraffle-winner-picker
github/spec-kit/.github/skills/code-review/SKILL.md
Reviews Spec Kit code changes for consistency with applicable design documents, positive and negative test coverage, regression evidence for bug fixes, and consistent repository terminology. Use when reviewing a diff or pull request. Do not use for implementing changes or posting GitHub review actions.
Steady+42 stars this week
194 projects use a version of this
Often used withclose-specadd-new-modelcompare-screenshots
affaan-m/ECC/.agents/skills/investor-materials/SKILL.md
Create and update pitch decks, one-pagers, investor memos, accelerator applications, financial models, and fundraising materials. Use when the user needs investor-facing documents, projections, use-of-funds tables, milestone plans, or materials that must stay internally consistent across multiple fundraising assets.
Steady12 mentions in 2 weeks
40 projects use a version of this
Often used withbrand-discoveryconfigure-eccralphinho-rfc-pipeline
affaan-m/ECC/.cursor/skills/investor-materials/SKILL.md
Create and update pitch decks, one-pagers, investor memos, accelerator applications, financial models, and fundraising materials. Use when the user needs investor-facing documents, projections, use-of-funds tables, milestone plans, or materials that must stay internally consistent across multiple fundraising assets.
Steady12 mentions in 2 weeks
40 projects use a version of this
Often used withbrand-discoveryconfigure-eccralphinho-rfc-pipeline
mattpocock/skills/skills/engineering/code-review/SKILL.md
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to \"review since X\".
Rising8 mentions in 2 weeks
194 projects use a version of this
Often used withclose-specadd-new-modelcompare-screenshots
supabase/supabase/.agents/skills/review-the-docs/SKILL.md
Review Supabase docs changes locally in your `supabase/supabase` checkout — either an open PR (triage, classify, verify) or your own branch before opening a PR (local self-review). Covers markdown pipeline, MDX content, tutorials, examples, Studio links, and docs tooling. Use when asked to review docs PRs, self-review a draft branch, check who has approved, verify build output, or evaluate supabase/supabase documentation changes.
No other project uses it yet
microsoft/playwright/.claude/skills/api-review/SKILL.md
Produce the "Playwright 1.xx API Review" artifact for a range of commits - the public API additions and the breaking or behavior changes that affect existing users since the last API review or since the last release, ordered by impact, each with links, before/after snippets and a documentation check. Covers microsoft/playwright (Node.js) and the Python, Java and .NET ports. Use when asked for an API review, to review API changes, or to check what changed in the public API since a release or since the last review.
addyosmani/agent-skills/skills/spec-driven-development/SKILL.md
Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when drafting a PRD or requirements document with objectives and scope, or when requirements are unclear, ambiguous, or only exist as a vague idea. Use when a single requirement spans several independently testable capabilities and needs decomposing into a capability map of modules before specifying. Use when evolving a shipped spec — scoping a V1, deferring ideas to a V2 backlog, or writing a follow-up spec for a change to an existing feature.
Often used withusing-agent-skillsconstraint-driven-developmentobservability-and-instrumentation
microsoft/PowerToys/.github/skills/release-note-generation/SKILL.md
Toolkit for generating PowerToys stable or preview release notes from GitHub milestones, commit ranges, or Azure DevOps release-candidate builds. Prepare draft preview releases with three-component GitHub tags while preserving four-component build and asset versions. Use when asked to create release notes, summarize milestone PRs, generate changelog, prepare a draft preview release, calculate PR deltas across main and stable, update release documentation, manage PR milestones, or prepare and validate release assets.
No other project uses it yet
A folder with a SKILL.md file: a name, a description of when to use it, and instructions. Claude loads a skill only when the task matches its description.
Copy the folder into your project's .claude/skills/ directory, or into your own skills folder to use it everywhere.
We read each file for commands that read secrets, delete things or pipe downloads into a shell, and say so before you copy it. No warning is not a promise that a file is safe.
Open a skill to see its discussion. Reports from people and their agents are coming.