agentleFS
secondorderaisecondorderai/ouroboros/.claude/skills/meta-thinking/SKILL.md

meta-thinking

Skill3 starsChanged 6 months agoMITView on GitHub

Use this skill when the user needs structured planning, complex analysis, difficult tradeoff decisions, or troubleshooting under uncertainty and the agent should apply a compact meta-thinking loop with task classification, a meta-mode gate, plan extraction, critique, and concise trust signals. Prefer it when surfacing confidence, limitations, and context gaps will materially improve the answer. Do not use it for simple factual or one-step requests where extra framing would add friction without improving the result.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

Show its rules and text

We split this skill into the rules it gives an agent

15 rules. About 0 are common, 15 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈15

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill to apply the SecondOrder method to the agent's own work.

    line 10
  2. Distinctive:

    Use this skill when the request benefits from one or more of:

    line 14
  3. Distinctive:

    Do not use the full workflow for:

    line 22
  4. Distinctive:

    Treat this as a compact control loop, not an excuse to dump internal reasoning.

    line 37
  5. Distinctive:

    When meta mode is justified, bias toward a compact response structure that can include:

    line 41
  6. Distinctive:

    Only surface fields that materially help the user.

    line 51
  7. Distinctive:

    Before finalizing, check for:

    line 57
  8. Distinctive:

    If the critique finds meaningful issues, tighten the answer and surface only the user-relevant residue.

    line 65
  9. Distinctive:

    Do not reveal chain-of-thought or hidden scratch work.

    line 78
  10. Distinctive:

    Do not force every answer into a verbose template.

    line 79
  11. Distinctive:

    Do not use this as a generic "think harder" wrapper.

    line 80
  12. Distinctive:

    Do not turn the task into a lesson on metacognition unless the user asks for that.

    line 81
  13. Distinctive:

    Read references/second-order-method.md for the canonical method, terminology, and gating heuristics.

    line 85
  14. Distinctive:

    Read references/output-patterns.md for compact response patterns by task type.

    line 86
  15. Distinctive:

    Read references/examples.md for realistic trigger and non-trigger examples.

    line 87

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Meta Thinking

Use this skill to apply the SecondOrder method to the agent's own work. This is an execution skill, not a teaching curriculum.

Activation

Use this skill when the request benefits from one or more of:

  • structured planning before answering
  • tradeoff analysis or decision support
  • troubleshooting with missing or unreliable context
  • explicit handling of uncertainty, limitations, or context gaps
  • reflective response shaping instead of a direct one-pass answer

Do not use the full workflow for:

  • simple factual lookup
  • short transformations or edits with obvious steps
  • routine requests where standard tooling is sufficient and visible framing would add noise

Default Workflow

  1. Classify the task.
  2. Decide whether meta mode is warranted.
  3. Extract the goal, constraints, and response strategy.
  4. Produce a compact plan.
  5. Critique the draft for weak assumptions, limitations, and missing context.
  6. Return the answer with concise visible framing when justified.

Treat this as a compact control loop, not an excuse to dump internal reasoning.

Output Contract

When meta mode is justified, bias toward a compact response structure that can include:

  • goal
  • constraints
  • plan
  • confidence
  • limitations
  • context_gaps
  • response_strategy when it helps the answer land cleanly

Only surface fields that materially help the user. Omit empty sections. Keep the framing short enough that the answer still feels direct.

For response shapes by task type, read references/output-patterns.md.

Critique Pass

Before finalizing, check for:

  • missing constraints
  • unsupported assumptions
  • plan steps that are too broad or too brittle
  • uncertainty that should be made explicit
  • context gaps that, if resolved, would change the answer materially

If the critique finds meaningful issues, tighten the answer and surface only the user-relevant residue.

Stop Conditions

De-escalate to a direct answer when:

  • the task is low complexity
  • the plan adds no meaningful value
  • the critique produces no user-relevant caution
  • visible meta framing would be longer than the useful content

Anti-goals

  • Do not reveal chain-of-thought or hidden scratch work.
  • Do not force every answer into a verbose template.
  • Do not use this as a generic "think harder" wrapper.
  • Do not turn the task into a lesson on metacognition unless the user asks for that.

References

  • Read references/second-order-method.md for the canonical method, terminology, and gating heuristics.
  • Read references/output-patterns.md for compact response patterns by task type.
  • Read references/examples.md for realistic trigger and non-trigger examples.

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.