Skip to content
SkillCheatSheet Sign in

addyosmani/agent-skills

Agent skills in the GitHub repository addyosmani/agent-skills, each with its code score out of 100.

Production-grade engineering skills for AI coding agents.

Repository score
80 / 100 B
Skills
25
Verified
9
Average skill score
76
GitHub stars
116,263
License
MIT

Open addyosmani/agent-skills on GitHub

25 skills in this repository

  1. constraint-driven-development

    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 wh…

    Verified91A
  2. 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 underlyin…

    Verified86A
  3. 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 acc…

    Verified83B
  4. 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-testin…

    Verified81B
  5. 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…

    Verified81B
  6. 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…

    Verified80B
  7. 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 feat…

    Verified80B
  8. 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 a…

    Verified80B
  9. 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…

    Verified80B
  10. 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 con…

    79B
  11. 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 pla…

    79B
  12. performance-optimization

    Optimizes application performance across frontend, backend, queries, and databases. Use when performance requirements exist, when you suspect performance regressions, when Core We…

    78B
  13. 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 authori…

    78B
  14. 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 wo…

    78B
  15. 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 ac…

    76B
  16. 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 b…

    75B
  17. security-and-hardening

    Hardens code against vulnerabilities. Use when auditing an input handler for vulnerabilities, when handling user input, authentication, data storage, or external integrations, or…

    74B
  18. 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 unexpec…

    73B
  19. 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 sch…

    73B
  20. 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 cl…

    73B
  21. 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 th…

    71B
  22. 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 esta…

    69C
  23. 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, analy…

    68C
  24. 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…

    66C
  25. 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 b…

    59C

Scores come from a snapshot of 300 public GitHub repositories taken on 12 November 2026. Every score is the result of fixed checks run by code; no AI is involved. How scoring works.