derek

KB article quality reviewer. Run against KB articles in docs/kb/ to review frontmatter, article type and structure, title format, product names, callout format, bolding/path formatting, image alt-text/external-references, and keyword quality. Use when editing or reviewing any file under docs/kb/.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

—

The risk profile of this skill

Quality

Content

81%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, highly actionable reviewer skill with a crisp workflow and exemplary externalized rule content. Its main weakness is verbosity in the scope-boundary justification paragraph and a duplicated reminder, which cost it conciseness.

Suggestions

Compress the Review Areas boundary paragraph (the 'kb-pr-open/kb-pr-review vs Derek' rationale) to one or two sentences — e.g., 'Links and image location are out of scope: they require unbounded filesystem searches; everything in the table plus Product Names is either one lookup against a known source or a pure text check.'

Remove the duplicated 'Never re-flag issues that Vale or Dale already catch' sentence from Troubleshooting, since the Overview already states it with the full rule list.

Tighten the 'Derek reports; it never edits' paragraph — the fixer-voice explanation can be one sentence ('Derek translates fixer-voice rules into table rows; never edit the article').

Dimension	Reasoning	Score
Conciseness	The body is mostly dense operational rules, but the paragraph justifying why links/image-location are out of scope ('an unbounded lookup with no fixed answer from the article's text alone... never a search across the repo') is ~120 words of reasoning that could be one sentence, and Troubleshooting repeats the 'Never re-flag issues that Vale or Dale already catch' rule already stated in the Overview.	3 / 5
Actionability	Provides a numbered procedure, an area-to-rulebook-section mapping table, a literal example output row, verbatim soft-reminder note templates, and per-violation line-number rules — fully executable guidance for an instruction-only skill with no code requirement.	5 / 5
Workflow Clarity	Six clearly ordered steps with explicit prerequisite reads, a checklist table of review areas, and a strictly specified output format; the skill is read-only ('Derek reports; it never edits the article'), so the destructive/batch validation cap does not apply.	5 / 5
Progressive Disclosure	Rule content is correctly deferred to one-level-deep, clearly signaled external files ('.claude/references/kb-editing-conventions.md', 'kb_style_guide.md', named rulebook sections) with an explicit 'do not duplicate its content' instruction, but the output templates and line-number guidance are inlined rather than split, and the referenced paths are repo-relative rather than skill bundle files.	4 / 5
	Total	17 / 20 Passed

Description

92%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 names a precise domain, lists comprehensive concrete capabilities, gives an explicit path-scoped 'Use when' trigger, and occupies a distinct niche. The only gap is a few natural synonyms users might use instead of 'KB articles'.

Dimension	Reasoning	Score
Specificity	Enumerates eight concrete review actions ('frontmatter, article type and structure, title format, product names, callout format, bolding/path formatting, image alt-text/external-references, and keyword quality') — comprehensive coverage, not the 'minor gaps' of anchor 4.	5 / 5
Completeness	Explicitly answers both what (the enumerated review areas) and when ('Use when editing or reviewing any file under docs/kb/') with a concrete trigger phrase, matching anchor 5.	5 / 5
Trigger Term Quality	Good natural terms ('KB articles', 'editing or reviewing any file under docs/kb/'), but missing common variations a user might say such as 'knowledge base', 'support article', or 'Netwrix' — the 'few natural terms missing' of anchor 4 rather than the synonym-complete anchor 5.	4 / 5
Distinctiveness Conflict Risk	Clear niche scoped to a specific artifact type and path (KB articles under docs/kb/), so it is unlikely to trigger for the wrong skill.	5 / 5
	Total	19 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: netwrix/docs
Path: .claude/skills/derek/SKILL.md
Commit: 9dbd89e

Reviewed: 7 days ago

Table of Contents

Discovery Implementation Validation

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.