Agent skill

Fable Soul

by akseolabs-seo in akseolabs-seo/fable-soul

A skill your agent uses when a session or weaker model needs the Fable judgment layer loaded; when installing, refreshing, or syncing the soul across machines, runtimes, or global instruction files…

MITAuto-check passedDevOps & Cloud

Install Fable Soul

skills CLI
$ npx skills add akseolabs-seo/fable-soul --skill fable-soul -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install akseolabs-seo/fable-soul fable-soul --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
fable-soul
GitHub stars
107
Token cost
~1.1k tokens
SKILL.md length
568 words
Files
17 (incl. scripts, references)
Skills in repo
1
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when a session or weaker model needs the Fable judgment layer loaded; when installing, refreshing, or syncing the soul across machines, runtimes, or global instruction files…

  • Weaker model needs the Fable judgment layer loaded
  • SKILL.md covers Canonical And Mirrors, Mode 1: Embody, Mode 2: Maintain and Mode 3: Transfer, plus 1 more section
  • Runs Python scripts from its folder; calls python
  • Syncing the soul across machines

What it does

Fable Soul is an agent skill from akseolabs-seo/fable-soul. Use when a session or weaker model needs the Fable judgment layer loaded; when installing, refreshing, or syncing the soul across machines, runtimes, or global instruction files; when capturing a new model failure into the soul's rationalization table; when auditing or slimming the judgment rules; or when transferring a stronger model's judgment, postmortems, or session lessons into durable skills.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 19 other files, including scripts and reference files (for example `CHANGELOG.md`, `README.md` and `README.zh-TW.md`).

It sits in DevOps & Cloud, covering Runbooks and postmortems. The repository describes itself as: A judgment layer for AI coding agents - make your AI think, verify, and communicate like a senior engineer. The licence is MIT.

When your agent uses it

  • Weaker model needs the Fable judgment layer loaded
  • Syncing the soul across machines
  • Global instruction files
  • Capturing a new model failure into the souls rationalization table

Example prompts

  • “/fable-soul”

Requirements

  • Python 3

What it can do on your machine

Read from SKILL.md and the folder at commit 643ae8b. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 4 files in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • python

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Fable Soul loads about 1.1k tokens when it runs, and up to ~12k if it reads all its reference files. Until then it costs about 103 tokens; SKILL.md has 568 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~103
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~12k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from akseolabs-seo/fable-soul at commit 643ae8b, republished under its MIT licence (© akseolabs-seo). 568 words, ~1,143 tokens.

