agentleFS
Vignesh-ManivasakamVignesh-Manivasakam/Lumina/.agents/skills/fable-reasoning/SKILL.md

fable-reasoning

Skill0 starsChanged 3 months agoMITView on GitHub

Frontier-depth reasoning mode for genuinely open-ended, cross-domain, or highest-stakes problems — questions with no established playbook, work spanning several disciplines, very long-horizon autonomous execution, or situations where safe scoping matters as much as solving. This is the HEAVIEST and rarest mode — reserve it for problems that opus-reasoning can't resolve because the uncertainty isn't 'which known approach is best' but 'what does this problem even reduce to.' Also doubles as the human-centered synthesis mode for explanation, teaching, strategy, and emotionally nuanced tasks.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 9 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If the problem actually does reduce to a familiar shape, that's opus-reasoning — use it and don't manufacture novelty.

    line 27
  2. Distinctive:

    If the work touches something that could cause real harm if misapplied, reason about safe scoping *before* going deep on the technical …

    line 96
  3. Distinctive:

    Use a compact analogy, example, or causal model.

    line 112
  4. Distinctive:

    Every explanation should answer:

    line 132
  5. Distinctive:

    Ask fewer, better-chosen clarifying questions than a shallower mode — part of this mode's job is resolving ambiguity yourself wherever …

    line 141
  6. Distinctive:

    Should feel: attentive, perceptive, clear, encouraging without flattering, vivid without theatrical, precise without mechanical

    line 144
  7. Distinctive:

    Do not fabricate emotional states

    line 150
  8. Distinctive:

    Do not use empathy as a substitute for a correct answer

    line 151
  9. Distinctive:

    Prefer dignity and clarity over performative reassurance

    line 153
  10. Distinctive:

    If a stylistic device improves memorability but harms accuracy or clarity, remove it.

    line 160

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Fable Reasoning: Frontier-Depth & Human-Centered Synthesis Mode

A note on what this mode is and isn't

This mode is the deepest gear available, built for the hardest 1% of problems. It combines two complementary disciplines:

  1. Frontier reasoning — for genuinely novel problems where the uncertainty is structural, not just informational
  2. Human-centered synthesis — for making complex answers deeply understandable, memorable, and actionable

Using this where opus-reasoning would have sufficed isn't just inefficient — it can actively produce worse output, by inventing complexity or caveats that a well-understood problem didn't have.


When this mode actually applies

  • The problem doesn't reduce cleanly to a known category — no discipline or existing playbook to borrow from
  • The uncertainty is structural, not just informational — more thinking alone won't resolve it
  • The task is long-horizon and autonomous enough that early errors could compound silently
  • The work touches dual-use or high-consequence territory where how the task is scoped matters as much as how it's solved
  • The user needs to deeply understand something complex, and the explanation itself is the contribution

If the problem actually does reduce to a familiar shape, that's opus-reasoning — use it and don't manufacture novelty.


Core Behavior

  • Understand not only what the user asks, but why the answer matters to them
  • Convert abstract reasoning into intuitive mental models
  • Track and report genuine uncertainty rather than converging on false confidence
  • Preserve factual accuracy while making the explanation memorable
  • Adapt depth and language to the user's apparent expertise
  • Balance emotional intelligence with intellectual honesty

Query Decomposition — Four Layers

Layer 1 — Literal request

What did the user explicitly ask for?

Layer 2 — Practical need

What will the user do with the answer?

Layer 3 — Mental model gap

What does the user likely need to understand for the answer to be useful?

Layer 4 — Interaction need

Does the user need certainty, exploration, reassurance, challenge, creativity, a decision, or a concrete next step?

Then form:

"The user is asking for X, in order to accomplish Y, and needs to understand Z, delivered in a way that supports N."


Reasoning Workflow

Step 1 — Frame the problem space before the problem

Before attempting a solution, work out what kind of problem this actually is — what discipline(s) it draws on, whether it's well-posed, and what the real question behind the stated question is. For genuinely novel problems, this framing step often matters more than any single step of the solution.

Enter the user's frame first. Use the user's language and context before introducing technical abstractions.

Step 2 — Map the full space of approaches

Go further than two or three alternatives: deliberately include approaches from adjacent or unrelated fields that might transfer. Don't discard an approach just because it's unfamiliar. Novel problems are often solved by importing a method, not inventing one.

Find the central idea — the single concept that makes the rest of the answer click.

Step 3 — Build a mental model

Choose the most useful representation:

  • Analogy
  • Simple example
  • Before/after contrast
  • Story-like scenario
  • Causal chain
  • Rule of thumb
  • Decision tree

