doc-pr

Orchestrate an editorial review for pull requests targeting dev. Reviews changed markdown files and posts a structured comment to the PR. Vale and Dale issues are auto-fixed separately by the vale-autofix workflow. Use this skill whenever a PR involves markdown files in docs/ and targets the dev branch — triggered automatically by the doc-pr GitHub Actions workflow on PR open, sync, or when invoked manually via /doc-pr.

1.92x

Quality

82%

Does it follow best practices?

Impact

77%

1.92x

Average score across 3 eval scenarios

Securityby

Low

Low-risk findings worth noting

Quality

Content

82%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.

The body is actionable and well-structured with concrete commands, a complete output template, and clear edge-case handling. It is efficient and well-organized, with only minor room to tighten emphasis and add a feedback loop.

Dimension	Reasoning	Score
Conciseness	Largely efficient with concrete commands and templates and minimal over-explanation of known concepts; minor emphasis padding ('the review is useless if it is not posted') keeps it just below a 5.	4 / 5
Actionability	Fully executable guidance: concrete env-var reads, a complete copy-paste-ready review output template, and an exact `gh pr comment` command, matching the score-5 anchor.	5 / 5
Workflow Clarity	Clear sequenced flow (Input -> Editorial Review -> Output) with explicit edge-case handling (empty env vars, KB-only files, comment failure), but lacks a validate-and-retry feedback loop, fitting the score-4 anchor.	4 / 5
Progressive Disclosure	Well-organized into clear sections with a single clearly-signaled one-level-deep reference (docs/CLAUDE.md); no bundle files exist, and at ~60 lines with minor organization gaps it sits at the score-4 anchor rather than 5.	4 / 5
	Total	17 / 20 Passed

Description

82%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.

The description clearly states what the skill does and when to use it, with concrete, natural trigger language and a well-scoped niche. It is slightly less comprehensive on enumerating specific actions but otherwise strong.

Dimension	Reasoning	Score
Specificity	Names the domain and a couple concrete actions ('Reviews changed markdown files and posts a structured comment to the PR') but does not enumerate a comprehensive set of capabilities, matching the score-3 anchor.	3 / 5
Completeness	Explicitly answers both what ('Orchestrate an editorial review... posts a structured comment') and when ('Use this skill whenever a PR involves markdown files in docs/ and targets the dev branch') with concrete trigger phrases, matching the score-5 anchor.	5 / 5
Trigger Term Quality	Good natural-keyword coverage ('PR', 'pull requests', 'markdown files in docs/', 'dev branch', 'editorial review', 'doc-pr') with synonyms; a few common variations are absent, fitting the score-4 anchor rather than the comprehensive 5.	4 / 5
Distinctiveness Conflict Risk	Clear niche scoped to PRs targeting the dev branch with markdown in docs/ and a named GitHub Actions workflow, giving distinct triggers with minimal conflict risk, matching the score-5 anchor.	5 / 5
	Total	17 / 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-pr/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.