CtrlK
BlogDocsLog inGet started
Tessl Logo

source-audit

外部高风险 claim 与研究贡献审计。Use when: 数字、benchmark、因果、趋势、模型能力、 外部论文或会进入 docs/ADR/PPT 的结论。Not for: 低风险常识、只读官方原文且不外推、 已进入 deep-research 的重调研。Output: claim ledger + source / non-triviality / decision-fit 三轴 verdict + provenance。

63

Quality

75%

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 ./cat-cafe-skills/source-audit/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 delivers genuinely actionable audit policy — concrete templates, explicit three-axis verdicts, and well-designed pressure tests — organized in a legible sequence. Its weaknesses are redundancy (the same rules restated in four forms plus narrative asides) and the absence of any progressive disclosure: all material is inlined in one long file rather than split into referenced files.

Suggestions

Deduplicate the policy statements: the 八问 checklist, the 最低证据面 paragraphs, the Common Mistakes table, and the Pressure Tests restate the same rules; consolidate each rule into one canonical location and cross-reference it.

Move the Pressure Tests and the extended field/benchmark templates into a references/ file, keeping SKILL.md as a concise overview with clearly signaled one-level-deep pointers.

Trim the idiosyncratic narrative asides (the F218 anecdote, Magic Words framing, and the 口诀) into short rules, since they add token cost without adding executable guidance.

DimensionReasoningScore

Conciseness

The body is dense and avoids explaining basics, but the same policies are restated across the 八问 checklist, the minimum-evidence paragraphs, the Common Mistakes table, and the Pressure Tests, and idiosyncratic narrative asides (the F218 anecdote, Magic Words framing, the 口诀) add tokens without adding policy. It could be tightened meaningfully but is not heavily padded.

3 / 5

Actionability

For an instruction-only skill the guidance is largely concrete: copy-ready field templates (measured_construct, comparator, …), an explicit claim-ledger table, three named verdict scales with definitions, and worked pressure tests with expected verdicts. Some guidance stays abstract (e.g., "先换坐标系,再查细节"), keeping it below fully executable.

4 / 5

Workflow Clarity

A clear sequence is present (Trigger → lenses → ledger → 八问 → verdicts → provenance, with "先列 claim,再逐条审") and the minimum-evidence caps plus pressure tests function as explicit validation checkpoints. It falls short of 5 because error-recovery loops are only implicit in places.

4 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent), so everything — the extended checklist, the Common Mistakes table, the field templates, and four pressure-test vignettes — is inlined in a ~200-line SKILL.md. Section headers are clear, but content that clearly belongs in separate reference files is inline with no pointers, matching the 'some structure' anchor.

3 / 5

Total

14

/

20

Passed

Description

87%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 explicitly states what the skill does, when to use it, when not to use it, and what output to produce, with concrete trigger terms and clear demarcation from deep-research. The only soft spot is slightly incomplete synonym coverage in the trigger list.

DimensionReasoningScore

Specificity

The description names the domain ("外部高风险 claim 与研究贡献审计") and several concrete actions and artifacts — "claim ledger", "source / non-triviality / decision-fit 三轴 verdict", "provenance". It falls short of 5 only because the action coverage is not fully comprehensive.

4 / 5

Completeness

It explicitly answers both what ("外部高风险 claim 与研究贡献审计…Output: claim ledger + …三轴 verdict + provenance") and when ("Use when: 数字、benchmark…"), plus an explicit "Not for:" exclusion list — concrete trigger phrases on both sides.

5 / 5

Trigger Term Quality

"数字、benchmark、因果、趋势、模型能力、外部论文或会进入 docs/ADR/PPT 的结论" provides good natural keyword coverage users would actually say. A few natural synonyms (e.g., citation, source check, verify) are missing, keeping it below 5.

4 / 5

Distinctiveness Conflict Risk

The niche (auditing external high-risk claims) is distinct, and "Not for: …已进入 deep-research 的重调研" explicitly delimits it from the closest overlapping skill, minimizing wrong-skill triggering.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
zts212653/clowder-ai
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.