CtrlK
BlogDocsLog inGet started
Tessl Logo

article-fact-checker

三层审查模型,逐段逐句验证文章真伪、证据链与逻辑结构。Use when the user asks to fact-check, verify, audit, or evaluate the credibility of an article, essay, report, opinion piece, social-media post, or any written claim — including checking logical consistency, evidence chains, source reliability, fabrication, non-quantifiable conclusions, and producing a scored report with original-text citations.

77

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

92%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-engineered instruction-only skill body: lean table-driven content, a clearly sequenced six-pass workflow with explicit triangulation and counter-evidence checkpoints, and clean progressive disclosure into a verified one-level reference bundle. The single notable gap is that the automation script is referenced without a usage example, which keeps actionability just below the top anchor.

Suggestions

Add a one-line invocation example for scripts/evidence-extractor.py in Pass 3 and the Resources section (e.g. `python scripts/evidence-extractor.py <article-file> -o evidence-list.json`) so the automation step is copy-paste ready like the reverse-search commands.

Show 1-2 concrete filled-in rows of the L1/L2/L3 scoring rubric (or point to where the per-dimension 1-5 anchors live) so '各维 1-5 分' is unambiguous at scoring time.

State where the weighting override is documented or how to adjust L1/L2/L3 weights by article type, since the body mentions '可按文章类型调整' without a rule or pointer.

DimensionReasoningScore

Conciseness

The body is lean and dense: tables instead of prose (evidence-type/reverse-search table, 6-dimension qualitative table, time-budget table), an ASCII evidence-chain skeleton, and per-pass time budgets — with zero padding or explanation of concepts Claude already knows. Not 4 because there is no over-explanation to trim; every section carries operational information.

5 / 5

Actionability

Guidance is largely executable: copy-paste-ready reverse-search commands per evidence type (e.g. `data:"<具体数字>"`, `<作者> <期刊> <年份>`), a concrete default weighting (L1=30%/L2=30%/L3=40%), a report template to copy, and a named script. It falls short of the 5 anchor only because `scripts/evidence-extractor.py` is referenced twice with no invocation example or arguments, so that step is not fully copy-paste ready.

4 / 5

Workflow Clarity

The six-pass workflow is explicitly sequenced ("按顺序执行,每遍只解决一层问题"), each pass has a time budget and a defined question, and verification checkpoints are explicit: reverse-search per high-risk evidence, "每个核心主张找 ≥2 个独立(无相互引用)来源" triangulation, counter-evidence (反证 R) in the chain check, plus a degradation path when time is short. This matches the anchor with explicit validation steps and error/edge handling.

5 / 5

Progressive Disclosure

SKILL.md is an overview that inlines only the decision-level detail and points to a real, one-level-deep bundle: all 7 referenced reference files, the script, and the report template exist, spot-checking confirms the reference files are substantive (peer cross-links at most, no 'see details.md' chains), and a Resources section indexes each file with its purpose. Content is appropriately split and navigation is easy.

5 / 5

Total

19

/

20

Passed

Description

100%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: it states a concrete three-layer capability set with a defined output artifact and pairs it with an explicit, well-enumerated 'Use when' clause covering synonyms and content types. All four dimensions sit at the top anchors with no padding or over-claims.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "逐段逐句验证文章真伪、证据链与逻辑结构" plus "checking logical consistency, evidence chains, source reliability, fabrication, non-quantifiable conclusions, and producing a scored report with original-text citations" — comprehensive coverage with no vague filler. Not 4 because coverage spans verification, evidence-chain analysis, fabrication detection, and a defined output artifact, matching the multi-action comprehensive anchor.

5 / 5

Completeness

It explicitly answers both: what ("三层审查模型" that verifies authenticity, evidence chains, and logical structure, producing a scored cited report) and when ("Use when the user asks to fact-check, verify, audit, or evaluate the credibility of..."). This matches the anchor example for a clear what plus a concrete 'Use when' trigger clause; neither half is missing or weak.

5 / 5

Trigger Term Quality

Natural trigger terms users would actually say are well covered: "fact-check, verify, audit, or evaluate the credibility of an article, essay, report, opinion piece, social-media post, or any written claim" — synonyms (fact-check/verify/audit/evaluate) and artifact types are enumerated. Not 4 because essentially all common phrasings of this need are present rather than 'a few natural terms missing'.

5 / 5

Distinctiveness Conflict Risk

It occupies a clear niche (article/claim credibility auditing with a scored, citation-backed report) with triggers that are distinct from writing, summarizing, or general research skills. Minor overlap with source-verification behaviors exists, but the enumerated triggers are specific enough that conflict risk is minimal.

5 / 5

Total

20

/

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
digoal/blog
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.