Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for AI-coding power users, agent developers, automation builders, engineering teams, DevOps engineers, SREs, engineering managers, AI-curious readers, founder-CTOs, technical writers, and any developer who runs Claude Code / Codex on a long-running coding workflow and is tired of agents that 'edit a file, say Done! Fixed the bug, never ran anything' -- and who can pair fable-soul with a Cla
Who should use it
Who should skip it
Pass on akseolabs-seo/fable-soul if its scope or audience does not match what your team is building right now.
About this signal
akseolabs-seo/fable-soul is tracked by RepoRadar as a judgment layer for ai coding age in the Coding Agent Skills / Prompt Engineering section. It was first seen on 2026-07-06 and last updated on 2026-07-06. The current verdict is 'try now' with a Silver tier and easy setup difficulty. akseolabs-seo/fable-soul leads on workflow potential (9.2) and setup ease (8.8); its lowest signal is maturity (5.6), so factor that in before investing setup time. This page summarizes the evidence RepoRadar has captured from captured source metadata. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.
How this item is evaluated
RepoRadar assigned akseolabs-seo/fable-soul a composite score of 7.7 out of 10, placing it in the Silver tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 1.0 and never affects the composite score or tier. The risk label of 'low' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.
Putting this into practice? Read How to vet an AI agent or MCP server before you wire it in for the checklist behind this score.
Risk explanation
The 83* / 3-commit codebase is very recent (created 2026-07-03; 3 days before this cycle) and the community is small -- treat the first evaluation cycle as a smoke test (clone the repo + copy the folder to ~/.claude/skills/fable-soul/ + give the agent the README's example pressure scenario + confirm the agent runs the rationalization table + confirm the agent refuses to bump the timeout without first identifying the real cause + disable the soul and rerun to confirm the agent falls back to the bad pattern) before relying on the 19 rules in production; the references/soul.md (~250 lines) is the durable opinionated layer -- audit the 19 rules + the rationalization table + the Red Flags before deploying to a multi-tenant environment to confirm the rules match the team's coding style; the sync_soul.py script handles the install surface (the --check flag compares without writing) but if ~/.claude/CLAUDE.md or ~/.codex/AGENTS.md already exists.