agentleFS
Sign inStart free
AgriciDanielAgriciDaniel/claude-obsidian/skills/think/SKILL.md

think

Skill16k starsChanged 52 days agoMITView on GitHub

Apply the Fable-derived 10-stage OBSERVE, OBSERVE, LISTEN, THINK, CONNECT, CONNECT, FEEL, ACCEPT, CREATE, GROW loop to consequential or ambiguous reasoning and decisions. Use for think this through, deep think, architecture review, postmortem, tradeoff analysis, or challenges to assumptions. This is a reasoning review, not a deterministic vault health check or repair workflow.

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 21 edited versions we read keep these.

  • 11

    Distinctive

    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 the ten stages as a loop of attention, not a ceremonial transcript.

    line 8
  2. Distinctive:

    CREATE stage recommends a change, compose with the appropriate mutation skill after the user authorizes that operation.

    line 14
  3. Distinctive:

    Before the loop, separate:

    line 19
  4. Distinctive:

    Read the actual inputs, current state, constraints, failures, and prior work.

    line 33
  5. Distinctive:

    Prefer the smallest reversible test that could disprove the leading hypothesis.

    line 51
  6. Distinctive:

    Treat failure behavior as part of the specification.

    line 52
  7. Distinctive:

    Look for the same structure in adjacent components or another domain.

    line 56
  8. Distinctive:

    Consider the user's cognitive load, emotional state, accessibility, trust, and error-recovery experience.

    line 67
  9. Distinctive:

    Do not mutate state under this skill.

    line 82
  10. Distinctive:

    Before calling the work complete:

    line 92
  11. Distinctive:

    Test the highest-risk claim or clearly state why it remains untested.

    line 94

“Common” is measured: kept by at least 6 in 10 of the 21 edited versions of this file we could read. “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

Think

Use the ten stages as a loop of attention, not a ceremonial transcript. Scale the depth to novelty, stakes, uncertainty, and irreversibility. Keep the final reasoning summary concise and evidence-bearing.

This skill is read-only. It may inspect available evidence, but it does not edit files, execute a vault mutation, commit Git, or publish anything. If the CREATE stage recommends a change, compose with the appropriate mutation skill after the user authorizes that operation.

Establish an evidence frame

Before the loop, separate:

  • Observed: directly supported by an input, source, test, or measurement.
  • Inferred: a conclusion drawn from observations; state the bridge.
  • Unknown: missing evidence that could change the decision.
  • Preference: a user or designer choice, not a factual claim.

Attach citations or concrete locators when sources exist. Never fabricate a quotation, locator, test result, consensus, or confidence level.

The ten stages

1. OBSERVE: external

Read the actual inputs, current state, constraints, failures, and prior work. Distinguish what was inspected in full from what was sampled or assumed.

2. OBSERVE: internal

Name the biases most likely to distort this decision: anchoring, ownership, novelty, familiarity, urgency, sunk cost, confirmation, or a desired verdict. Recalibrate confidence to the evidence available.

3. LISTEN

Recover the user's intent, success condition, constraints, and unstated stakes. Attend to error messages, dissent, edge cases, and affected voices. Ask only questions whose answers could materially change the outcome.

4. THINK

Reduce the problem to invariants, alternatives, tradeoffs, and failure modes. Prefer the smallest reversible test that could disprove the leading hypothesis. Treat failure behavior as part of the specification.

5. CONNECT: lateral

Look for the same structure in adjacent components or another domain. Use an analogy only when its mapped similarities and limits are explicit.

6. CONNECT: system

Trace upstream inputs, downstream consumers, ownership, state boundaries, interfaces, and recovery paths. Check whether a locally sound decision creates an integration failure elsewhere.

7. FEEL

Consider the user's cognitive load, emotional state, accessibility, trust, and error-recovery experience. Treat intuition as a signal to investigate, never as a substitute for evidence.

8. ACCEPT

State constraints, uncertainty, contradictory evidence, and unfavorable findings plainly. Do not inflate a score, soften a material risk to please the user, or mistake agreement for correctness. Present the strongest reasonable counterargument to the preferred conclusion.

9. CREATE

