fable-advisor
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".
npx skills add fcakyon/claude-codex-settings --skill fable-advisor --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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.
- Route by tool
What does the fable-advisor skill do?
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".
How do I install it?
Run `npx skills add fcakyon/claude-codex-settings --skill fable-advisor --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From fcakyon/claude-codex-settings, a repository with 967 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.