skills

In the author's own words, from each skill's SKILL.md — showing the first 30 of 35 files.

• ablate-ai-layer

  Measure whether a repository's AI instructions still earn their place, by running the same real task many times with the layer intact and with it stripped, then grading every rule against what actually changed. Runs both arms itself in throwaway git worktrees and never touches the working tree. Agent-agnostic across CLAUDE.md, AGENTS.md, .claude/, .agents/, .cursor/rules, .clinerules, .windsurfru…

  .claude/skills/ablate-ai-layer/SKILL.md on GitHub (opens in a new tab)

• agent-browser

  Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to…

  .claude/skills/agent-browser/SKILL.md on GitHub (opens in a new tab)

• ast-grep

  Guide for writing ast-grep rules to perform structural code search and analysis. Use when users need to search codebases using Abstract Syntax Tree (AST) patterns, find specific code structures, or perform complex code queries that go beyond simple text search. This skill should be used when users ask to search for code patterns, find specific language constructs, or locate code with particular s…

  .claude/skills/ast-grep/SKILL.md on GitHub (opens in a new tab)

• build-dark-factory

  Take a PRD and build a dark factory around it - a repository that takes work in as an issue and ships validated code out with nobody at the keyboard - one component at a time, into the user's actual repo. Covers the five components in construction order - the guidance layer, the validation harness, the workflow-driven repo, deployment, and the trigger that makes it autonomous - and is agnostic ab…

  .claude/skills/build-dark-factory/SKILL.md on GitHub (opens in a new tab)

• drive-screen

  Take real control of the desktop - list and focus windows, type, paste, click, scroll, and screenshot - on Windows, macOS or Linux, and drive other coding-agent sessions running in terminals. Use when asked to set up the screen or the day, open and arrange a set of apps or repos, prepare or run a live demo before recording, test a desktop application that has no headless harness, launch or steer…

  .claude/skills/drive-screen/SKILL.md on GitHub (opens in a new tab)

• hooks-create

  Author a working Claude Code hook from a plain-English description of what it should guarantee or do. You describe the behavior ("never let the agent edit my migrations", "don't stop until the tests pass", "log every command"); this skill picks the right lifecycle event, writes the hook script, and wires it into .claude/settings.json. Use when you want a deterministic guarantee or automation in y…

  .claude/skills/hooks-create/SKILL.md on GitHub (opens in a new tab)

• opportunity-scan

  Scan how you actually work with your coding agent and surface what to encode next. Point it at ONE run's artifacts to find what would have prevented a specific failure (the reactive loop — 'that went wrong, what should change in the AI layer?'), or at a window of session logs to find recurring patterns worth building (the proactive scan). Agent-agnostic. Outputs a shape-only HTML report. Use to e…

  .claude/skills/opportunity-scan/SKILL.md on GitHub (opens in a new tab)

• piv-commit

  Creates a new git commit for all uncommitted changes with an atomic, conventionally-tagged message. Use when work is complete and ready to be committed.

  .claude/skills/piv-commit/SKILL.md on GitHub (opens in a new tab)

• piv-create-pr

  Push the current feature branch and open a pull request, ready for review. Use after a ticket's implementation is committed on its own branch — it detects the base branch, pushes, opens the PR with a clear body (summary · what changed · validation status), and returns the URL to hand to a reviewer.

  .claude/skills/piv-create-pr/SKILL.md on GitHub (opens in a new tab)

• piv-fix-review-findings

  Triage code-review findings (manual or AI), fix the ones you choose one at a time with tests, defer/log the rest, then validate — and if the work is on a PR, commit and push so the PR reflects the fixes. Use after a review has produced a list of issues or a review file.

  .claude/skills/piv-fix-review-findings/SKILL.md on GitHub (opens in a new tab)

• piv-implement-issue

  Implement the fix for a GitHub issue from its RCA artifact (created by piv-investigate-issue) — drift-check the plan, branch, implement, add regression tests, and validate. Use after the investigation artifact exists and you're ready to fix the issue.

  .claude/skills/piv-implement-issue/SKILL.md on GitHub (opens in a new tab)

