CtrlK
BlogDocsLog inGet started
Tessl Logo

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

64

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/derek/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 reviewer skill with a clear workflow and strong output specification. Its main weakness is conciseness — the scope-justification paragraph and repeated reminders add length without proportional value — and some inlined operational detail that could live in a reference file.

Suggestions

Tighten the long paragraph in Review Areas explaining why links/image-location are out of scope: reduce it to one or two sentences stating the rule (no filesystem search beyond the article) without the extended rationale.

Move the detailed output templates, soft-reminder wording, and line-number guidance into a references/ file (e.g. output-format.md) and summarize them in SKILL.md, improving both conciseness and progressive disclosure.

Consolidate the 'do not re-flag what Vale/Dale catch' guidance so it appears once instead of being restated in the Overview and Troubleshooting sections.

DimensionReasoningScore

Conciseness

The body is mostly efficient operational detail, but the long paragraph justifying why links/image-location are out of scope ('an unbounded lookup with no fixed answer from the article's text alone...') is padded philosophical explanation that could be tightened, and the 'do not re-flag' reminders repeat across sections.

3 / 5

Actionability

It gives concrete, executable guidance — named rulebook sections per area, exact output table columns, copy-paste assessment-line templates, and precise line-number rules — with only minor gaps because the actual check logic is delegated to the external rulebook and some areas rely on judgment ('plausible customer search term').

4 / 5

Workflow Clarity

The 'How to Review' section gives a clear 6-step sequence and the Review Areas table acts as a checklist with strict output-format enforcement, but there is no error-recovery feedback loop, capping it just below 5.

4 / 5

Progressive Disclosure

Content is well-organized into clear sections and points to one-level-deep external references (the rulebook and style guide) that are clearly signaled, but a large amount of operational detail (output templates, soft-reminder wording, line-number guidance) is inlined in SKILL.md rather than split into a reference file.

4 / 5

Total

15

/

20

Passed

Description

88%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 the capability (reviewing KB articles across many concrete dimensions) and the trigger (editing/reviewing files under docs/kb/). It is mostly distinct and well-targeted, with only minor room to add user-natural synonyms beyond the path-based trigger.

DimensionReasoningScore

Specificity

The description lists many 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' — giving comprehensive coverage of what the skill reviews.

5 / 5

Completeness

It explicitly answers both what ('KB article quality reviewer... review frontmatter... keyword quality') and when ('Use when editing or reviewing any file under docs/kb/') with concrete trigger phrases.

5 / 5

Trigger Term Quality

It includes a clear 'Use when editing or reviewing any file under docs/kb/' trigger with natural terms like 'KB articles' and 'editing or reviewing', but coverage leans on the docs/kb/ path rather than synonyms a user might naturally say, leaving a few natural terms missing.

4 / 5

Distinctiveness Conflict Risk

The docs/kb/ scope and KB-article-review niche make it mostly distinct, though the body reveals closely related sister skills (kb-pr-open, kb-pr-review) that create minor overlap risk for KB-editing tasks.

4 / 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
netwrix/docs
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.