Sponsored by

Find leads on Reddit on auto pilot

Agent skills

Skills you can use with AI coding agents, indexed from public GitHub repositories.

Latest Most Popular

method:research-to-implementation Artifact-driven method for taking a significant feature from idea to shipped code. 10 steps across 5 phases: Alignment → Evidence → Decision → Preflight → Delivery. Use when the user describes a non-trivial feature that needs research, design, and implementation — not for bug fixes, single-file changes, or quick wiring tasks.
petekp/claude-code-setup 20
literate-guide Create a narrative guide to a codebase or feature in the style of Knuth's Literate Programming — code and prose interwoven as a single essay, ordered for human understanding rather than compiler needs. Use when the user asks to 'explain this codebase as a story', 'write a literate guide', 'create a narrative walkthrough', 'tell the story of this code', 'Knuth-style documentation', 'weave a guide for this feature', or when they want deep, readable documentation that treats the program as literature. Also trigger when someone wants a document that a thoughtful reader could follow from start to finish and come away understanding both WHAT the code does and WHY every design choice was made.
petekp/claude-code-setup 20
method:dry-run Validate a Claude Code method skill for mechanical soundness by dry-running a concrete feature through every step. Use when you need to dry run, validate a method, trace a method skill, check mechanical soundness, or verify that a method's setup, paths, commands, artifact chains, headers, templates, gates, and topology are wired correctly. Invoke this after authoring or editing any method skill, and before trusting it for real work.
petekp/claude-code-setup 20
exhaustive-systems-analysis Perform evidence-driven, multi-subsystem audits of real codebases to find correctness bugs, race conditions, security gaps, stale documentation, dead code, and production-readiness risks. Use when asked to audit a system end-to-end, verify agent-written code before shipping, analyze a subsystem for correctness across multiple modules, or produce a structured risk report for a real implementation. Prefer other skills for a single isolated bug, a proposal or document review, or a dedicated dead-code cleanup.
petekp/claude-code-setup 20
method:decision-pressure-loop Architecture decision workflow for choosing between meaningful architectural or protocol options under uncertainty before implementation begins. 8 steps across 5 phases: Framing -> Reality Mapping -> Option Exploration -> Pressure -> Publication. Use when the team needs a defensible decision with explicit tradeoffs, reopen conditions, and implementation-facing guidance — not when the goal is already code delivery.
petekp/claude-code-setup 20
method:janitor Artifact-centric method for systematic codebase cleanup — dead code, stale docs, orphaned artifacts, vestigial comments, and redundant abstractions. 8 steps across 5 phases: Survey -> Triage -> Prove -> Clean -> Verify. Dual-mode: interactive (user checkpoints) or autonomous (evidence-gated with deferred review). Use when asked to clean up dead code, do a janitor sweep, improve context hygiene for agents, remove stale docs, or find and remove unused code. Do not use for refactoring with behavior changes, architecture decisions, feature work, one-off deletions, dependency upgrades, or formatting cleanup.
petekp/claude-code-setup 20
research-prompt Craft a high-quality prompt for a deep research agent (like ChatGPT Deep Research) through adaptive interviewing. Use when the user wants to research something but needs help formulating what to ask — when they say "I need to research X", "help me figure out what to ask about Y", "write a research prompt for Z", "I want to use deep research on...", or when they have a vague research need and want a precise, comprehensive prompt that will get excellent results from a research agent. Also use when the user mentions deep research, ChatGPT research, or preparing a query for an AI research tool.
petekp/claude-code-setup 20
seam-ripper Ruthlessly analyze architectural seams—the interfaces, boundaries, and contracts between system components—to expose coupling problems, abstraction leaks, and design failures. Use when asked to review architecture, analyze coupling, find interface problems, improve module boundaries, audit dependencies, or redesign system structure. Produces uncompromising redesign proposals that prioritize correctness over backwards compatibility.
petekp/claude-code-setup 20
deep-research Conduct exhaustive, citation-rich research on any topic using all available tools: web search, browser automation, documentation APIs, and codebase exploration. Use when asked to "research X", "find out about Y", "investigate Z", "deep dive into...", "what's the current state of...", "compare options for...", "fact-check this...", or any request requiring comprehensive, accurate information from multiple sources. Prioritizes accuracy over speed, cross-references claims across sources, identifies conflicts, and provides full citations. Outputs structured findings with confidence levels and source quality assessments.
petekp/claude-code-setup 20
pipeline Modular development pipeline orchestrator. Use for "/pipeline", "pipeline init", "pipeline resume", "pipeline status", or phased triage → align → execute workflows.
petekp/claude-code-setup 20
vercel-react-best-practices React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
petekp/claude-code-setup 20
dead-code-sweep This skill should be used when cleaning up codebases that have accumulated dead code, redundant implementations, and orphaned artifacts — especially codebases maintained by coding agents. Triggers on "find dead code", "clean up unused code", "remove redundant code", "prune this codebase", "dead code sweep", "code cleanup", or when a codebase has gone through multiple agent-driven refactors and likely contains overlooked remnants. Systematically identifies cruft, categorizes findings, and removes confirmed dead code with user approval.
petekp/claude-code-setup 20
improve-codebase-architecture Explore a codebase to find opportunities for architectural improvement, focusing on making the codebase more testable by deepening shallow modules. Use when user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more AI-navigable.
petekp/claude-code-setup 20
method:create Codex-powered compiler for turning a natural-language workflow description into a method skill that matches the live corpus. 5 phases: Intake -> Analysis -> Authoring -> Validation -> Refinement. Codex workers handle analysis, file generation, and quality gate; Claude does intake and a final refinement pass optimized for Claude Code. Use when you want to create a method, compile a method, author a method skill, or turn this workflow into a method. Not for editing existing methods, not a runtime engine, and not for one-off prompts.
petekp/claude-code-setup 20
method:router Routes `/method:router` requests to the best-fit method skill among the 7 methods. Not a method itself. Use for `/method:router` or `/method:router <args>` when choosing which method to start.
petekp/claude-code-setup 20
deepwiki Query DeepWiki for repository documentation and structure. Use to understand open source projects, find API docs, and explore codebases.
petekp/claude-code-setup 20
prd-to-issues Break a PRD into independently-grabbable GitHub issues using tracer-bullet vertical slices. Use when user wants to convert a PRD to issues, create implementation tickets, or break down a PRD into work items.
petekp/claude-code-setup 20
architecture-scaffold Build a compilable type-level skeleton from a high-level architecture spec before writing any implementation logic. Use when you have an architectural assessment, design doc, or restructuring plan and need to prove the new architecture is sound before migrating code. Also use when asked to "scaffold the new architecture", "create type stubs", "build the shell", "flesh out this spec", "skeleton the modules", or any request to turn architectural intent into verified structure. This skill follows the "Human Builds the Shell" paradigm: types are hard constraints that the compiler enforces, so if the skeleton compiles, the architecture is structurally sound. Especially valuable for large refactors where you don't trust agents to maintain coherence.
petekp/claude-code-setup 20
formal-verify Continuous formal verification of architectural constraints and code quality. Use when asked to verify, audit, or validate codebase integrity. Runs automatically via hooks on every edit (structural) and pre-commit (full). Catches ownership violations, boundary crossings, state machine bugs, and code smells that grep ratchets miss. Triggers: "verify", "formal verify", "check architecture", "audit code quality", "run verification", "/verify", "/verify --bootstrap", "/verify --grade".
petekp/claude-code-setup 20
write-a-prd Create a PRD through user interview, codebase exploration, and module design, then submit as a GitHub issue. Use when user wants to write a PRD, create a product requirements document, or plan a new feature.
petekp/claude-code-setup 20
agentation Add Agentation visual feedback toolbar to a Next.js project
petekp/claude-code-setup 20
skill-manager Manage, audit, and maintain your skill ecosystem. Use when the user asks to "check my skills", "audit skills", "find duplicate skills", "which skills am I using", "prune unused skills", "are my skills synced", "check for skill updates", "skill report", "skill health", or mentions skill maintenance, cleanup, or organization.
petekp/claude-code-setup 20
grill-me Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
petekp/claude-code-setup 20
claude-md-author This skill should be used when the user asks to "create a CLAUDE.md", "write a CLAUDE.md", "set up CLAUDE.md", "configure Claude for this project", "add project instructions for Claude", "initialize Claude context", or mentions needing project-specific Claude instructions.
petekp/claude-code-setup 20