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.
JuliusBrusseeSkillJuliusBrussee/caveman/skills/caveman-evidence-review/SKILL.md
Read-only review of Caveman Cloud evidence: cost, Cave Score, workflows, traces, latency, errors, routing, savings. Use when asked what Caveman found or where LLM spend goes.
Steady22 mentions in 2 weeks
10 projects use a version of this
JuliusBrusseeSkillJuliusBrussee/caveman/skills/caveman-help/SKILL.md
Quick-reference card for the three caveman skills and their commands. Trigger: /caveman-help or "caveman help".
JuliusBrusseeSkillJuliusBrussee/caveman/skills/caveman-learn/SKILL.md
Act on a Caveman learn report - review the ranked token sinks, apply cost-lowering fixes with per-edit consent, and report what those fixes returned. Use when asked to lower an agent's token cost, what caveman has saved, to trim a heavy CLAUDE.md, or to offload re-pasted context into cavemem.
Steady22 mentions in 2 weeks
10 projects use a version of this
JuliusBrusseeSkillJuliusBrussee/caveman/skills/caveman-manage/SKILL.md
Inspect Caveman Cloud's experiment lifecycle and block unsafe execution. Use when asked to start, approve, cancel, promote or roll back a Caveman experiment.
Steady22 mentions in 2 weeks
10 projects use a version of this
addyosmaniSkilladdyosmani/agent-skills/skills/browser-testing-with-devtools/SKILL.md
Tests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data. Requires the chrome-devtools MCP server to be configured.
61 projects use a version of this
Often used withdeprecation-and-migrationconstraint-driven-developmentdoubt-driven-development
addyosmaniReads credentialsSkilladdyosmani/agent-skills/skills/ci-cd-and-automation/SKILL.md
Automates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.
67 projects use a version of this
Often used withdeprecation-and-migrationconstraint-driven-developmentdoubt-driven-development
addyosmaniSkilladdyosmani/agent-skills/skills/constraint-driven-development/SKILL.md
Establishes a project's quality bar as a written contract and stops agents quietly lowering it. Interviews the user on which dimensions matter, supplies sane default thresholds when they have no number in mind, records everything in CONSTRAINTS.md, and watches the diff for a weakened bar — new @ts-ignore or eslint-disable suppressions, skipped or deleted tests, assertions stripped out, unimplemented stubs, thresholds edited down. Use when no quality bar is written down, when the user says "set up constraints" or "define our standards", when the user wants dimensions they care about — accessibility, web performance, coverage — set up as enforced constraints, when an agent keeps silencing checks or skipping tests to get to green, when you need a coverage or performance threshold and don't know what number to pick, or when an agent writes more code than anyone will read.
Often used withobservability-and-instrumentationusing-agent-skillsgit-workflow-and-versioning
addyosmaniReads credentialsSkilladdyosmani/agent-skills/skills/documentation-and-adrs/SKILL.md
Records decisions and documentation, and detects when documentation has drifted from the code it describes. Use when you need to document an architecture decision (ADR) or the reasoning behind a design choice, when changing public APIs, shipping features, when docs may be stale or out of sync with the code they describe, when working out which module docs are still accurate, or when setting up a check so docs cannot silently go out of date again.
Often used withconstraint-driven-developmentdeprecation-and-migrationdoubt-driven-development
addyosmaniSkilladdyosmani/agent-skills/skills/frontend-ui-engineering/SKILL.md
Builds production-quality, accessible, responsive user-facing UIs. Use when building or modifying interfaces and pages, creating components, implementing layouts, meeting WCAG accessibility requirements, managing state, or when the output needs to look and feel production-quality rather than AI-generated.
Often used withobservability-and-instrumentationconstraint-driven-developmentdoubt-driven-development
addyosmaniReads credentialsSkilladdyosmani/agent-skills/skills/incremental-implementation/SKILL.md
Delivers changes incrementally in thin, verifiable slices. Use when implementing any feature or change that touches more than one file, or when picking up the next task from a plan. Use when rolling a change out behind a feature flag, when you're about to write a large amount of code at once, or when a task feels too big to land in one step.
74 projects use a version of this
Often used withconstraint-driven-developmentdeprecation-and-migrationdoubt-driven-development
addyosmaniSkilladdyosmani/agent-skills/skills/interview-me/SKILL.md
Extracts what the user actually wants instead of what they think they should want. Achieves this through one-question-at-a-time interview until ~95% confidence about the underlying intent. Use when an ask is underspecified ("build me X" without "for whom" or "why now"), when the user explicitly invokes ("interview me", "grill me", "are we sure?", "stress-test my thinking"), or when you catch yourself silently filling in ambiguous requirements before any plan, spec, or code exists.
98 projects use a version of this
Often used withconstraint-driven-developmentidea-refineobservability-and-instrumentation
addyosmaniReads credentialsSkilladdyosmani/agent-skills/skills/observability-and-instrumentation/SKILL.md
Instruments code so production behavior is visible and diagnosable. Use when adding logging, metrics, tracing, or alerting. Use when shipping any feature that runs in production and you need evidence it works. Use when production issues are reported but you can't tell what happened from the available data.
46 projects use a version of this
Often used withconstraint-driven-developmentincremental-implementationperformance-optimization
addyosmaniSkilladdyosmani/agent-skills/skills/performance-optimization/SKILL.md
Optimizes application performance across frontend, backend, queries, and databases. Use when performance requirements exist, when you suspect performance regressions, when Core Web Vitals or load times need improvement, when N+1 query patterns need fixing, or when profiling reveals bottlenecks.
125 projects use a version of this
Often used withconstraint-driven-developmentgit-workflow-and-versioningdeprecation-and-migration
addyosmaniSkilladdyosmani/agent-skills/skills/planning-and-task-breakdown/SKILL.md
Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.
Often used withconstraint-driven-developmentdeprecation-and-migrationdoubt-driven-development
addyosmaniReads credentialsSkilladdyosmani/agent-skills/skills/security-and-hardening/SKILL.md
Hardens code against vulnerabilities. Use when auditing an input handler for vulnerabilities, when handling user input, authentication, data storage, or external integrations, or when checking a login flow is safe against the OWASP Top Ten. Use when building any feature that accepts untrusted data, manages user sessions or session cookies, or interacts with third-party services. Use when auditing dependencies for known vulnerabilities, triaging package-manager audit findings, or assessing supply-chain risk in a new package. Use when personal data or privacy compliance (GDPR, CCPA) is involved.
Often used withconstraint-driven-developmentobservability-and-instrumentationdoubt-driven-development
addyosmaniSkilladdyosmani/agent-skills/skills/shipping-and-launch/SKILL.md
Prepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.
65 projects use a version of this
Often used withobservability-and-instrumentationconstraint-driven-developmentdoubt-driven-development
addyosmaniSkilladdyosmani/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
addyosmaniSkilladdyosmani/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
addyosmaniSkilladdyosmani/agent-skills/skills/test-driven-development/SKILL.md
Drives development with tests using the red-green-refactor loop. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality. Use when asked to add tests to a function, fix a bug in it or change its behavior, even when the code is pasted inline, the request does not mention tests and the answer looks obvious from reading it. The skill writes the failing test first and changes the function second, never the change alone.
Often used withchinese-code-reviewdiagnosing-superpowersusing-agent-skills
addyosmaniSkilladdyosmani/agent-skills/skills/using-agent-skills/SKILL.md
Discovers and invokes agent skills. Use when starting a session, or when you need to decide which skill or workflow applies to the piece of work at hand. This is the meta-skill that governs how all other skills are discovered and invoked.
49 projects use a version of this
Often used withconstraint-driven-developmentobservability-and-instrumentationdoubt-driven-development
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.
