CtrlK
BlogDocsLog inGet started
Tessl Logo

fact-checking

Review and validate claims using counter-hypothesis testing. Use when verifying technical content, checking references, validating API endpoints, or performing quality assurance on deliverables.

66

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./.squad/skills/fact-checking/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%

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

A compact, well-organized methodology skill with a ready-to-use output template, weakened mainly by abstract core technique guidance and an implicit rather than explicit validation feedback loop.

Suggestions

Add one concrete worked example of counter-hypothesis testing (a sample claim, a counter-hypothesis, and the resulting verdict) to lift actionability.

Make the feedback loop explicit: after a ⚠️/❌ verdict, state the re-investigation gate (e.g., "re-test up to 3 cycles, only PASS when all claims are ✅ or justified ⚠️") so workflow clarity reaches the validation-checkpoint anchor.

De-duplicate the ✅/⚠️/❌ legend, which appears both in the methodology step and again in the Confidence Levels section.

DimensionReasoningScore

Conciseness

The body is lean: it states methodology, a compact output template, confidence levels, and a spawn command without explaining what fact-checking is or padding with concepts Claude already knows; nearly every token earns its place.

3 / 3

Actionability

The output-format table and the ceremony spawn template are copy-paste ready, but the core methodology steps ("Generate counter-hypotheses and test them against available data") stay abstract without a concrete technique or worked example, leaving guidance incomplete.

2 / 3

Workflow Clarity

A clear 4-step review sequence is present and confidence flags act as a checkpoint, but the validation/feedback loop is mostly implicit — there is no explicit "re-test until resolved" gate tying the ✅/⚠️/❌ verdicts back to a retry decision.

2 / 3

Progressive Disclosure

This is a short single-purpose skill (under 50 lines, no bundle files) organized into clearly labeled sections (Context, Pattern, Confidence Levels, Ceremony Integration), so the simple-skill carve-out applies and structure alone earns full credit.

3 / 3

Total

10

/

12

Passed

Description

85%

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, third-person description with an explicit Use-when clause and concrete actions; its main gap is trigger-term coverage, which lacks the most colloquial phrasings a user might invoke.

Suggestions

Add natural trigger terms users would actually say (e.g., "fact-check", "double-check claims", "audit a deliverable") to broaden trigger coverage.

Consider mentioning the verdict/output framing (e.g., "produces a structured fact-check report") so the deliverable shape is signaled in the description.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Review and validate claims using counter-hypothesis testing", "verifying technical content", "checking references", "validating API endpoints", "quality assurance" — matching the multiple-specific-actions anchor.

3 / 3

Completeness

Explicitly states what ("Review and validate claims using counter-hypothesis testing") and when ("Use when verifying technical content, checking references, validating API endpoints, or performing quality assurance on deliverables"), satisfying both halves.

3 / 3

Trigger Term Quality

Includes relevant natural terms ("verifying technical content", "checking references", "quality assurance") but omits common variations a user would actually say like "fact-check", "double-check", or "audit", so coverage is partial.

2 / 3

Distinctiveness Conflict Risk

The "counter-hypothesis testing" framing and specific triggers (API endpoint validation, reference checking) carve a clear niche unlikely to fire for unrelated skills.

3 / 3

Total

11

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
bradygaster/squad
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.