CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

audit-reproducibility

Enforce the replication-protocol.md rule by cross-checking numeric claims in a manuscript against the actual R / Stata / Python outputs. Report PASS/FAIL per claim against tolerance thresholds. Use before submission and before releasing a replication package.

Quality

70%

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 ./.agents/skills/audit-reproducibility/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

51%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.

The body is a token-efficient wrapper whose sole substantive instruction is to defer to an external file that is not present in the skill bundle, leaving the skill non-self-contained and the actual audit workflow undefined. Conciseness is excellent, but actionability and workflow clarity are weak because no domain guidance exists in the file itself, and progressive disclosure rests entirely on a redirect that dead-ends.

Suggestions

Inline the core audit procedure (or at least a concise summary: extract numeric claims, compare against R/Stata/Python outputs, apply tolerance thresholds, report PASS/FAIL per claim) so the skill remains actionable when the source path is unavailable.

Add the domain workflow as a numbered sequence with validation checkpoints, e.g. per-claim tolerance comparison and a re-check loop for FAILed claims, since this is a batch verification task.

Ensure the referenced path (../../../.claude/skills/audit-reproducibility/SKILL.md) resolves within the skill bundle, or copy the source instructions into a references/ file and link to that instead.

DimensionReasoningScore

Conciseness

The ~25-line body is lean and efficient: no concept explanations, no padding, and each bullet ('Arguments', 'Fresh context', 'Guards') carries concrete environment guidance Claude would not otherwise know. Fits the 'lean and efficient; every token earns its place' anchor rather than the 'minor over-explanation' anchor at 4.

5 / 5

Actionability

The only executable guidance is meta-level — 'Read that file now and follow it, with the files it points to' — with no steps, commands, or examples for the actual claim-audit task, and the referenced source file does not exist within the skill bundle so the redirect dead-ends. Matches 'minimal concrete guidance; high-level hints but missing the specific steps to execute'; not 1 because the read-order directives with specific paths are executable.

2 / 5

Workflow Clarity

Only a meta-sequence is present ('Read AGENTS.md first', then the source SKILL.md); the audit workflow itself — claim extraction, tolerance comparison, PASS/FAIL reporting, re-checking failures — is entirely absent, with no validation checkpoints for this batch-claim-checking task. Matches 'rough sequence present but many gaps; validation absent'; not 3 because there are no domain steps listed at all, only the redirect.

2 / 5

Progressive Disclosure

The single reference is clearly signaled, linked, and one level deep, but the body is a pure redirect with no overview of its own and the bundle contains no content files (no references/, scripts/, or assets/), so the referenced path resolves outside the bundle. Not 4 because navigation dead-ends within the bundle; not 2 because the reference is not buried and structure is minimal-but-clear.

3 / 5

Total

12

/

20

Passed

Description

78%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 actions, an explicit use-when clause, and a well-defined niche with domain-natural trigger terms. Its main weakness is the absence of common synonyms and user-utterance trigger phrases (e.g. 'verify numbers', 'replicate results') that would push trigger coverage and completeness to the top level.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'cross-checking numeric claims in a manuscript against the actual R / Stata / Python outputs' and 'Report PASS/FAIL per claim against tolerance thresholds' — with minor gaps such as what happens on FAIL or the report format. Not 5 because coverage is not comprehensive; not 3 because it goes beyond 1-2 actions with specific, concrete verbs.

4 / 5

Completeness

Explicitly answers 'what' (cross-check numeric claims, report PASS/FAIL against tolerances) and 'when' ('Use before submission and before releasing a replication package'). Not 5 because the 'when' clause is lifecycle-timing based rather than concrete user-utterance trigger phrases; not 3 because an explicit 'Use when...' clause is present.

4 / 5

Trigger Term Quality

Good natural keyword coverage: 'manuscript', 'replication package', 'submission', 'R / Stata / Python outputs'. A few natural terms are missing, e.g. 'reproducibility check', 'verify numbers', 'replicate results'. Not 5 because synonyms and common user phrasings are absent; not 3 because coverage is solid rather than partial.

4 / 5

Distinctiveness Conflict Risk

A clear niche — auditing numeric manuscript claims against statistical package outputs for replication packages — with distinct triggers, so conflict risk with other skills is minimal. Clearly matches the anchor for a distinct niche rather than the 'minor overlap risk' anchor below.

5 / 5

Total

17

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 2 suspicious

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

14

/

16

Passed

Repository

pedrohcgs/claude-code-my-workflow

Path

.agents/skills/audit-reproducibility/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.