Claude Skills
The open format is called Agent Skills and works in Claude Code, Codex, Cursor and other agents — most people know it as Claude Skills.
Every Agent Skill we could find on GitHub, deduplicated by content. 86 696 files from 2 113 authors, of which 68 413 are unique — the rest is the same skill repackaged into someone else's repository. For each one: what it weighs in tokens, whether it ships runnable scripts, and which MCP servers it needs.
Workflow for auditing, designing, and writing structured documentation based on the Diátaxis Framework (Tutorials, How-to, Reference, Explanation).
Helps interrogate Product Requirements (PRD), Technical Specifications, and Implementation Plans to find ambiguities, missing edge cases, and hidden assumptions.
Systematic codebase exploration, architectural critique, and generation of Project Discovery Drafts for SDLC Phase 0.
Language-agnostic workflow for code reviews and security audits using a Two-Axis (Standards vs Spec) approach against Clean Code/SOLID principles, generating formal refactoring plans.
God Mode Developer - God-Tier Autonomous Engineer for Coding/Implementation (Phase 6). Executes code strictly based on /spec/ and /plan/.
Grill the user relentlessly about a plan or design. Use when the user wants to stress-test a plan before building, or uses any 'grill' trigger phrases.
Generates formal, structured, and executable implementation plan documents based on specifications.
Scans, analyzes, and documents the existing repository architecture, directories, and file purposes into docs/ARCHITECTURE.md.
Workflow to generate a comprehensive Product Requirements Document (PRD) detailing user stories, acceptance criteria, technical considerations, and metrics.
Standardized workflow for discovering, reading, writing, and compacting the project's memory file (memory.instructions.md) to persist context across AI chat sessions, with a permanent Knowledge Base for cross-session decisions and lessons learned.
Performs consistency and traceability audits across documents (PRD vs Spec vs Plan) to detect missing coverage and scope creep.
Generates or updates highly detailed, machine-readable technical specification documents in the /spec/ directory.
Systematic codebase exploration, architectural critique, and generation of Project Discovery Drafts for SDLC Phase 0.
Helps interrogate Product Requirements (PRD), Technical Specifications, and Implementation Plans to find ambiguities, missing edge cases, and hidden assumptions.
Workflow for analyzing bug reports, tracing root causes, and generating structured bug-fix implementation plans with rollback strategies.
Workflow for auditing, designing, and writing structured documentation based on the Diátaxis Framework (Tutorials, How-to, Reference, Explanation).
Language-agnostic workflow for code reviews and security audits using a Two-Axis (Standards vs Spec) approach against Clean Code/SOLID principles, generating formal refactoring plans.
God Mode Developer - God-Tier Autonomous Engineer for Coding/Implementation (Phase 6). Executes code strictly based on /spec/ and /plan/.
Grill the user relentlessly about a plan or design. Use when the user wants to stress-test a plan before building, or uses any 'grill' trigger phrases.
Standardized workflow for discovering, reading, writing, and compacting the project's memory file (memory.instructions.md) to persist context across AI chat sessions, with a permanent Knowledge Base for cross-session decisions and lessons learned.
Generates formal, structured, and executable implementation plan documents based on specifications.
Workflow to generate a comprehensive Product Requirements Document (PRD) detailing user stories, acceptance criteria, technical considerations, and metrics.
Scans, analyzes, and documents the existing repository architecture, directories, and file purposes into docs/ARCHITECTURE.md.
Generates or updates highly detailed, machine-readable technical specification documents in the /spec/ directory.
Systematic codebase exploration, architectural critique, and generation of Project Discovery Drafts for SDLC Phase 0.
Performs consistency and traceability audits across documents (PRD vs Spec vs Plan) to detect missing coverage and scope creep.
Workflow for analyzing bug reports, tracing root causes, and generating structured bug-fix implementation plans with rollback strategies.
Helps interrogate Product Requirements (PRD), Technical Specifications, and Implementation Plans to find ambiguities, missing edge cases, and hidden assumptions.
God Mode Developer - God-Tier Autonomous Engineer for Coding/Implementation (Phase 6). Executes code strictly based on /spec/ and /plan/.
Language-agnostic workflow for code reviews and security audits using a Two-Axis (Standards vs Spec) approach against Clean Code/SOLID principles, generating formal refactoring plans.
Workflow for auditing, designing, and writing structured documentation based on the Diátaxis Framework (Tutorials, How-to, Reference, Explanation).
Grill the user relentlessly about a plan or design. Use when the user wants to stress-test a plan before building, or uses any 'grill' trigger phrases.
Standardized workflow for discovering, reading, writing, and compacting the project's memory file (memory.instructions.md) to persist context across AI chat sessions, with a permanent Knowledge Base for cross-session decisions and lessons learned.
Workflow to generate a comprehensive Product Requirements Document (PRD) detailing user stories, acceptance criteria, technical considerations, and metrics.
Generates or updates highly detailed, machine-readable technical specification documents in the /spec/ directory.
Generates formal, structured, and executable implementation plan documents based on specifications.
Scans, analyzes, and documents the existing repository architecture, directories, and file purposes into docs/ARCHITECTURE.md.
Systematic codebase exploration, architectural critique, and generation of Project Discovery Drafts for SDLC Phase 0.
Performs consistency and traceability audits across documents (PRD vs Spec vs Plan) to detect missing coverage and scope creep.
Workflow for auditing, designing, and writing structured documentation based on the Diátaxis Framework (Tutorials, How-to, Reference, Explanation).
Helps interrogate Product Requirements (PRD), Technical Specifications, and Implementation Plans to find ambiguities, missing edge cases, and hidden assumptions.
Language-agnostic workflow for code reviews and security audits using a Two-Axis (Standards vs Spec) approach against Clean Code/SOLID principles, generating formal refactoring plans.
Workflow for analyzing bug reports, tracing root causes, and generating structured bug-fix implementation plans with rollback strategies.
God Mode Developer - God-Tier Autonomous Engineer for Coding/Implementation (Phase 6). Executes code strictly based on /spec/ and /plan/.
Grill the user relentlessly about a plan or design. Use when the user wants to stress-test a plan before building, or uses any 'grill' trigger phrases.
Standardized workflow for discovering, reading, writing, and compacting the project's memory file (memory.instructions.md) to persist context across AI chat sessions, with a permanent Knowledge Base for cross-session decisions and lessons learned.
Workflow to generate a comprehensive Product Requirements Document (PRD) detailing user stories, acceptance criteria, technical considerations, and metrics.
Generates formal, structured, and executable implementation plan documents based on specifications.
Scans, analyzes, and documents the existing repository architecture, directories, and file purposes into docs/ARCHITECTURE.md.
Generates or updates highly detailed, machine-readable technical specification documents in the /spec/ directory.
An advanced, autonomous AI agent skill designed to execute complex, multi-step, and long-horizon tasks with high reliability and minimal human interruption.
Grill the user relentlessly about a plan or design. Use when the user wants to stress-test a plan before building, or uses any 'grill' trigger phrases.
Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.
Standardized workflow for discovering, reading, writing, and compacting the project's memory file (memory.instructions.md) to persist context across AI chat sessions, with a permanent Knowledge Base for cross-session decisions and lessons learned.
Omni-expert principal software architect. Triggers on requests for app development, coding, refactoring, or architectural design. Enforces clean code, clean architecture, deep reasoning, mandatory testing, and strict anti-ambiguity protocols.
Performs consistency and traceability audits across documents (PRD vs Spec vs Plan) to detect missing coverage and scope creep.
> Applies the "lazy senior developer" mindset. Use this skill whenever generating, modifying, reviewing code, or fixing bugs to prioritize code reuse, minimalism, YAGNI principles, and root-cause fixes. Supports for over-engineering review (ponytail-review), repo-wide audit (ponytail-audit), and debt tracking (ponytail-debt).
Workflow for analyzing bug reports, tracing root causes, and generating structured bug-fix implementation plans with rollback strategies.
Language-agnostic workflow for code reviews and security audits using a Two-Axis (Standards vs Spec) approach against Clean Code/SOLID principles, generating formal refactoring plans.
Helps interrogate Product Requirements (PRD), Technical Specifications, and Implementation Plans to find ambiguities, missing edge cases, and hidden assumptions.
Claude Skills — questions
Answers built from the skills we actually parsed.