CtrlK
BlogDocsLog inGet started
Tessl Logo

experiment-audit

Audit experiment integrity before claiming results. Uses cross-model review (external reviewer backend) to check for fake ground truth, score normalization fraud, phantom results, and insufficient scope. Use when user says "审计实验", "check experiment integrity", "audit results", "实验诚实度", or after experiments complete before writing claims.

71

Quality

88%

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

77%

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

The body is highly actionable with a clear sequenced workflow and concrete reviewer calls, but is denser than ideal: conceptual rationale and a long inline audit prompt could be offloaded. Referenced shared-references files are not present in the bundle, weakening navigation.

Suggestions

Trim conceptual padding — remove or shorten 'Why This Exists' rationale and the 'These are NOT intentional deception' editorializing, which explains concepts Claude already grasps.

Extract the ~70-line audit prompt and the EXPERIMENT_AUDIT report templates into a referenced file (e.g., references/audit-prompt.md) so SKILL.md stays a lean overview with one-level-deep references.

Either supply the referenced shared-references/*.md files in the bundle or replace the dangling links with inline pointers, since the current references cannot be resolved.

DimensionReasoningScore

Conciseness

Mostly efficient and instruction-oriented, but includes conceptual padding (e.g., 'These are NOT intentional deception — they are failure modes of optimizing agents') and a 'Why This Exists'/'Acknowledgements' rationale that assumes less competence than warranted; could be tightened.

2 / 3

Actionability

Provides concrete file-scan glob patterns, exact reviewer MCP call signatures with model/config/sandbox parameters, a full copy-paste audit prompt, and exact output report templates — fully executable guidance.

3 / 3

Workflow Clarity

A clearly sequenced 4-step workflow (collect artifacts → send to reviewer → parse/write report → print summary) with explicit validation checkpoints (reviewer reads directly, PASS/WARN/FAIL verdict) and an integration diagram.

3 / 3

Progressive Disclosure

Structure is present and references to shared-references/*.md are signaled, but the body is somewhat monolithic with the ~70-line audit prompt and full report templates inline; the referenced shared-references files do not exist in the bundle, so navigation is not actually resolvable.

2 / 3

Total

10

/

12

Passed

Description

100%

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

The description is specific, bilingual, and complete, with explicit 'Use when' triggers covering what the skill does and when to invoke it. It occupies a distinct niche unlikely to conflict with other skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'check for fake ground truth, score normalization fraud, phantom results, and insufficient scope' — matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers both what ('Audit experiment integrity... Uses cross-model review to check for...') and when ('Use when user says...'), with explicit 'Use when' trigger guidance.

3 / 3

Trigger Term Quality

Provides good coverage of natural terms users would say in both English ('check experiment integrity', 'audit results') and Chinese ('审计实验', '实验诚实度'), matching the top anchor.

3 / 3

Distinctiveness Conflict Risk

A clearly defined niche (experiment integrity auditing) with distinct bilingual triggers unlikely to fire for unrelated skills, matching the 'clear niche with distinct triggers' anchor.

3 / 3

Total

12

/

12

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.

Validation13 / 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: 1 suspicious

Warning

Total

13

/

16

Passed

Repository
wanshuiyin/Auto-claude-code-research-in-sleep
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.