addyosmani/agent-skills

Last imported 1w ago

ChangedOct 21, 2026

The source has changed since this result was produced. The evidence may not reflect the current state.

Upstreamaeac41d4

In Vettd Directory

Skills Assessed

Graded A or B

Graded C or F

With a Vettd Note

Skills Assessed

planning-and-task-breakdown

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.

Up to date

1 finding: 0 critical, 0 medium

Best forteams who want on-demand domain depth with low ambient token overhead

Not forenforced end-to-end process: nothing mandates skill ordering

idea-refine

Refines raw ideas into sharp, actionable concepts through structured divergent and convergent thinking. Use when an idea is still vague, when you need to stress-test assumptions before committing to a plan, or when you want to expand options before converging on one. Triggers on "ideate", "refine this idea", or "stress-test my plan".

Up to date

1 finding: 0 critical, 0 medium

Best forteams who want on-demand domain depth with low ambient token overhead

Not forenforced end-to-end process: nothing mandates skill ordering

source-driven-development

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.

Up to date

3 findings: 1 critical, 1 medium

Best forteams who want on-demand domain depth with low ambient token overhead

Not forenforced end-to-end process: nothing mandates skill ordering

spec-driven-development

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.

Up to date

1 finding: 0 critical, 0 medium

Best forteams who want on-demand domain depth with low ambient token overhead

Not forenforced end-to-end process: nothing mandates skill ordering

incremental-implementation

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.

Up to date

1 finding: 0 critical, 0 medium

Best forteams who want on-demand domain depth with low ambient token overhead

Not forenforced end-to-end process: nothing mandates skill ordering

documentation-and-adrs

Records decisions and documentation. Use when you need to document an architecture decision (ADR) or the reasoning behind a design choice, when changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.

Up to date

1 finding: 0 critical, 0 medium

Best forteams who want on-demand domain depth with low ambient token overhead

Not forenforced end-to-end process: nothing mandates skill ordering

shipping-and-launch

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.

Up to date

1 finding: 0 critical, 0 medium

Best forteams who want on-demand domain depth with low ambient token overhead

Not forenforced end-to-end process: nothing mandates skill ordering

api-and-interface-design

Guides stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints, defining type contracts between modules, or establishing boundaries between frontend and backend.

Up to date

1 finding: 0 critical, 0 medium

Best forteams who want on-demand domain depth with low ambient token overhead

Not forenforced end-to-end process: nothing mandates skill ordering

using-agent-skills

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.

Up to date

1 finding: 0 critical, 0 medium

Best forteams who want on-demand domain depth with low ambient token overhead

Not forenforced end-to-end process: nothing mandates skill ordering

frontend-ui-engineering

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.

Up to date

1 finding: 0 critical, 0 medium

Best forteams who want on-demand domain depth with low ambient token overhead

Not forenforced end-to-end process: nothing mandates skill ordering

debugging-and-error-recovery

Guides systematic root-cause debugging. Use when tests fail, builds break, something that worked yesterday broke, behavior doesn't match expectations, or you encounter any unexpected error. Use when you need to figure out what broke and why — a systematic approach to finding and fixing the root cause rather than guessing.

Up to date

1 finding: 0 critical, 0 medium

Best forteams who want on-demand domain depth with low ambient token overhead

Not forenforced end-to-end process: nothing mandates skill ordering

observability-and-instrumentation

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.

Up to date

1 finding: 0 critical, 0 medium

Best forteams who want on-demand domain depth with low ambient token overhead

Not forenforced end-to-end process: nothing mandates skill ordering

context-engineering

Optimizes agent context setup. Use when starting a new session, when agent output quality degrades, when switching between tasks, or when you need to configure rules files and context for a project.

Up to date

1 finding: 0 critical, 0 medium

Best forteams who want on-demand domain depth with low ambient token overhead

Not forenforced end-to-end process: nothing mandates skill ordering

ci-cd-and-automation

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.

Up to date

1 finding: 0 critical, 0 medium

Best forteams who want on-demand domain depth with low ambient token overhead

Not forenforced end-to-end process: nothing mandates skill ordering

deprecation-and-migration

Manages deprecation and migration. Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another. Use when migrating a database schema in production, such as renaming or dropping a column without downtime (expand/contract). Use when deciding whether to maintain or sunset existing code.

Up to date

1 finding: 0 critical, 0 medium

Best forteams who want on-demand domain depth with low ambient token overhead

Not forenforced end-to-end process: nothing mandates skill ordering

code-simplification

Simplifies code for clarity. Use when refactoring code for clarity without changing behavior. Use when code works but is harder to read, maintain, or extend than it should be. Use when reviewing code that has accumulated unnecessary complexity.

Up to date

2 findings: 0 critical, 1 medium

Best forteams who want on-demand domain depth with low ambient token overhead

Not forenforced end-to-end process: nothing mandates skill ordering

git-workflow-and-versioning

Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, splitting uncommitted work in a messy working tree into clean atomic commits, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump, tagging, or writing a changelog.

Up to date

1 finding: 0 critical, 0 medium

Best forteams who want on-demand domain depth with low ambient token overhead

Not forenforced end-to-end process: nothing mandates skill ordering

interview-me

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.

Up to date

1 finding: 0 critical, 0 medium

Best forteams who want on-demand domain depth with low ambient token overhead

Not forenforced end-to-end process: nothing mandates skill ordering

browser-testing-with-devtools

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.

Up to date

4 findings: 2 critical, 1 medium

Best forteams who want on-demand domain depth with low ambient token overhead

Not forenforced end-to-end process: nothing mandates skill ordering

performance-optimization

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.

Up to date

1 finding: 0 critical, 0 medium

Best forteams who want on-demand domain depth with low ambient token overhead

Not forenforced end-to-end process: nothing mandates skill ordering

test-driven-development

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 and the request does not mention tests.

Up to date

1 finding: 0 critical, 0 medium

Best forteams who want on-demand domain depth with low ambient token overhead

Not forenforced end-to-end process: nothing mandates skill ordering

doubt-driven-development

Subjects every non-trivial decision to a fresh-context adversarial review before it stands. Use when you want every assumption cross-examined before proceeding, when stress-testing a plan for hidden failure modes, when correctness matters more than speed, when working in unfamiliar code, when stakes are high (production auth, security-sensitive logic, a high-stakes migration, irreversible operations), or any time a confident output would be cheaper to verify now than to debug later.

Up to date

1 finding: 0 critical, 0 medium

Best forteams who want on-demand domain depth with low ambient token overhead

Not forenforced end-to-end process: nothing mandates skill ordering

code-review-and-quality

Conducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensions before it enters the main branch. Use when asked to review a diff or a pull request, even when the diff is pasted inline.

Up to date

1 finding: 0 critical, 0 medium

Best forteams who want on-demand domain depth with low ambient token overhead

Not forenforced end-to-end process: nothing mandates skill ordering

/ Ship your skills

Import your repository to get your skills certified and listed.

Submit skills →