CtrlK
BlogDocsLog inGet started
Tessl Logo

source-audit

外部证据信源卫生中档闸门。 Use when: 准备引用外部 claim,且命中数字/百分比、benchmark、因果归因、趋势判断、模型能力对比、论文/医学/金融、或会落 docs/ADR/PPT 的高风险特征。 Not for: 简单事实查询、只读官方一手文档且不做外推、已经进入 deep-research 的重调研。 Output: claim ledger + verdict(use / use-with-caveat / reject / escalate-to-deep-research)+ provenance 行。

80

Quality

100%

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

100%Weight 40%Scale 1-3

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 tight, well-structured instruction skill: it gives a concrete ledger/checklist workflow, a verdict ladder, provenance format, and self-checking via a pressure test and common-mistakes table, with no redundant concept explanations. It exemplifies token-efficient, actionable guidance.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence—it does not explain what a paper, blog, or benchmark is, and every section (ledger, five-question checklist, verdict ladder, provenance format) earns its place, matching the 'lean and efficient' anchor.

3 / 3

Actionability

Provides concrete, executable instruction: a five-question checklist, a four-rung verdict ladder with explicit definitions, a one-line provenance template, and a ledger table schema. It is instruction-only but the guidance is specific and copy-ready, which the rubric rewards.

3 / 3

Workflow Clarity

The process is clearly sequenced (list claims → five-question audit → assign verdict → emit provenance) and includes a Pressure Test validation checkpoint plus a Common Mistakes feedback loop, matching the 'clear sequence with explicit validation steps' anchor.

3 / 3

Progressive Disclosure

This is a simple single-file skill with well-organized sections and no nested or multi-level references; per the rubric's simple_skills note, that structure can score 3 without external file references.

3 / 3

Total

12

/

12

Passed

Description

100%Weight 40%Scale 1-3

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 concise yet complete, clearly stating capabilities, natural trigger conditions, exclusions, and output format in third person. It avoids fluff and over-claims while covering all four dimensions strongly.

DimensionReasoningScore

Specificity

Names multiple concrete outputs ('claim ledger + verdict ... + provenance 行') and several specific trigger categories rather than vague actions, matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers both what (信源卫生 gate producing a ledger/verdict/provenance) and when (a 'Use when' clause plus a 'Not for' carve-out), satisfying the explicit-trigger requirement.

3 / 3

Trigger Term Quality

Includes natural terms users would say ('数字/百分比', 'benchmark', '论文/医学/金融', 'docs/ADR/PPT') with good coverage, matching the 'good coverage of natural terms' anchor; not merely technical jargon.

3 / 3

Distinctiveness Conflict Risk

The 'Not for' clause explicitly distinguishes it from simple lookups, official-doc reads, and deep-research, giving it a clear niche unlikely to trigger for the wrong skill.

3 / 3

Total

12

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

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.