SkillAgentSearch skills...

efficient-fable

Alias for /efficient-orchestrator. Run only when the user explicitly invokes /efficient-fable; never self-activate.

Install / Use

npx skills add BuilderIO/skills --skill efficient-fable

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

81/100

Supported Platforms

Universal

Tags

Our assessment of efficient-fable

efficient-fable scores 81/100 on our quality scale, 3491st of 4,698 Development & Engineering skills we index.

Its SKILL.md is 3.9 KB long, well organised into 8 sections and no code examples: a solid amount of guidance for an agent.

With 4,394 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
13/20
Description
12/15
Adoption
16/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so efficient-fable is actively maintained.
  • Our last check on 2026-11-08 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-09-29. Automated pattern scan on 2026-09-29. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

efficient-fable compared with similar skills

All 4 of these similar skills score higher than efficient-fable; compare them before choosing.

SkillScoreStarsUpdatedFormat
efficient-fable (this skill)by BuilderIO814.4k54d agoSKILL.md
taste-skillby Leonxlnx100116.8k8d agoCLAUDE.md
ai-job-searchby ai-job-search-dev10072.1ktodayCLAUDE.md
claude-howtoby luongnv8910047.3k2d agoCLAUDE.md
lobehubby lobehub10085.6ktodayMCP Server

Frequently asked questions

How do I install efficient-fable?
Run npx skills add BuilderIO/skills --skill efficient-fable. The install tabs above show the steps for each supported agent.
Which AI agents does efficient-fable work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is efficient-fable safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is efficient-fable still maintained?
The repository was last updated about 2 months ago, so efficient-fable is actively maintained.

name: efficient-fable description: Use when running Claude Fable on codebase-heavy or token-heavy work and the user wants Fable to orchestrate research, coding, and testing while cheaper subagents do bounded heavy lifting.

Efficient Fable

Use Claude Fable as the orchestrator, architect, synthesizer, and final judge. Use cheaper subagents for token-heavy research, coding, testing, and summarization that do not require Fable's full judgment.

Where Fable Shines

Reserve Fable for:

  • Decomposing ambiguous work into clean parallel slices.
  • Architecture, product, and safety tradeoffs.
  • Reading conflicting subagent reports and deciding what matters.
  • Integrating partial implementations into one coherent plan.
  • Final review, risk assessment, and user-facing synthesis.

Delegation Pattern

  1. Name the expensive-token risk: large repo search, long logs, broad docs, or repetitive edits.
  2. Split independent work into subagents before reading everything yourself.
  3. Use cheaper models for research scans, inventory, search summaries, narrow bug hunts, browser/testing passes, test output reduction, and bounded code edits.
  4. Ask subagents for concise evidence: files, line references, commands run, diffs, uncertainties, and stop conditions they hit.
  5. Spend Fable tokens on the decision layer: compare results, resolve conflicts, choose the implementation path, and review the final patch.

Prefer parallel subagents when the slices do not depend on each other. Keep blocking or highly coupled work local.

Handoff Packets

Write delegated prompts as if the subagent has no useful chat context. Include only the context it needs:

  • The repo path and exact objective.
  • The files, packages, or surfaces in scope and anything explicitly out of scope.
  • The evidence format to return: files, line refs, commands, diffs, failures, screenshots, and uncertainty.
  • The verification commands or browser flows to run, plus what success should look like when that is knowable.
  • Stop conditions: if the code does not match the prompt, a command fails after a reasonable retry, or the task needs out-of-scope files, stop and report instead of improvising.

Vetting Delegated Work

Treat subagent reports as leads, not facts. Before using a high-impact finding, opening a PR, or telling the user the work is done, Fable should reopen the important cited files, confirm the relevant line refs or failures, and review the final diff against the task. Let lighter agents gather signal; keep truth-judgment with Fable.

Common Scenarios

Treat these as soft defaults, not rigid rules:

  • Research: ask lighter agents to scan docs, prior art, APIs, and repo surfaces; Fable decides what evidence changes the plan.
  • Coding: give cheaper agents bounded edits or candidate patches; Fable owns shared-file coordination, integration, and final review.
  • Testing: have Fable suggest the validation direction and the scripts or browser checks that matter. Let lighter agents run targeted tests, browser flows, screenshots, and log reduction, then report exact commands, failures, likely causes, and whether failures look flaky, environmental, or real.
  • Debugging: use cheaper agents to cluster logs, reproduce issues, and try small fixes; Fable decides which diagnosis is most trustworthy.

If a task is tiny or the validation itself needs delicate judgment, keep it with Fable.

Diagram

Use assets/fable-orchestrator.excalidraw when a visual explanation helps.

Claims

For codebase-heavy work, it is reasonable to describe this as up to 3-5x more cost-efficient and 2-4x faster when independent research, coding, or testing slices can run in parallel. Treat those as workload-dependent estimates, not guarantees.

Good launch copy:

Make Claude Fable more efficient by using cheaper subagents for token-heavy research, coding, and testing, saving Fable for judgment, architecture, synthesis, and final review.

Related Skills

View on GitHub
GitHub Stars4.4k
CategoryDevelopment
Updated1mo ago
Forks220

Languages

JavaScript

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions