CtrlK
BlogDocsLog inGet started
Tessl Logo

scientific-critical-thinking

Evaluate scientific claims and evidence quality. Use for assessing experimental design validity, identifying biases and confounders, applying evidence grading frameworks (GRADE, Cochrane Risk of Bias), or teaching critical analysis. Best for understanding evidence quality, identifying flaws. For formal peer review writing use peer-review.

68

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is scientific-critical-thinking in K-Dense-AI/scientific-agent-skills

SKILL.md
Quality
Evals
Security

Quality

Content

71%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured procedural skill: clear critique structure with severity tiers, concrete conditional-assessment phrasings, and excellent one-level-deep progressive disclosure verified against the real bundle. The main drag is redundancy — three sections restate either the frontmatter description or each other — and the absence of a single worked critique example.

Suggestions

Cut the "Reference Materials" section's file-by-file re-listing — it duplicates the six reference links already given under "Core Capabilities"; keep one listing with the "when to consult" guidance attached.

Remove or merge the "Remember" section, which restates the Application Guidelines principles (constructive critique, proportional confidence, consistent standards) nearly verbatim.

Replace the "When to Use This Skill" bullet list (a restatement of the description) with one short worked example, e.g., a two-line sample critique applying the Summary → Concerns-by-severity → Recommendations template to a flawed study.

DimensionReasoningScore

Conciseness

The body is mostly efficient but carries clear padding: "When to Use This Skill" restates the frontmatter description, the "Reference Materials" section re-lists all six reference files already linked under "Core Capabilities", and "Remember" restates the Application Guidelines principles. Fits the 3 anchor ('could be tightened'); not 2 because no section over-explains concepts Claude already doesn't know (no 'what is a p-value' material), and not 4 because the duplication is substantial rather than minor.

3 / 5

Actionability

Concrete, actionable guidance for an instruction-only skill: an explicit five-part critique structure ("Summary / Strengths / Concerns organized by severity with Critical/Important/Minor tiers / Specific Recommendations / Overall Assessment"), copy-ready conditional phrasings ("If X was done, then Y follows; if not, then Z is concern"), and executable commands (grep for references, the scientific-schematics invocation). Not 5 because the "General Approach" principles ("Be Constructive", "Consider Context") are abstract advice with no worked example of applying them or of a GRADE assessment.

4 / 5

Workflow Clarity

The critique workflow is clearly sequenced with severity-graded checkpoints and an explicit feedback structure, plus a separate "When Uncertain" branch for conditional assessment. Not 5 because the end-to-end process (assess capability areas → consult references → produce structured feedback) is implied by section order rather than stated as an ordered procedure. Not 3 because the sequencing and checkpoints that are present are explicit, and no destructive/batch validation cap applies.

4 / 5

Progressive Disclosure

Verified against the actual bundle: all seven referenced files exist in references/ exactly as linked, references are one level deep with no nesting, and navigation is well signaled — a numbered capability map linking core_capabilities.md, per-topic reference links, and a "When to consult references" section including a grep command. Content is appropriately split between the overview and references, matching the 5 anchor; the duplicate reference listing is a conciseness flaw, not a navigation gap.

5 / 5

Total

16

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: third-person voice, concrete named-framework actions, an explicit 'Use for...' trigger clause, and explicit de-confliction guidance against the peer-review skill. The only weakness is a handful of missing natural trigger phrasings users might say (e.g., 'study quality', 'methodology critique').

DimensionReasoningScore

Specificity

Quotes multiple concrete actions: "Evaluate scientific claims and evidence quality", "assessing experimental design validity, identifying biases and confounders, applying evidence grading frameworks (GRADE, Cochrane Risk of Bias)". The actions are specific and named-framework-level, comprehensively covering the skill's domain. Not 4 because coverage has no meaningful gaps; not below 5 because no generic filler is present.

5 / 5

Completeness

Explicitly answers both: what — "Evaluate scientific claims and evidence quality"; when — "Use for assessing experimental design validity, identifying biases and confounders, applying evidence grading frameworks (GRADE, Cochrane Risk of Bias), or teaching critical analysis". Concrete trigger phrases and an explicit use-when clause match the 5 anchor; below 5 would require a weak or implied 'when', which is not the case.

5 / 5

Trigger Term Quality

Good natural-term coverage: "scientific claims", "evidence quality", "experimental design", "biases and confounders", "critical analysis", "peer review", plus named frameworks (GRADE, Cochrane Risk of Bias). A few natural user phrasings are missing (e.g., "study quality", "methodology critique", "risk of bias" as a standalone phrase), so it sits at the 4 anchor rather than 5.

4 / 5

Distinctiveness Conflict Risk

Clear niche (critical evaluation of scientific evidence) with an explicit boundary clause: "For formal peer review writing use peer-review". This actively disambiguates against the nearest competing skill, giving minimal conflict risk — the 5 anchor; anchor 4's 'minor overlap risk' understates the explicit routing guidance present.

5 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
K-Dense-AI/claude-scientific-writer
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.