Menu

Individual skill

logical-thinking

0upvotes

Determine what premises and evidence warrant.

skills/logical-thinking/SKILL.md

Read pinned source

Source commit 9922fa0af0aea32443cf7365ef5024dc7797382d

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
137
Repository last updated
Oct 22, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Logical Thinking

Produce the strongest conclusion the available premises warrant, including `unknown`, conditional, or no conclusion when appropriate. Logical rigor means choosing the right inference system, preserving meaning and scope, checking each decisive step, and refusing to strengthen the result beyond its proof obligations.

## Scale the proof to the question

Adapt the inference family; do not impose a universal template. Preserve meaning, units, scope and quantifiers. Test whether premises can hold while the conclusion fails; use decisive calculations, solvers, tests or observations. Correlated self-review is not independent verification.

For **consequential, multi-step, ambiguous or contested inference**, read [proof and verification](references/proof-and-verification.md) plus the applicable family below for maps, step checks, conclusion types and adversarial tests. Simple entailment/calculation remains direct.

Use conditional or unknown when warranted. `Proven`, `must`, `causes`, `always` and `impossible` require their own proof burden.

## Normalize the problem
Back to top