• piv-implement

  Executes an implementation plan task-by-task with validation at every step. Use when you have a completed feature plan and want to implement it in one pass.

  .claude/skills/piv-implement/SKILL.md on GitHub (opens in a new tab)

• piv-investigate-issue

  Investigate a GitHub issue — fan out parallel exploration, find the root cause (5 Whys, evidence-backed), and write a reviewable RCA artifact (then post a summary to the issue). The investigate step before piv-implement-issue. Use to diagnose a bug/issue before fixing it.

  .claude/skills/piv-investigate-issue/SKILL.md on GitHub (opens in a new tab)

• piv-plan-implementation

  Creates a comprehensive, context-rich implementation plan through deep codebase analysis, a short clarifying interview, and external research. Accepts a tracker ticket (a Jira/Linear/GitHub key or URL, fetched from the tracker) or a free-form feature request. Use when you have a ticket or feature and need a one-pass-ready plan before writing any code.

  .claude/skills/piv-plan-implementation/SKILL.md on GitHub (opens in a new tab)

• piv-review-changes

  Performs a technical code review of recently changed files for bugs, security issues, and standards compliance, then writes a report. Use before committing, as a pre-commit quality gate.

  .claude/skills/piv-review-changes/SKILL.md on GitHub (opens in a new tab)

• piv-review-pr

  Full pull-request review — fetch the PR, run the project's validation, review the diff with fresh eyes (dispatching the code-reviewer agent), categorize issues by severity, post the review to GitHub (approve / request-changes / comment), and save a report. The agentic gate that runs on an open PR before a human approves. Use after piv-create-pr.

  .claude/skills/piv-review-pr/SKILL.md on GitHub (opens in a new tab)

• piv-run-full-loop

  Autonomously develops a complete feature from priming through planning, execution, and commit by chaining the four core PIV-loop skills. Use when you want a full hands-off feature build from a single description.

  .claude/skills/piv-run-full-loop/SKILL.md on GitHub (opens in a new tab)

• piv-slice-epic

  Slice an epic (with its architecture decisions) into PIV-sized tickets with a dependency graph, then create them in your tracker (Jira via the Atlassian MCP, or GitHub/Linear/local). Accepts the epic and its architecture as one doc or as an epic plus a separate linked architecture page. Turns a large strategic doc into the discrete units of work that the PIV loop consumes.

  .claude/skills/piv-slice-epic/SKILL.md on GitHub (opens in a new tab)

• piv-validate

  Runs this project's full validation suite — tests, type checks, and linting across every part of the stack — then reports overall health. Use before committing, before opening a PR, or after finishing a chunk of work to confirm zero regressions.

  .claude/skills/piv-validate/SKILL.md on GitHub (opens in a new tab)

• plan-architecture

  Interactively explore HOW to approach an intent (a PRD, epic, brief, or free-form idea) and decide the high-level architecture — the approach, stack, libraries, data shape, and risks the intent left open. A working session with a CTO/staff-engineer advisor that asks questions, proposes 2–3 options with trade-offs, recommends a direction with reasoning, and flags what to de-risk with a spike. Prod…

  .claude/skills/plan-architecture/SKILL.md on GitHub (opens in a new tab)

• plan-create-prd

  Interactive, problem-first PRD generator — interviews the user to surface the thesis (the problem, and WHY build it) and a falsifiable hypothesis, then writes a focused PRODUCT-level PRD (problem · evidence · hypothesis · users · MVP · success metrics · non-goals · open questions). Use at the start of a greenfield effort to discuss the product. A PRD is INTENT (what/why), never engineering decisi…

  .claude/skills/plan-create-prd/SKILL.md on GitHub (opens in a new tab)

• plan-create-stories

  Decomposes a PRD into well-formed, engineer-ready tickets — Jira issues or GitHub issues. Use after a PRD exists, to turn its phases and user stories into a structured backlog. Works for a new codebase (MVP scope) or an existing one (epic scope).

  .claude/skills/plan-create-stories/SKILL.md on GitHub (opens in a new tab)

