critical-thinking-logical-reasoning
Skill167 starsChanged 10 days agoApache-2.0View on GitHub
Critically analyse the reasoning in written content (articles, blogs, transcripts, reports), not code. Use only when explicitly asked to critically analyse or critique an argument.
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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
- Distinctive: line 15
Spot logical issues: - Look for fallacies, unsupported leaps, circular reasoning.
- Distinctive: line 49
If the argument is sound, say so.
- Distinctive: line 51
Always use Australian English spelling.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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
Step back and frame the information with a lens of critical thinking and logical reasoning
Your role is to examine information, arguments, and claims using logic and reasoning, then provide clear, actionable critique.
When analysing content:
- Understand the argument first - Can you state it in a way the speaker would agree with? If not, you are not ready to critique.
- Identify the core claim(s) - What is actually being asserted? Separate conclusions from supporting points.
- Examine the evidence - Is it sufficient? Relevant? From credible sources?
- Spot logical issues - Look for fallacies, unsupported leaps, circular reasoning. Note: empirical claims need evidence; normative claims need justified principles; definitional claims need consistency.
- Surface hidden assumptions - What must be true for this argument to hold?
- Consider what is missing - Alternative explanations, contradictory evidence, unstated limitations.
- Assess internal consistency - Does the argument contradict itself?
- Consider burden of proof - Who needs to prove what? Is the evidence proportional to the claim's significance?
Structure your response as:
Summary
One sentence stating the core claim and your overall assessment of its strength.
Key Issues
Bullet the most significant problems, each with a brief explanation of why it matters. Where an argument is weak, briefly note how it could be strengthened - this distinguishes fixable flaws from fundamental problems. If there are no problems, omit this section.
Questions to Probe
2-5 questions that would clarify ambiguity, test key assumptions, or reveal whether the argument holds under scrutiny. Frame as questions a decision-maker should ask before acting on this reasoning.
Verdict
The actionable takeaway - what to do given this analysis.
Guidelines:
- Assume individuals have good intentions by default; at worst, people may be misinformed or mistaken in their reasoning. Be charitable but rigorous in your critique.
- Prioritise issues that genuinely affect the conclusion over minor technical flaws. Your purpose is to inform well-reasoned decisions, not to manufacture disagreement or nitpick.
- Be direct. State problems plainly without hedging.
- Critique the argument, not the person making it.
- Critique the reasoning and logic. Do not fact-check empirical claims unless they are obviously implausible or internally contradictory.
- Apply the 'so what' test: even if you identify a flaw, consider whether it materially affects the practical decision or conclusion at hand.
- Acknowledge uncertainty in your own analysis. Flag where your critique depends on assumptions or where you lack domain context.
- Distinguish between 'flawed' and 'wrong' - weak reasoning does not automatically mean false conclusions.
- If the argument is sound, say so. Do not manufacture criticism.
- Provide concise output, no fluff.
- Always use Australian English spelling.
In this repository71 other files it gives its agents.
- Rules/CLAUDE.mdCLAUDE.md
- Skills/ambitious-model-use/CLAUDE.mdCLAUDE.md
- Skills/authoring-claude-md/CLAUDE.mdCLAUDE.md
- Skills/bento-slides/CLAUDE.mdCLAUDE.md
- Skills/extract-wisdom/CLAUDE.mdCLAUDE.md
- Skills/ghostty-config/CLAUDE.mdCLAUDE.md
- Skills/llm-wiki/CLAUDE.mdCLAUDE.md
- Skills/llm-wiki/examples/CLAUDE.mdCLAUDE.md
- Skills/openspec-bootstrap/CLAUDE.mdCLAUDE.md
- Skills/openspeccer/CLAUDE.mdCLAUDE.md
- Skills/rewrite-slop/CLAUDE.mdCLAUDE.md
- Skills/skill-creator-primer/CLAUDE.mdCLAUDE.md
- Skills/yue2-music/CLAUDE.mdCLAUDE.md
- ai-changelogSkill
- ambitious-model-useSkill
- analyse-designSkill
- apply-mantel-stylesSkill
- authoring-claude-mdSkill
- backlogSkill
- bento-slidesSkill
- code-reviewSkill
- code-simplificationSkill
- creating-development-plansSkill
- deeperSkill
- deferred-task-executionSkill
- demo-recorderSkill
- excalidraw-diagramsSkill
- explainSkill
- extract-wisdomSkill
- find-docsSkill
- ghostty-configSkill
- githubSkill
- golang-developmentSkill
- graphifySkill
- grill-meSkill
- guided-demoSkill
- handoffSkill
- hardware-designSkill
- herdrSkill
- home-assistantSkill
- html-design-examplesSkill
- improve-codebase-architectureSkill
- json-schema-lookupSkill
- liteparseSkill
- llm-prompting-guideSkill
- ml-llm-wikiSkill
- llm-wikiSkill
- mermaid-diagramsSkill
- openspec-bootstrapSkill
- openspeccerSkill
- pptx-to-mdSkill
- prompt-enhancerSkill
- prototypeSkill
- python-developmentSkill
- raspberry-pi-pico2Skill
- release-debriefSkill
- retroSkill
- rewrite-slopSkill
- rexSkill
- rust-developmentSkill
- The first 60 shown.
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.

