.fyi
SkillsMCPPluginsSubagents

Browse by category

DevOps & CI/CD SkillsProductivity & Workflow SkillsOther SkillsProduct & Project Management SkillsDocumentation & Knowledge SkillsCode Review & Refactor SkillsBackend & APIs SkillsAgent Meta & Communication SkillsResearch SkillsSecurity SkillsUX UI & Design SkillsTesting & QA SkillsSee all →

Every Claude Code skill, MCP server, plugin and subagent in one directory. Searchable, comparable, and one command from installed. Live stats from GitHub, npm and PyPI.

We're on Product HuntYour agent's app storeCheck it out →
Agent SkillsMCP ServersPluginsSubagentsCoding Agents
CollectionsOfficial publishersGlossaryFAQBlogSearchSavedFeedback
PrivacyTermsllms.txtSitemap

made with ♥ · © 2026 aaaa.fyi

Independent project · real data from public registries

…/benjaminard/fable-skills
home/skills/benjaminard/fable-skills
benjaminard avatar

benjaminard/fable-skills

9 skills

View on GitHub
$npx skills add benjaminard/fable-skills
SkillInstalls
delegate-and-verifySubagent orchestration and verification discipline. Use whenever a task has independent subtasks that could run in parallel, whenever work is substantial…—evidence-audited-analysisData-skepticism discipline for quantitative work. Use whenever reading data and producing a conclusion: analytics questions, metrics reports, spreadsheet…—finish-the-turnAutonomy and checkpoint discipline for agentic work. Use on every task where the model works with tools over multiple steps.—lessons-ledgerCross-run memory discipline for agents with a persistent workspace.—minimal-diffScope discipline for code changes. Use whenever writing or editing code: implementing a feature, fixing a bug, or modifying existing files.—outcome-first-writingProse discipline for any written deliverable. Use whenever writing for a human reader: answers, explanations, reports, summaries, documentation, PR…—plain-handoffFinal-summary discipline for agentic sessions. Use when writing the closing message of any multi-step working session: after many tool calls, after a long…—root-cause-firstDebugging discipline. Use whenever diagnosing a bug, error, test failure, crash, regression, flaky behavior, or unexpected output, and especially before…—verified-doneCompletion and progress-reporting discipline for any coding task.—