• prime-backend

  Primes the agent with focused understanding of the backend portion of the codebase — API routes, services, data models, and database layer — without loading unrelated frontend code. Use at the start of a session when the work is scoped to API endpoints, business logic, or data access. Optionally pulls external task context from Jira issues and Confluence pages first.

  .claude/skills/prime-backend/SKILL.md on GitHub (opens in a new tab)

• prime-codebase

  Primes the agent with deep codebase understanding by analyzing structure, documentation, and key files. Use when starting work on a codebase, at the beginning of a session, or when you need a fast orientation before planning or implementing. Optionally pulls external task context from Jira issues and Confluence pages first.

  .claude/skills/prime-codebase/SKILL.md on GitHub (opens in a new tab)

• prime-frontend

  Primes the agent with focused understanding of the frontend portion of the codebase — components, routing, state management, and styling — without loading unrelated backend code. Use at the start of a session when the work is scoped to UI or client-side features. Optionally pulls external task context from Jira issues and Confluence pages first.

  .claude/skills/prime-frontend/SKILL.md on GitHub (opens in a new tab)

• rules-check-drift

  Check whether your rules file (CLAUDE.md or AGENTS.md) still matches the codebase after recent changes — run before a merge, or fold into your code-review pass. Reports stale/now-false rules, drifted architecture-map entries, and any new invariant worth adding, each with the minimal edit. Advisory and anti-bloat: it keeps the rules file true, never longer than it needs to be.

  .claude/skills/rules-check-drift/SKILL.md on GitHub (opens in a new tab)

• rules-create-global

  Set up your project's global rules, a lean and well-structured root CLAUDE.md (plus a starter .claude/), following the course methodology. Greenfield: pass your PRD and/or architecture-spec path and it derives rules from your engineering decisions (a PRD alone is product context). Brownfield: leave it blank to derive from your primed codebase (run /prime-codebase first), or pass a codebase-analys…

  .claude/skills/rules-create-global/SKILL.md on GitHub (opens in a new tab)

• second-brain-audit

  Audit any second brain, notes folder, or agent memory for facts that have quietly stopped being true, then fix the worst one so it stops recurring. Works on a wiki, a single notes file, daily notes, or a non-markdown tool, and adapts the fix to whichever it finds. Checks every current-sounding claim in whatever the agent loads each session against the freshest evidence, and separates contradicted…

  .claude/skills/second-brain-audit/SKILL.md on GitHub (opens in a new tab)

• second-brain-fix

  Work through the findings from a second-brain audit in batches, correcting stale facts and converting locations onto the state/event schema, driven by the markdown file of findings the audit left behind. Use after running second-brain-audit, when someone wants to fix the rest of their notes rather than one page, when they ask how to take the audit forward, when they have a list of contradicted or…

  .claude/skills/second-brain-fix/SKILL.md on GitHub (opens in a new tab)

• setup-ai-tutor

  Sets up and starts the AI Tutor project locally (environment file, dependencies, database, migrations, and dev server). Use when standing up the AI Tutor for the first time on a new machine or after a fresh clone. This is sample-project specific; adapt it when you install the AI Layer into your own project.

  .claude/skills/setup-ai-tutor/SKILL.md on GitHub (opens in a new tab)

No skill matches that filter.

Similar skills

• superpowersby obra An agentic skills framework & software development methodology that works. 300k stars · 15 skills
• skillsby mattpocock Skills for Real Engineers. Straight from my .agents directory. 293k stars · 30 skills
• ECCby affaan-m The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Cod… 280k stars · 30 skills
• reaby morluto Reverse engineer anything with agents, from app behavior down to native binaries. 270k stars · 1 skill
• andrej-karpathy-skillsby multica-ai A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls. 220k stars · 1 skill
• skillsby anthropics Public repository for Agent Skills 181k stars · 19 skills