CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

paper-claim-audit

Zero-context verification that every number, comparison, and scope claim in the paper matches raw result files. Uses a fresh cross-model reviewer with NO prior context to prevent confirmation bias. Use when user says "审查论文数据", "check paper claims", "verify numbers", "论文数字核对", or before submission to ensure paper-to-evidence fidelity.

Quality

82%

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

SKILL.md
Quality
Evals
Security

Quality

Content

77%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 highly actionable, well-sequenced audit workflow with excellent validation checkpoints and copy-paste-ready templates. Its weaknesses are repetition of the zero-context/thread-freshness rules and the absence of any bundle files, leaving substantial detail material inlined in SKILL.md.

Suggestions

State the fresh-thread rule once (e.g., in Key Rules) and have Step 2 and the Thread independence section reference it, removing the duplicated CRITICAL note and repeated exclusion list.

Move the Submission Artifact Emission JSON schema and the verdict decision table into a references/ file (e.g., references/artifact-schema.md), keeping only the path convention and NOT_APPLICABLE/BLOCKED emission rules inline in SKILL.md.

Extract the full reviewer prompt template into references/audit-prompt.md, leaving a short parameterization summary (inputs, model, effort) in Step 2.

DimensionReasoningScore

Conciseness

Mostly operational content Claude could not infer (verdict decision table, path conventions, exact MCP contract), but the zero-context/fresh-thread rule is stated three times (Step 2 CRITICAL note, Key Rules, and the Thread independence section) and the excluded-files list is duplicated between Core Principle and Step 1, which is more than minor trimming.

3 / 5

Actionability

Fully executable: exact MCP tool names with model/config, a complete copy-paste reviewer prompt with audit protocol and per-claim output fields, report templates for MD and JSON, a concrete artifact schema, and path conventions with the paper/paper/main.tex false-fail example.

5 / 5

Workflow Clarity

Steps 1-4 are clearly sequenced with explicit validation checkpoints: a verdict decision table covering every input state (including ERROR), PASS/WARN/FAIL handling rules, a non-blocking render-failure fallback, and an external verifier rehash check for stale artifacts.

5 / 5

Progressive Disclosure

Sections are well-organized with clearly signaled one-level references to shared-references docs, but the bundle contains no reference files at all; the ~60-line reviewer prompt and ~80-line artifact schema/decision tables are inlined in a 360-line SKILL.md where a references/ split would be appropriate.

3 / 5

Total

16

/

20

Passed

Description

83%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: concrete third-person capabilities, explicit what-and-when structure with quoted trigger phrases (in two languages), and a well-delineated niche. Only minor gaps in action coverage and synonym triggers keep it off the top anchor on two dimensions.

DimensionReasoningScore

Specificity

Names several concrete actions (verify every number, comparison, and scope claim against raw result files; uses a fresh cross-model reviewer with no prior context to prevent confirmation bias) in third person, but is not a comprehensive multi-action list as in the anchor-5 example.

4 / 5

Completeness

Explicitly answers both what (zero-context verification that paper claims match raw result files via a fresh cross-model reviewer) and when ("Use when user says ... or before submission") with concrete quoted trigger phrases, matching the anchor-5 pattern.

5 / 5

Trigger Term Quality

Natural phrases users would actually say ("check paper claims", "verify numbers", "before submission") plus bilingual triggers, but misses common synonyms like "audit paper", "paper numbers", or "verify results".

4 / 5

Distinctiveness Conflict Risk

Clear niche (paper-to-evidence fidelity at submission time) that is distinct from general paper-writing or experiment-code audits; only minor overlap risk with sibling audit skills in the same family.

4 / 5

Total

17

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 2 suspicious

Warning

Total

13

/

16

Passed

Repository

wanshuiyin/Auto-claude-code-research-in-sleep

Path

skills/paper-claim-audit/SKILL.md

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.