send-to-claude-fable
Skill4 starsChanged 21 days agoMITView on GitHub
Send a bounded task or review packet to the local Claude Code CLI on the Fable model and bring back its verdict. Use when you want an independent second opinion from a different model.
In this repository79 other files it gives its agents.
- AGENTS.mdAGENTS.md
- accepted-proof-exact-retuneSkill
- arxiv-portable-researchSkill
- auto-autoresearch-pipelineSkill
- beachhead-ratchetSkill
- bounded-commuting-foldSkill
- burn-the-house-downSkill
- calibrated-static-cost-proxySkill
- circuit-edit-integration-safetySkill
- colab-laneSkill
- computer-algebra-oraclesSkill
- constraint-construction-searchSkill
- cross-model-review-gateSkill
- deepseek-pressure-testSkill
- ecdsafail-fastevalSkill
- ecdsafail-lowq-playbookSkill
- ecdsafail-oracle-loopSkill
- ecdsafail-pareto-ratchetSkill
- ecdsafail-scratch-dietSkill
- elicit-researchSkill
- evaluator-scoring-surface-auditSkill
- exact-evaluator-replicaSkill
- exact-hold-passSkill
- exact-postpass-stackSkill
- exact-search-engineeringSkill
- fast-lean-proof-loopSkill
- fit-probe-and-spliceSkill
- gpu-affine-table-synthesisSkill
- greedyfrog-methodSkill
- hard-problem-contractSkill
- hold-demand-ledgerSkill
- hosted-carry-lendingSkill
- inert-op-screen-to-structural-ruleSkill
- invariant-chartSkill
- jev-second-perspectiveSkill
- lambda-exchange-deskSkill
- leader-rebase-stackSkill
- lean-arklib-proofsSkill
- lean-finite-certificate-splittingSkill
- lever-switches-and-break-controlsSkill
- mission-commandSkill
- nasqret-playbookSkill
- paged-walk-descentSkill
- peak-lifetime-ledgerSkill
- pinned-table-stackingSkill
- pip-disciplineSkill
- portable-source-assertionsSkill
- proximity-prize-campaignSkill
- proximity-prize-frontier-archaeologySkill
- quantum-affine-lookup-synthesisSkill
- quantum-borrowed-wire-counterexampleSkill
- quantum-dense-qromSkill
- quantum-dirty-borrowingSkill
- quantum-divstep-reconstructionSkill
- quantum-encoded-arithmeticSkill
- quantum-graded-divider-placementSkill
- quantum-guarded-permutation-auditSkill
- quantum-mbundo-lifetimesSkill
- quantum-record-miningSkill
- quantum-replay-arithmeticSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Use this skill when the user explicitly asks to send, delegate, or obtain a review from Claude Fable through the local claude CLI.
- Very specific: line 12
Verify the local interface with command -v claude, claude --version, and only the relevant help when its flags are uncertain.
- Distinctive: line 34
If the command yields a running session, poll it normally and do not signal or kill it unless the user explicitly asks.
- Very specific: line 40
Do not use --continue or --resume unless the user asks to enter an existing Claude conversation.
- Very specific: line 41
Prefer --no-session-persistence for one-shot reviews.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Märlitante (send-to-claude-fable)
Use this skill when the user explicitly asks to send, delegate, or obtain a review from Claude Fable through the local claude CLI.
Dispatch
- Verify the local interface with
command -v claude,claude --version, and only the relevant help when its flags are uncertain. - Build a self-contained prompt containing:
- the concrete task and expected verdict or deliverable;
- exact source, artifact, or conversation bindings needed to work independently;
- the user's current authorization and prohibitions;
- a request to label measured evidence separately from inference.
- Redact secrets, credentials, personal data, provider identifiers, and unrelated private context.
Invoke Fable non-interactively and wait for its answer:
claude -p \ --model fable \ --effort high \ --permission-mode dontAsk \ --allowedTools 'Read,Grep,Glob' \ --disallowedTools 'Write,Edit,NotebookEdit,Bash' \ --no-session-persistence \ --output-format text \ "<bounded prompt>"These are safe defaults for review and discovery work.
dontAskis intentional: Claude'splanmode may create a file under~/.claude/plans, even when the task is otherwise read-only. Adjust tools or permission mode only when the user explicitly authorizes the corresponding mutations. Never use--dangerously-skip-permissionsmerely to avoid a permission boundary.- If the command yields a running session, poll it normally and do not signal or kill it unless the user explicitly asks.
- Return Fable's actual verdict, clearly attributed to Claude Fable. Keep Codex's own assessment separate, and report CLI/authentication failure rather than fabricating a handoff.
Boundaries
- Sending a task does not expand its authority. Carry forward all no-edit, no-provider, no-spend, no-submit, and other active restrictions.
- Do not use
--continueor--resumeunless the user asks to enter an existing Claude conversation. - Prefer
--no-session-persistencefor one-shot reviews. Use background agents only when the user explicitly asks for a persistent or background Claude task. - A successful CLI launch is not a successful review. Wait for and report the terminal response.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

