agentleFS
nic095laysonnic095layson/claude/.claude/skills/logic-tree/SKILL.md

logic-tree

Skill1 starsChanged 4 months agoNo licenceView on GitHub

A disciplined reasoning protocol for complex, multi-step, or high-stakes tasks — decompose into gated phases, register assumptions explicitly, predict expected outcomes before acting, truth-label every claim, and deliver with open items stated. Use whenever the user invokes it by name ("logic tree this", "use the logic tree", "run the logic tree") OR the task is genuinely complex — multiple constraints or unknowns, several steps whose later steps depend on earlier results, a plan or investigation where being wrong is costly, or a request to "figure out" something with incomplete information. Do NOT use for simple factual questions, single-step tasks, or pure judgment calls between named options (a deliberation skill like claude-council fits those better) — applying this protocol to trivia is ceremony, not rigor.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

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

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.