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, and keyword quality. Use when editing or reviewing any file under docs/kb/.

72

Quality

88%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Risky

Do not use without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a strong, well-structured skill that provides highly actionable review criteria with clear workflow sequencing and a strictly defined output format. Its main weakness is moderate verbosity — the inline enumeration of Vale/Dale exclusions and detailed review tables make it longer than strictly necessary, though most content earns its place. The skill would benefit from splitting some reference material (e.g., product name lists, frontmatter validation rules) into separate bundle files.

Suggestions

Consider moving the Vale/Dale exclusion lists to a separate reference file (e.g., `vale_dale_coverage.md`) and referencing it with a single line, since Claude only needs to know not to re-flag these items.

If `kb_style_guide.md` already contains the product name rules and article type definitions, consider removing the duplicated content from the skill body and simply referencing the relevant sections of the style guide.

DimensionReasoningScore

Conciseness

The skill is mostly efficient and well-structured, but includes some content that could be tightened. The explicit lists of what Vale and Dale handle are useful for avoiding duplication but are somewhat lengthy. The detailed table formats and rule explanations are necessary for the task but could be slightly more compact.

2 / 3

Actionability

The skill provides highly concrete, actionable guidance: specific frontmatter fields to check with exact validation rules, precise article type identification logic based on title patterns, exact heading requirements per article type, a strict output format with example table rows, and clear product name usage rules. Every review area has specific, checkable criteria.

3 / 3

Workflow Clarity

The workflow is clearly sequenced (read style guide → read article → identify type → review each area → output). Each review area has explicit criteria and the output format includes validation constraints (e.g., consolidation rules for structure violations, line number guidance). The troubleshooting section adds a clear boundary constraint. For a review/audit task, this is well-structured with clear checkpoints.

3 / 3

Progressive Disclosure

The skill references `kb_style_guide.md` as an external resource (good), but all review rules are inline in a single file that runs ~120+ lines. The detailed tables for frontmatter validation, article structure, and output format could potentially be split into referenced files. However, no bundle files are provided, so there's no evidence of a multi-file structure. The content is well-organized with clear H2 sections, which partially compensates.

2 / 3

Total

10

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a strong skill description that clearly communicates its purpose, lists specific review actions, and provides explicit trigger guidance with a clear file path scope. It uses proper third-person voice and is concise without being vague. The description effectively distinguishes itself from general document review or editing skills.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: reviewing frontmatter, article type and structure, title format, product names, and keyword quality. These are clearly defined review dimensions.

3 / 3

Completeness

Clearly answers both what ('review frontmatter, article type and structure, title format, product names, and keyword quality') and when ('Use when editing or reviewing any file under docs/kb/').

3 / 3

Trigger Term Quality

Includes natural keywords users would say: 'KB article', 'review', 'frontmatter', 'docs/kb/', 'editing', 'reviewing', 'keyword quality', 'title format'. Good coverage of terms a user working with KB articles would naturally use.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive with a clear niche: KB article quality review specifically in docs/kb/. The combination of KB articles, specific review criteria, and the file path makes it very unlikely to conflict with other skills.

3 / 3

Total

12

/

12

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

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.