Name: doc-help
Rating: 86.6 (1 reviews)
Author: netwrix

doc-help

Interactive writing assistant for Netwrix documentation. Use when a writer wants hands-on, conversational help: brainstorming structure, drafting a section, editing existing content, incorporating external documents (e.g., .docx files) into existing markdown files, or understanding a style or Vale rule. For fully autonomous tasks (write this entire doc, fix all Vale errors end-to-end), use the tech-writer agent instead.

1.18x

Quality

90%

Does it follow best practices?

Impact

69%

1.18x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

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 clear, well-sequenced interactive workflow with concrete commands, examples, and explicit validation feedback loops. Main weaknesses are the duplicated Vale/Dale block and procedurally-phrased (rather than executable) guidance inherent to an interactive skill.

Suggestions

Factor the repeated Vale/Dale check into a single shared subsection referenced from Stage 2 and Stage 3 to remove the verbatim duplication and tighten conciseness.

Add a short, copy-paste-ready example of an edit round (input sentence -> edited sentence) in the Editing workflow to push actionability from procedural to executable.

Consider moving the Netwrix doc structure patterns and the 'Always:' writing principles into a reference file under references/ so SKILL.md stays a lean overview, improving progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and free of concepts Claude already knows, but the Vale/Dale block is repeated verbatim across Stage 2 and Stage 3, and a few persona lines ('patient, knowledgeable writing partner') could be trimmed. Not a 5 because of that duplicated lint block.	4 / 5
Actionability	Provides concrete commands (`vale <file>`, `/dale <file>`, Read `docs/CLAUDE.md`), explicit intake questions, and a concrete before/after plus findings-format example. Not a 5 because much of the guidance is procedural 'ask the writer X' prompts rather than copy-paste-ready artifacts.	4 / 5
Workflow Clarity	Stages and numbered steps give a clear sequence, and the Vale/Dale check ('Fix all reported errors. Re-run until zero errors remain') is an explicit validate-fix-retry feedback loop, matching the explicit-validation anchor.	5 / 5
Progressive Disclosure	Well organized into stages with a clear single external reference (`docs/CLAUDE.md`) for style rules instead of duplicating them. Not a 5 because no bundle files exist and the repeated inline Vale/Dale blocks could be factored out, leaving minor organization gaps.	4 / 5
	Total	17 / 20 Passed

Description

100%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-scoped description that clearly states capabilities, provides concrete trigger phrasing with a file extension, and explicitly carves out when not to use it. No first/second-person voice or vague fluff is present.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'brainstorming structure, drafting a section, editing existing content, incorporating external documents (e.g., .docx files) into existing markdown files, or understanding a style or Vale rule' — giving comprehensive coverage of what the skill does.	5 / 5
Completeness	Explicitly answers both 'what' (interactive writing assistant for Netwrix documentation with the listed actions) and 'when' ('Use when a writer wants hands-on, conversational help: ...'), and even adds negative guidance pointing to the tech-writer agent for autonomous tasks.	5 / 5
Trigger Term Quality	Covers natural user phrasings ('help me write', drafting, editing) plus synonyms and the concrete file extension '.docx', matching the comprehensive-coverage anchor including synonyms and extensions.	5 / 5
Distinctiveness Conflict Risk	Scoped to Netwrix documentation with a clear conversational/interactive niche, and explicitly distinguishes itself from the tech-writer agent for autonomous work, minimizing overlap risk.	5 / 5
	Total	20 / 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/doc-help/SKILL.md
Commit: a2eb049

Reviewed: 3 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.