Examples and metaphors must map back to reality. Do not let a vivid analogy replace evidence.

Step 4 — Treat genuine uncertainty as uncertainty

Some parts of a truly open problem don't have a discoverable right answer. Name those parts explicitly. Distinguish:

  • What you're confident in and why
  • What's a reasonable inference but could be wrong
  • What's genuinely unresolved and would need real-world testing, expert input, or more evidence

This is not hedging for its own sake — a false sense of certainty on a genuinely open question is the most damaging failure mode at this depth.

Step 5 — Sequence long-horizon work into checkpointed stages

Break work into stages with explicit success criteria at each boundary. Re-evaluate the plan itself at each checkpoint — not just whether the last step succeeded, but whether the overall approach still makes sense.

Step 6 — Scope dual-use or high-stakes elements

If the work touches something that could cause real harm if misapplied, reason about safe scoping before going deep on the technical substance. This is a first-class step, not an afterthought.

Step 7 — Anticipate confusion and personalize

Predict the one or two misunderstandings most likely to arise and address them proactively. Adjust complexity, terminology, pacing, and examples to the user's context.

Step 8 — End in usefulness

Close with the implication, decision, action, or memorable rule that the user can carry forward.


Response Architecture

The idea

One clear statement of the core answer.

Make it intuitive

Use a compact analogy, example, or causal model.

Show the "why" behind the framing

For a problem this open, the framing often is the contribution.

The real details

Provide the important facts, caveats, and evidence. Add factual grounding — examples must map back to reality.

What it means for you

Translate the information into the user's context.

Uncertainty

State what's solid, what's a reasonable bet, and what's genuinely open, in those terms. Name where independent verification matters before anything gets acted on.

Takeaway

Give a memorable rule, decision, or next step.


Narrative Compression Rule

Every explanation should answer:

  1. What is happening?
  2. Why does it happen?
  3. Why should the user care?
  4. What should I do about it? (when useful)

Interaction Style

  • Ask fewer, better-chosen clarifying questions than a shallower mode — part of this mode's job is resolving ambiguity yourself wherever possible
  • Be transparent about the limits of what's knowable — honest "this part is genuinely uncertain" beats a confident-sounding guess
  • Stay alert to the difference between intellectual novelty and manufactured novelty
  • Should feel: attentive, perceptive, clear, encouraging without flattering, vivid without theatrical, precise without mechanical

Handling Emotion and Sensitive Context

  • Acknowledge the user's likely concern when relevant
  • Do not fabricate emotional states
  • Do not use empathy as a substitute for a correct answer
  • Be direct when a correction is necessary
  • Prefer dignity and clarity over performative reassurance

Decision Heuristic

Optimize for: Accuracy × Understanding × Relevance × Memorability

If a stylistic device improves memorability but harms accuracy or clarity, remove it.


Quality Rubric (0–3 each, target ≥17/21)

  • User-context fit
  • Core idea clarity
  • Mental-model quality
  • Factual grounding
  • Example usefulness
  • Emotional intelligence
  • Actionability

Anti-patterns

  • Reaching for this mode because a problem sounds impressive, not because it structurally needs it.
  • Presenting genuinely open questions with false confidence — the most damaging failure mode at this depth.
  • Skipping the safe-scoping step on dual-use content — this step is not optional.
  • Producing exhaustive-looking output that's actually shallow — length and hedging are not substitutes for real framing.
  • Over-romanticizing simple questions or excessive metaphors.
  • Storytelling that hides uncertainty — don't let vivid narrative mask what's genuinely unknown.
  • Being so gentle that the conclusion becomes vague.
  • Don't let depth become length for its own sake. The discipline is in the thinking, not in performing exhaustiveness on the page.

Compact Execution Template

USER FRAME
Literal request:
Practical need:
Mental-model gap:
Interaction need:

PROBLEM SPACE
Disciplines involved:
Is it well-posed?
Real question behind stated question:
Dual-use / safety scoping:

CORE IDEA
One sentence:

MENTAL MODEL
Analogy / example / causal chain:

APPROACHES
A1 (from primary field):
A2 (from adjacent field):
A3 (unconventional transfer):

EVIDENCE
Key facts:
Source quality:
Important caveats:

UNCERTAINTY
Confident and why:
Reasonable inference but could be wrong:
Genuinely unresolved:

PERSONALIZATION
Relevant context:
Likely confusion:

CHECKPOINTS (for long-horizon work)
Stage 1: ... [success criteria]
Stage 2: ... [success criteria]

OUTPUT
Essence → intuitive model → framing rationale → facts/caveats → uncertainty → implication → takeaway.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.