Download SKILL.mdSave it as .claude/skills/fable-soul/SKILL.md (or your agent's skills folder). This skill also uses 16 other files; get the full folder from GitHub.
name
fable-soul
description
Use when a session or weaker model needs the Fable judgment layer loaded; when installing, refreshing, or syncing the soul across machines, runtimes, or global instruction files; when capturing a new model failure into the soul's rationalization table; when auditing or slimming the judgment rules; or when transferring a stronger model's judgment, postmortems, or session lessons into durable skills.
metadata.short-description
Fable judgment layer - embody, maintain, and transfer it

Fable Soul

The canonical home of the Fable judgment layer: how to think, investigate, verify, and communicate — distilled from real session failures and TDD-tested against weaker models. This skill has two jobs: EMBODY the soul in the current session, and MAINTAIN/TRANSFER it as infrastructure.

Canonical And Mirrors

references/soul.md in this skill is the single source of truth. Everything else is a mirror; never edit a mirror directly. Mirror map and sync procedure: maintenance.md. If you find a mirror that differs from canonical, that is drift — reconcile via the sync script, reviewing any mirror-side additions before adopting them into canonical.

Mode 1: Embody

When the task is ordinary work and this skill was loaded for judgment: read soul.md, obey it for the rest of the session, and re-check its Red Flags before ending every turn. Do not narrate the rules to the user; just work that way.

Mode 2: Maintain

Capture a failure (a model shipped a false "done", hedged a checkable claim, patched a symptom...): read maintenance.md and follow the capture loop. Core discipline: check whether an existing rule or table row already covers the failure — if yes, strengthen it instead of adding a duplicate; if no, add the rationalization verbatim, then re-test with a pressure scenario before syncing (RED-GREEN, no untested rule edits).

Install or refresh environments: run the sync script per maintenance.md, then verify each target actually received the change (read it back where the runner will load it).

Audit / slim the rules: use the Instruction Audit prompt in transfer-prompts.md. Rules earn their place by changing a future action or verification step; strip ceremony.

Run the evals: after any rule change, run the relevant scenarios in evals.md and record the results there. Captured failures with their before/after receipts live in worked-examples.md — add new captures in the same format.

Optional hook enforcement: examples/hooks.json shows a Claude Code Stop hook that re-fires the core Red Flags deterministically every turn, independent of context length. Offer it to users who want enforcement beyond model discipline; never install hooks silently.

Check for upstream updates: run python scripts/check_update.py from the skill root. It compares local files against the upstream GitHub repo and reports which files differ; it never modifies anything. The first time this skill is used in an environment that supports scheduled tasks (cron, Task Scheduler, or the runner's own scheduling feature), ASK the user whether they want a weekly automatic update check that runs this script and reports the result. Create the schedule only if the user says yes — never install a scheduled task silently.

Show full SKILL.md (145 more words)Show less

Mode 3: Transfer

When the user wants to move judgment into new durable form — a stronger model's advice, a Reddit post, session lessons, a project handover — use the prompt templates in transfer-prompts.md: Departing Principal, Instruction Audit, Failure Archaeology, Executable Campaign, Fresh Verifier, Skill Library Review. Preserve the mechanism, not the aura: every kept rule needs a failure mode, trigger, changed behavior, proof surface, and strip condition.

Evidence Gates

Soul work is complete only when:

  • canonical was edited first, mirrors regenerated by script (not by hand)
  • python scripts/validate_skill.py passes
  • any new or changed rule survived a RED-GREEN subagent test, with the baseline behavior documented in evals.md
  • each sync target was read back and contains the change
  • drift check is clean (script reports all mirrors in sync)
  • any review finding accepted during the work was resolved with evidence or explicitly closed as residual risk — never silently dropped

© akseolabs-seo, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 16 other files (scripts, references) in the repository root of akseolabs-seo/fable-soul.

  • SKILL.md
  • .gitignore
  • CHANGELOG.md
  • LICENSE
  • README.md
  • README.zh-TW.md
  • examples/hooks.json
  • references/evals.md
  • references/maintenance.md
  • references/soul-compact.md
  • references/soul.md
  • references/transfer-prompts.md
  • references/worked-examples.md
  • scripts/check_update.py
  • scripts/sync_soul.py
  • scripts/test_sync_soul.py
  • scripts/validate_skill.py

Open the folder on GitHubat commit 643ae8b

Compare with similar skills

Fable Soul next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Fable Soul compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Fable Soul this skillakseolabs-seo/fable-soul107—~1.1kAutomated safety check: PassMIT
Trader Memory Coretradermonty/claude-trading-skills3k2 repos~4.3kAutomated safety check: PassMIT
Author Migrationnrwl/nx29k—~12kAutomated safety check: NotesMIT
Write Notes Like Deepseekczm15053/write-notes-like-deepseek508—~2kAutomated safety check: PassNone
OpenRig Upgrade Proceduremvschwarz/openrig6.8k—~2.9kAutomated safety check: PassApache-2.0
GreptimeDB Release RunbookGreptimeTeam/greptimedb6.7k—~1.4kAutomated safety check: PassApache-2.0

Similar skills

  • Trader Memory Core

    tradermonty/claude-trading-skills

    Track investment theses across their lifecycle — from screening idea to closed position with postmortem.

    3k GitHub starsUsed in 2 repos~4.3k tokens
    DevOps & CloudAuto-check passed
  • Author or scope a first-party Nx migration. An agent skill from nrwl/nx.

    29k GitHub stars~12k tokensUpdated yesterday
    DevOps & CloudAuto-check: notes
  • Write Notes Like Deepseek

    czm15053/write-notes-like-deepseek

    A skill your agent uses when a change is non-trivial by DSH standards (behavior, architecture, cross-file contracts, process/tooling, testing strategy, or on-disk/wire/config formats), when choosing…

    508 GitHub stars~2k tokensUpdated 3 days ago
    DevOps & CloudAuto-check passed
  • OpenRig Upgrade Procedure

    mvschwarz/openrig

    Walks an agent through upgrading the OpenRig CLI and daemon one observed step at a time, keeping live seats alive and reconciling managed plugin files.

    6.8k GitHub stars~2.9k tokensUpdated today
    DevOps & CloudAuto-check passed
  • GreptimeDB Release Runbook

    GreptimeTeam/greptimedb

    Runbook for publishing a GreptimeDB version: pick the release branch, verify the Cargo version, then tag, create the GitHub release and open the docs note PR.

    6.7k GitHub stars~1.4k tokensUpdated today
    DevOps & CloudAuto-check passed
  • Statem

    henryqin1997/statem

    A skill your agent uses when a long coding or research task should be managed with statem state-machine runbooks, including creating specs, starting or resuming runs, checking current state…

    1.3k GitHub stars~1.2k tokensUpdated 1 mo ago
    DevOps & CloudAuto-check passed

Categories

Questions about Fable Soul

What does Fable Soul do?

A skill your agent uses when a session or weaker model needs the Fable judgment layer loaded; when installing, refreshing, or syncing the soul across machines, runtimes, or global instruction files…. Fable Soul is an agent skill from akseolabs-seo/fable-soul. Use when a session or weaker model needs the Fable judgment layer loaded; when installing, refreshing, or syncing the soul across machines, runtimes, or global instruction files; when capturing a new model failure into the soul's rationalization table; when auditing or slimming the judgment rules; or when transferring a stronger model's judgment, postmortems, or session lessons into durable skills.

When should I use Fable Soul?

Fable Soul fits situations like: weaker model needs the Fable judgment layer loaded; syncing the soul across machines; global instruction files; capturing a new model failure into the souls rationalization table.

How do I install Fable Soul in Claude Code?

Run `npx skills add akseolabs-seo/fable-soul --skill fable-soul -a claude-code`. Or copy the skill folder (the akseolabs-seo/fable-soul repository) into .claude/skills/fable-soul in your project. Claude Code loads it when a task matches its description.

How do I install Fable Soul in Codex?

Run `npx skills add akseolabs-seo/fable-soul --skill fable-soul -a codex`. Or copy the skill folder (the akseolabs-seo/fable-soul repository) into .agents/skills/fable-soul in your project. Codex loads it when a task matches its description.

Can I use Fable Soul in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add akseolabs-seo/fable-soul --skill fable-soul -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/fable-soul, .gemini/skills/fable-soul, .github/skills/fable-soul and .opencode/skills/fable-soul in your project.

What does Fable Soul need to run?

Going by SKILL.md and its folder, Fable Soul needs Python for the scripts in its folder and the command-line tools its instructions call (python). Our summary lists: Python 3.

Does Fable Soul access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Fable Soul safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Fable Soul use?

Fable Soul is published under the MIT licence (from the LICENSE file in the skill folder). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Fable Soul use?

About 1.1k tokens (SKILL.md is roughly 4.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 11k tokens, read only when the agent opens those files.

What are the alternatives to Fable Soul?

Skills that share tags, products or a category with Fable Soul: Trader Memory Core (tradermonty/claude-trading-skills, 3k stars), Author Migration (nrwl/nx, 29k stars), Write Notes Like Deepseek (czm15053/write-notes-like-deepseek, 508 stars) and OpenRig Upgrade Procedure (mvschwarz/openrig, 6.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Fable Soul?

akseolabs-seo (a GitHub user) maintains it in akseolabs-seo/fable-soul, which has 107 GitHub stars. The repository was last updated on July 8, 2026.

Source: akseolabs-seo/fable-soul on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.