Produce the smallest useful artifact: a recommendation, decision record, experiment, draft, review, or handoff. Mark assumptions and unresolved risks. Do not mutate state under this skill.

10. GROW

Define what feedback or measurement should update the decision, when to revisit it, and what lesson is reusable. Saving the lesson is a separate explicit operation composed with save.

Verification discipline

Before calling the work complete:

  1. Test the highest-risk claim or clearly state why it remains untested.
  2. Seek disconfirming evidence, not only supporting examples.
  3. Match verification effort to blast radius and reversibility.
  4. Report actual commands, sources, artifacts, or observations used.
  5. Separate a passing check from broader correctness it does not establish.
  6. Give confidence as a calibrated qualitative judgment with reasons, not as a decorative percentage.

Output shape

Adapt the headings to the task, but preserve these outcomes:

## Decision
<recommendation or artifact>

## Evidence
<observed facts and important inferences>

## Counterargument and risks
<strongest alternative, contradictions, unknowns>

## Verification
<checks performed and checks still needed>

## Growth loop
<feedback signal, revisit condition, reusable lesson>

For a trivial, reversible lookup or typo, skip the formal loop. For a consequential decision, loop back whenever a later stage exposes a missing observation or misunderstood requirement.

Download now (ZIP)

Trending

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Aug 30: 0 new projectsWeek of Sep 6: 0 new projectsWeek of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projects
Aug 2026Sep 2026Oct 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Who's talking about AgriciDaniel/claude-obsidian

The biggest 5 of 68 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 68

Talked about on GitHub, YouTube and Bluesky (68 times).

On GitHub · 37

32 more on GitHub

On YouTube · 25

20 more on YouTube

On Bluesky · 6

1 more on Bluesky
  • Other versions25 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 25

    1. tw93/Waza★ 7.4ksame name
    2. tw93/claude-health★ 7.3ksame name
    3. ninehills/skills★ 280same name
    4. garagon/nanostack★ 206same name
    5. jonathanmalkin/jules★ 65same name
    6. TserenTserenov/FMT-exocortex-template★ 63same name
    7. myclaude-sh/myclaude-creator-engine★ 25same name
    8. ironyjk/strategy-frameworks★ 14same name
    9. therealtinhtute/mono-harness★ 5same name
    10. ByronFinn/dev-skills★ 4same name

    15 more not listed

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects with it also use hunt, read and 10 more.

    Other files people use alongside this one.

    Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
    • ninehillsSkill

      hunt

      Finds root cause before applying fixes for errors, crashes, regressions, failing tests, broken behavior, and screenshot-reported defects. Use when users report in any language errors, crashes, broken behavior, regressions, failing tests, screenshot evidence, or something that used to work and now fails. Not for code review or new features.

      Also in 5 projects that use this

    • MicrosoftSkill

      read

      Read pages from a document. Returns MinerU markdown (preferred) or PyPDF text, with optional page screenshots and sub-image fetching. When markdown is available, a figure_images_meta catalog is included — use the figures parameter to fetch specific sub-image pixels. Triggers include "read page 5", "what does page 12 say", "show me the chart on page 3", "extract pages 3-5".

      Also in 5 projects that use this

    • DockerSkill

      write

      Write or edit reader-facing technical prose for immediate comprehension. Use for documentation, PR titles and descriptions, release notes, design documents, user-facing explanations, and substantive comments. Also use when asked to make writing clearer, more natural, less AI-generated, or easier to read. For documentation fixes, handles edits, formatting, self-review, and commits after research identifies what to change. Do not use for code-only tasks with no prose deliverable.

      Also in 8 projects that use this

    • genomewalkerSkill

      health

      Soul system health check with remediation

      Also in 5 projects that use this

    • kt057Skill

      check

      lint, typecheck, test を一括実行して結果をサマリーする

      Also in 6 projects that use this

    • genomewalkerSkill

      learn

      Learn from web sources, generate SKILL.md, and store key patterns in soul memory. Trigger keywords: learn, skill-gen, web-learn, documentation, tutorial.

      Also in 6 projects that use this

  • In this repository17 other files it gives its agents.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

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.

Check your setup, free