fable-advisor

Featured

This skill should be used when the user asks for a "Fable second opinion", wants to "check a plan before committing", needs another view after repeated failures, or explicitly invokes "fable-advisor".

AI & Automation 1,141 stars 108 forks Updated today Apache-2.0

Install

View on GitHub

Quality Score: 91/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
40
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Fable Advisor Get a focused second opinion from Claude Fable 5 without substituting the host tool's model. ## Route by tool 1. In Claude Code, delegate to the native `fable-advisor` agent. Do not launch another Claude Code process. 2. Elsewhere, run this exact shape from this skill's directory so the request reaches standard input: ``` node scripts/ask_fable.mjs <<'REVIEW' the review request REVIEW ``` State the decision, the evidence behind it, and any constraint that changes the verdict. Name the paths that matter: the reviewer has read-only access and checks load-bearing claims itself. Return Fable's answer without rewriting it. If `claude` is missing or unauthenticated, surface the error and ask the user to install it or sign in. Never review in its place.

Details

Author
fcakyon
Repository
fcakyon/claude-codex-settings
Created
1 years ago
Last Updated
today
Language
Python
License
Apache-2.0

Integrates with

OpenAI · AI

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

fable

Ask Fable 5 for a one-off read-only advisory opinion. Not consilium; no report; no routing change.

0 Updated 1 months ago
demetrius2017
AI & Automation Listed

fable

Ask Fable 5 for a one-off read-only advisory opinion. Not consilium; no report; no routing change.

0 Updated 1 months ago
demetrius2017
AI & Automation Listed

fable-advisor

Use when the user wants a task executed by the current session model (typically Sonnet 5) with a persistent Fable 5 advisor overseeing it. Spawns a long-lived read-only Fable 5 subagent that authors the plan, gets consulted at fixed checkpoints via SendMessage, and a separate fresh Fable 5 reviewer that issues a binding pre-commit verdict. When a GitHub issue is referenced, gate-checks it and runs work-on-issue's build-and-ship pipeline under the advisor, posting the plan and the review verdict as issue comments; issue-less prose tasks take a lighter standalone path. A bare issue reference is a complete input — the task derives from the issue itself. Trigger on "/fable-advisor", "fable-advisor <task or issue>", or "execute this with a fable advisor".

49 Updated yesterday
richkuo