CtrlK
BlogDocsLog inGet started
Tessl Logo

doc-maintenance

Keep project docs aligned with recent code and feature changes — detect drift, update affected pages, and add release-relevant notes without rewriting unchanged sections.

67

Quality

81%

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

92%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 content is concise, well-structured, and actionably instructs an intelligent agent through a clear multi-step pass with built-in validation and drift checks. Its only mild gap is the absence of executable code examples, which is acceptable for an instruction-only skill.

DimensionReasoningScore

Conciseness

The body is lean and efficient, assumes Claude's competence (no explanation of what docs or PRs are), and every section earns its place without padding.

5 / 5

Actionability

Provides concrete, specific guidance ('New CLI flag -> CLI reference entry', 'Re-run any example that touches new behavior') and explicit rules, though it is instructional prose without executable code or commands.

4 / 5

Workflow Clarity

The 8-step 'pass' is clearly sequenced with an explicit cross-check/feedback loop ('Search the docs for the old behavior wording and remove or update stragglers') and a drift-detection checklist.

5 / 5

Progressive Disclosure

The single ~60-line file is well-organized into clearly signaled sections (When to use, The pass, Style baseline, Drift detection, Release-note rules, Anti-patterns) with no need for external references.

5 / 5

Total

19

/

20

Passed

Description

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

The description is specific and distinctive, clearly stating what the skill does with several concrete actions. Its main weakness is the missing explicit 'Use when...' trigger clause, which limits completeness.

Suggestions

Add an explicit 'Use when...' clause listing concrete trigger phrases (e.g., 'Use when a release is being cut, a user reports outdated docs, or behavior-changing PRs have merged').

Include a few more natural synonyms users might say, such as 'changelog', 'README', or 'docs drift', to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain ('project docs aligned with recent code and feature changes') and multiple concrete actions ('detect drift, update affected pages, and add release-relevant notes'), giving comprehensive coverage.

5 / 5

Completeness

The 'what' is clearly stated, but there is no explicit 'Use when...' trigger clause, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Includes natural terms ('docs', 'release-relevant notes', 'drift', 'code and feature changes') but is missing some common synonyms users would say, like 'changelog' or 'README'.

4 / 5

Distinctiveness Conflict Risk

The doc-maintenance/drift-detection niche is mostly distinct with clear triggers, with only minor overlap risk against general doc-writing skills.

4 / 5

Total

16

/

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
paperclipai/paperclip
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.