Scientific Clarity Checker
Reviews scientific documents for logical clarity, argument soundness, and rigor by auditing hypothesis-data alignment, claim-evidence chains, quantitative precision, hedging calibration, and terminology consistency across any document type. Use when reviewing scientific argumentation, checking claims vs evidence, auditing terminology, or when user mentions check clarity, review logic, scientific soundness, hypothesis-data alignment, or claims vs evidence.
Install
/plugin marketplace add lyndonkl/claudeThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add lyndonkl/claude --skill scientific-clarity-checkergit clone --depth 1 https://github.com/lyndonkl/claude.git /tmp/claude
mkdir -p ~/.claude/skills
cp -r /tmp/claude/skills/scientific-clarity-checker ~/.claude/skills/scientific-clarity-checkerPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Scientific Clarity Checker ## Table of Contents - [Core Principles](#core-principles) - [Workflow](#workflow) - [Analysis Frameworks](#analysis-frameworks) - [Common Issues](#common-issues) - [Guardrails](#guardrails) - [Quick Reference](#quick-reference) ## Core Principles **1. Claims must match evidence**: Every conclusion needs explicit support **2. Precision over vagueness**: Quantify wherever possible **3. Hedging matches certainty**: Strong claims need strong evidence **4. Logic must flow**: Arguments should be traceable step by step **5. Terminology must be consistent**: Same concept = same word **6. Mechanistic clarity**: The "how" should be explained, not just "what" ## Workflow Copy this checklist and track your progress: ``` Clarity Check Progress: - [ ] Step 1: Identify core claims and hypotheses - [ ] Step 2: Structural logic review (argument flow) - [ ] Step 3: Claims-evidence audit - [ ] Step 4: Quantitative precision check - [ ] Step 5: Terminology consistency audit - [ ] Step 6: Hedging calibration - [ ] Step 7: Mechanistic clarity check ``` **Step 1: Identify Core Claims** List all major claims, conclusions, and hypotheses in the document. These are what the author wants readers to believe after reading. Every claim needs to be evaluated. See [resources/methodology.md](resources/methodology.md#claim-identification) for claim extraction. **Step 2: Structural Logic Review**
Details
- Skill name
scientific-clarity-checker- Repository
- lyndonkl/claude
- Path
skills/scientific-clarity-checker/SKILL.md- Repo updated
- 1 September 2026
FAQ
What does the Scientific Clarity Checker skill do?
Reviews scientific documents for logical clarity, argument soundness, and rigor by auditing hypothesis-data alignment, claim-evidence chains, quantitative precision, hedging calibration, and terminology consistency across any document type. Use when reviewing scientific argumentation, checking claims vs evidence, auditing terminology, or when user mentions check clarity, review logic, scientific soundness, hypothesis-data alignment, or claims vs evidence.
How do I install the Scientific Clarity Checker skill?
Claude Code plugin: /plugin marketplace add lyndonkl/claude. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Scientific Clarity Checker popular?
It lives in lyndonkl/claude, which has 200 GitHub stars and 25 forks.
Related skills
Abstraction Concrete Examples
200lyndonkl/claude
Builds structured abstraction ladders that translate high-level principles into concrete, actionable examples across 3-5 levels. Bridges communication gaps, reveals hidden assumptions, and tests whether abstract ideas work in practice. Use when explaining concepts at different expertise levels, moving between abstract principles and concrete implementation, identifying edge cases by testing ideas against scenarios, designing layered documentation, decomposing complex problems into actionable steps, or bridging strategy-execution gaps.
Academic Letter Architect
200lyndonkl/claude
Guides the creation of evidence-based academic recommendation letters, reference letters, and award nominations that combine concrete examples, meaningful comparisons, and genuine enthusiasm. Use when writing recommendation letters for students, postdocs, or colleagues, or when user mentions recommendation letter, reference, nomination, letter of support, endorsement, or needs help with strong advocacy and comparative statements.
Adr Architecture
200lyndonkl/claude
Documents significant architectural and technical decisions with full context, alternatives considered, trade-offs analyzed, and consequences understood. Creates a decision trail that helps teams understand why decisions were made. Use when choosing between technology options, making infrastructure decisions, establishing standards, migrating systems, or when user mentions ADR, architecture decision, technical decision record, or decision documentation.
Scientific Email Polishing
200lyndonkl/claude
Composes and polishes professional scientific correspondence -- emails to collaborators, journal cover letters, and responses to peer reviewers -- ensuring clear communication, appropriate tone, explicit asks, and professional formatting for academic contexts. Use when writing or polishing scientific emails, cover letters to editors, reviewer responses, or when user mentions email to collaborator, cover letter to journal, reviewer response, or professional scientific correspondence.
Scene Construction Scam
200lyndonkl/claude
Builds scenes that are reported rather than generated, by running a four-slot SCAM qualification gate (Setting, Character, Action, Meaning) with a source required per slot, a scene floor and ceiling, the 1-of-20 telling-detail cut with a provenance veto, the RUE pass, and a scene/summary narrative-distance audit against per-form ratio targets. Every technique has a person variant and a system variant (market, protocol, institution, codebase, supply chain). Use when turning research notes into a scene, opening a section with a moment, deciding whether a passage is a scene or summary, or auditin
Scientific Manuscript Review
200lyndonkl/claude
Guides systematic multi-pass review and editing of scientific manuscripts (research articles, reviews, perspectives) to improve clarity, structure, scientific rigor, and reader comprehension. Use when reviewing or editing research manuscripts, journal articles, or perspectives, when user mentions manuscript, paper draft, article, research writing, journal submission, reviewer feedback, or needs to improve scientific writing.
Browse the most popular Claude skills, all research & science skills, or write your own with the skills generator.