CtrlK
BlogDocsLog inGet started
Tessl Logo

technical-writer

AI DevKit · Review and improve documentation for novice users. Use when users ask to review docs, improve documentation, audit README files, evaluate API docs, review guides, or improve technical writing.

70

Quality

86%

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

86%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 concise, well-organized review framework that gives Claude a clear rating scheme, prioritization guidance, and a copy-paste output template. Its main gap is the absence of a worked example illustrating a completed review.

Suggestions

Add a brief filled-in example review (one small doc rated across the four dimensions with sample issues and concrete fix text) to make the output template fully copy-paste ready.

Make the validation/approval checkpoint explicit in the workflow sequence rather than burying it only in Hard Rules, so the step ordering is unambiguous.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: dimensions, a priority scale, a red-flags table, and a copy-paste output template with no padding or explanations of concepts Claude already knows.

5 / 5

Actionability

It supplies a concrete output template, hard rules ("Suggest concrete fix text, not vague advice"), and dimension definitions, but lacks a worked example showing a filled-in review, leaving a minor gap.

4 / 5

Workflow Clarity

The review sequence (rate four dimensions, flag issues by priority, emit via template) is clear with an approval checkpoint ("Do not rewrite... until the user approves"), though verification checkpoints are implicit rather than explicit.

4 / 5

Progressive Disclosure

As a single-purpose skill under 50 lines with no bundle files and well-organized sections (Hard Rules, Review Dimensions, Priority, Output Template), it satisfies the simple-skill exception for full progressive-disclosure marks.

5 / 5

Total

18

/

20

Passed

Description

86%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, well-structured description with explicit what/when guidance and comprehensive natural trigger terms. Its only weakness is modest capability specificity, relying on just two verbs rather than enumerating the full range of review actions.

Suggestions

Expand specificity beyond the two verbs 'review' and 'improve' (e.g., add 'rewrite unclear sections, add missing examples, fix broken links') to reach comprehensive capability coverage.

DimensionReasoningScore

Specificity

"Review and improve documentation for novice users" names the domain and two concrete actions (review, improve) but offers no broader enumeration of capabilities, matching the anchor for 1-2 concrete actions rather than the several required for a 4.

3 / 5

Completeness

It explicitly answers both what ("Review and improve documentation for novice users") and when ("Use when users ask to review docs, improve documentation, audit README files...") with concrete trigger phrases.

5 / 5

Trigger Term Quality

"review docs, improve documentation, audit README files, evaluate API docs, review guides, or improve technical writing" provides comprehensive natural phrasings with synonyms (docs/documentation, README, API docs, guides) that users would actually say.

5 / 5

Distinctiveness Conflict Risk

The novice-audience documentation-review niche with specific triggers (audit README files, evaluate API docs) is mostly distinct with only minor overlap risk against general writing skills, fitting just above the 3 anchor but not fully the minimal-conflict 5.

4 / 5

Total

17

/

20

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
codeaholicguy/ai-devkit
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.