Fable-class agentic operating discipline, gated to task risk and domain so overhead scales with stakes. Trigger on: explicit /fable-skill or $fable-skill; debugging or diagnosing a failure; changes spanning multiple files; refactors and migrations; irreversible or destructive actions; ambiguous goals needing…
Use for AI-assisted code changes that must keep project living docs in sync. Triggers on feature work, bug fixes, refactors, API/schema/security/deployment changes, requirement updates, tests, guardrails, and change records. Do not use for general Q&A or non-project snippets.
Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
Lint and improve AI agent context files (CLAUDE.md, AGENTS.md, .cursorrules, COPILOT.md) based on empirical research. Use when reviewing, auditing, or creating context files.
Disciplined plan-build-verify loop for implementing a feature or change. Use when building something new or modifying existing behavior, especially across multiple files.
Generate production-ready AI steering documents — CLAUDE.md, AGENTS.md, GEMINI.md, SKILL.md, rules.md, .cursor/rules/, .kiro/steering/, copilot-instructions.md — for any AI coding system. Use when asked to write, improve, or review project instructions, agent rules, or steering docs for Claude, Copilot, Cursor, Kiro…
Maximum-savings variant of eco - the same frugality rules with a tighter reply budget, for routine chores (rename, small fix, quick lookup, boilerplate). Prefer plain eco for hard or high-stakes work. Works in any language.
A repository audit and cleanup tool for AI coding-agent instructions, such as AGENTS.md, CLAUDE.md, and editor-specific rule files. It consolidates these instructions into AGENTS.md and adds checks to detect later drift.
An instruction-file writing skill for creating, reviewing, or reorganizing AGENTS.md and CLAUDE.md files. These files give coding agents project facts and working rules, such as how to run tests or follow conventions.
Validate AGENTS.md and related agent instruction files with the published agents-doctor CLI. Use when the user asks to check, lint, verify, explain, audit, fix, release-check, or compare AGENTS.md, CLAUDE.md, GEMINI.md, agent instruction inheritance, tool profiles, context fidelity, instruction graphs, GitHub…
Compute the four DORA delivery metrics from uFawkesObs (Prometheus + Loki). Use when producing monthly DORA snapshots, validating post-release metric trends, or generating ROI evidence. Requires uFawkesObs running. Implements DORA AI Capabilities 2 and 7.
Lightweight smart project memory for Codex. Use when the user wants to initialize or maintain persistent Codex project memory, create a multi-project workspace, add a new project with reusable context files, recover context in new chats, write session snapshots, compact important conclusions into durable files, route…
Turn docs/PRD.md into docs/PLAN.md — an ordered, checkbox build plan with architecture, risk gates, and a test list. Use after /spec, before any code. The plan survives session compaction; conversation context does not.
Writes, audits, and continuously evolves project memory across the whole Claude Code memory system — CLAUDE.md (project ./CLAUDE.md, personal /.claude/CLAUDE.md, local ./CLAUDE.local.md), AGENTS.md, .claude/rules, and Auto Memory. Use when the user wants to create, generate, review, audit, slim down, or evolve a…
Generate AI agent config files for any project — Cursor, Claude Code, Copilot, Windsurf, Cline, AGENTS.md. Use when setting up a new project for AI agents.
Use when the user wants to set up Project Spine for a new project — phrases like "new client project", "kickoff", "create AGENTS.md from scratch", "generate agent instructions for this repo", "set up project context". Runs spine init → edits brief → spine compile → reviews outputs. For stale files use…
Decide how much review a change has earned, before reviewing it. Selects quick, standard, or deep from stated signals (reviewable changed lines, directory spread, trust-boundary risk flags, blast radius, documentation-only scope), reports the signal table and the rule that fired, then runs house-review at the selected…
Audit a repository's AI-agent readiness with the agentlint CLI and fix the findings. Use when the user asks to score, audit, or improve how well a repo works with AI coding agents (AGENTS.md, build/test docs, conventions, guardrails), or mentions agentlint.
Generate an HTML dashboard of project status and recent outputs, scoped to what the user asks about. Use when the user asks for a dashboard or project status, asks what is blocking a release, what needs attention, or where work was left off, or wants a visual read on a repo instead of scrolling terminal output.…
This skill should be used when the user wants to check how readable a website is to AI agents (ChatGPT, Claude, Perplexity, Google Gemini, MCP clients). Activates for "scan this site for AI readability", "check my llms.txt", "audit our agent-readability", "is my MCP server card valid", "what's our Vercel Agent…
AI media generation via Fal.ai: images, video, upscale, edits. Produces Instagram ad creative using a dual-model pipeline — runs Nano Banana Pro Edit AND Ideogram v4 Image-to-Image side-by-side for every concept, giving the user two takes per brief at negligible cost ($0.28/concept). Always uses image-to-image when a…
Write and edit so anyone can read it: plain words, human voice, real structure, no filler. Enforces the CLEAR-100 standard on four axes (Plain, Human, Structured, Dense) with a zero-dependency checker. Use this skill whenever you draft, rewrite, review, or edit any prose a person will read: posts, docs, READMEs…
★not rated 1 10d agoA119 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: