logical-thinking
Skill136 starsChanged 5 months agoMITView on GitHub
Determine what premises and evidence warrant.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- kanekoshoyu/hot-potatotheir own version, first seen Sep 18, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- kanekoshoyu/hot-potato★ 4same name
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.
In this repository80 other files it gives its agents.
- AGENTS.mdAGENTS.md
- accessibility-audit-websitesSkill
- accessibility-performance-polishSkill
- agent-evaluation-operationsSkill
- agent-memory-provenanceSkill
- agent-orchestration-architectureSkill
- animation-easing-languageSkill
- animation-jank-qaSkill
- animation-tool-routerSkill
- anti-generic-website-reviewSkill
- brand-voice-to-ui-copySkill
- browser-inspection-workflowSkill
- code-change-safety-checkpointSkill
- code-change-undo-revertSkill
- color-material-lighting-directionSkill
- content-pruning-reviewSkill
- content-structure-information-architectureSkill
- conversion-forms-checkout-polishSkill
- creativitySkill
- critical-thinkingSkill
- cross-browser-qaSkill
- css-grid-editorial-systemsSkill
- cta-language-systemsSkill
- deep-researchSkill
- design-motion-principlesSkill
- editorial-typography-systemsSkill
- evidence-reconciliationSkill
- final-client-handoffSkill
- frontend-quality-auditorSkill
- frontend-tooling-trust-gateSkill
- gsap-performanceSkill
- hero-image-art-directionSkill
- image-crop-responsive-qaSkill
- image-video-loading-qaSkill
- mobile-responsive-qaSkill
- modern-site-engineeringSkill
- motion-language-directorSkill
- motion-performance-qaSkill
- motion-react-layout-transitionsSkill
- motion-react-microinteractionsSkill
- motion-react-page-transitionsSkill
- motion-react-patternsSkill
- nextjs-app-router-routingSkill
- nextjs-server-client-boundariesSkill
- nextjs-site-architectureSkill
- non-generic-web-copySkill
- performance-audit-websitesSkill
- performance-budget-labSkill
- premium-visual-reference-librarySkill
- premium-web-build-gateSkill
- radix-accessible-primitivesSkill
- react-accessible-componentsSkill
- react-component-compositionSkill
- react-component-craftSkill
- react-error-loading-empty-statesSkill
- react-form-patternsSkill
- react-responsive-componentsSkill
- react-state-and-effects-disciplineSkill
- reduced-motion-designSkill
- responsive-visual-polish-qaSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 16
Use conditional or unknown when warranted.
- Distinctive: line 62
Entailed: every model satisfying the premises satisfies C.
- Very specific: line 63
Contradicted: every model satisfying the premises satisfies not C, or C directly conflicts with a controlling premise.
- Distinctive: line 67
Check premise consistency first, then classify the target as entailed, contradicted or unknown.
≈ “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.
Files
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 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
Before inference, identify:
- exact question and candidate conclusion;
- premises, observations, rules, and documentation;
- source/status of each premise: given, observed, documented, inferred, assumed, or disputed;
- definitions, entities, variables, units, timeframe, version, and domain;
- quantifiers and modal force: all, some, none, must, may, usually, likely;
- knowledge regime: closed world, open world, or incomplete real-world evidence;
- hidden premises required to connect the stated information.
Resolve semantic ambiguity before formalizing. Do not create precision by translating an unclear sentence into symbols without deciding what the sentence means.
Choose the inference family
| Family | Appropriate question | Valid conclusion form |
| Deductive | Must the conclusion follow? | entailed, contradicted, or unknown |
| Defeasible/informal | Is the argument presumptively reasonable? | supported unless a critical exception succeeds |
| Inductive | How strongly do observations generalize? | scoped probability or empirical support |
| Abductive | Which explanation best accounts for the evidence? | best current explanation, not proof |
| Causal | What would happen under intervention or counterfactual change? | association, intervention effect, or counterfactual claim |
| Probabilistic | How should uncertainty update? | posterior or calibrated range under assumptions |
| Documentary/rule | What does an authority establish here? | governing, permitted, required, documented, or unresolved applicability |
| Decision | Which action is preferable under uncertainty? | recommendation conditional on goals and tradeoffs |
For formal entailment, natural-language arguments, exceptions, or scheme-based reasoning, read formal and defeasible inference.
For causal, probabilistic, forecasting, or decision reasoning, read causal, probabilistic, and decision reasoning.
For conclusions from documentation, policies, tests, benchmarks, source code, or runtime evidence, read documentation and evidence conclusions.
Keep unknown open
Under an open-world or incomplete-evidence regime:
- failure to prove C does not prove
not C; - failure to prove
not Cdoes not prove C; - one absent fact does not license a closed-world assumption unless the system explicitly defines one;
- inconsistent premises do not justify an arbitrary conclusion in ordinary analysis.
Classify a deductive target as:
- Entailed: every model satisfying the premises satisfies C.
- Contradicted: every model satisfying the premises satisfies
not C, or C directly conflicts with a controlling premise. - Unknown: both C and
not Cremain compatible with the premises. - Premises inconsistent: the premise set itself requires repair before ordinary inference.
Check premise consistency first, then classify the target as entailed, contradicted or unknown; do not force a binary answer from incomplete evidence.
Coordinate boundaries
Use critical-thinking when the central question is whether evidence, assumptions, incentives, or argument quality deserves confidence. Use evidence-reconciliation when conflicting authority or current source state controls. Use deep-research when premises must be discovered. Use creativity when the missing work is generating possibilities rather than adjudicating what follows.
Deliver
For simple problems, apply the protocol silently and answer directly. For consequential problems, report the normalized premises, inference family, decisive rule or test, exceptions or unknowns, verification performed, and strongest warranted conclusion. Show enough structure to audit the result without dumping private scratch reasoning.
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
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.

