CtrlK
BlogDocsLog inGet started
Tessl Logo

doc-freshness-review

Use when auditing repository documentation for drift, stale statements, broken references, or README mismatches, especially across published docs under `doc/` and key entry surfaces such as `README.md` (English default), `README.zh-CN.md`, `mcp/README.md`, and `mcp/README.zh-CN.md` during periodic maintenance or before preparing corrective PRs.

68

Quality

83%

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

78%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 well-structured, actionable instruction-only skill body with clean progressive disclosure and a useful self-check. The lowest-scoring dimensions (conciseness, actionability, workflow_clarity) each have small, addressable gaps rather than fundamental weaknesses.

Suggestions

Add one short example finding (e.g., a stale command line with file path and the minimal rewrite direction) to make the expected output concrete and lift actionability.

Deduplicate the surface list between the 'When to use this skill' bullets and the description, and trim the Routing table rows that restate Phase-1 references, to tighten conciseness.

Insert an explicit mid-workflow verification checkpoint (e.g., 'confirm each referenced path exists before classifying the mismatch') so validation is not only captured in the final self-check.

DimensionReasoningScore

Conciseness

Lean and free of concept-padding, assuming Claude's competence throughout, with minor redundancy: the 'When to use this skill' section reprises the description and the Routing table repeats Phase-1 references.

4 / 5

Actionability

Concrete, actionable guidance ('Read references/review-scope.md first', specific mismatch categories, exact file paths, explicit skill routing) with a minor gap: no example finding showing the expected output shape.

4 / 5

Workflow Clarity

Clear four-phase sequence with decision checkpoints in Phase 3 and a Minimum self-check checklist, but validation is concentrated at the end rather than interspersed as explicit verify-after-step checkpoints.

4 / 5

Progressive Disclosure

Clear overview pointing to a real one-level-deep reference (references/review-scope.md) that is well-signaled via the Routing table and 'Read X first' instruction, with content appropriately split and easy navigation.

5 / 5

Total

17

/

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, specific description that clearly states both capability and trigger conditions with concrete surfaces and timing. Minor room for improvement in action-verb variety and synonym coverage.

DimensionReasoningScore

Specificity

Lists several specific finding-types ('drift, stale statements, broken references, or README mismatches') and named surfaces, but centers on a single verb ('auditing') rather than multiple distinct concrete actions, leaving minor coverage gaps.

4 / 5

Completeness

Explicitly answers both what ('auditing repository documentation for drift, stale statements, broken references, or README mismatches') and when ('Use when...', 'during periodic maintenance or before preparing corrective PRs') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good natural-term coverage ('drift', 'stale statements', 'broken references', 'README mismatches', 'corrective PRs', named README paths) users would actually say, but misses common synonyms like 'outdated' or 'out of date'.

4 / 5

Distinctiveness Conflict Risk

Clear niche (documentation freshness/drift auditing) with named surfaces and routing to sibling skills (api-contract-review, pr-review-fix), giving minimal conflict risk.

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
TencentCloudBase/CloudBase-AI-Toolkit
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.