CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

89

1.92x
Quality

Does it follow best practices?

Impact

77%

1.92x

Average score across 3 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

A strong, actionable skill body with executable commands, a copy-paste review template, explicit error-recovery checkpoints, and clean single-level referencing. The only friction is mild repetition of the Vale/Dale-exclusion message and the posting urgency across sections, which slightly inflates the token budget.

Suggestions

State the Vale/Dale exclusion once (near the top) and reference it from the Behavioral Notes and footer rather than restating it verbatim three times.

Replace the repeated MANDATORY/urgency framing around posting the comment with a single explicit checkpoint at the end of the Output stage.

The 'Read docs/CLAUDE.md' reference is the only external dependency; consider one line on what to extract from it so the review can proceed even if that file is unavailable.

DimensionReasoningScore

Conciseness

The body is mostly efficient and actionable, but the Vale/Dale exclusion is stated twice verbatim ('Vale and Dale issues are auto-fixed separately… Do not run Vale, Dale…' in the intro and again in Behavioral Notes and the footer), and the MANDATORY framing repeats the posting instruction three times — tightenable without losing clarity.

2 / 3

Actionability

Provides fully executable bash (echo/env-var reads, `gh pr view`/`gh pr diff` fallback, `gh pr comment … --body-file`) and a copy-paste-ready review markdown template with exact structure, matching the 'fully executable, copy-paste ready' anchor.

3 / 3

Workflow Clarity

Clear sequenced stages (Input → Editorial Review → Output) with explicit validation/error checkpoints: env-var-then-positional-then-gh fallback chain, 'If the file list contains only KB files…exit', and 'If the gh pr comment command fails, report the error. Do NOT end your turn without attempting to post.'

3 / 3

Progressive Disclosure

Well-organized into clearly signaled single-purpose sections with one one-level-deep external reference (`Read docs/CLAUDE.md`) and no bundle files present to misroute; content appropriately stays inline rather than nesting references.

3 / 3

Total

11

/

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.

A tight, third-person description that states concrete capabilities, an explicit 'Use this skill whenever…' trigger, and a clearly bounded niche with deliberate deconfliction from the vale-autofix workflow. It hits every completeness and distinctiveness anchor with no fluff.

DimensionReasoningScore

Specificity

Lists several concrete actions ('Reviews changed markdown files and posts a structured comment to the PR') plus concrete boundary behavior ('Skip any file under docs/kb/', 'post a comment noting that no reviewable files were found and exit'), matching the 'multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers both what ('Orchestrate an editorial review for pull requests…Reviews changed markdown files and posts a structured comment') and when ('Use this skill whenever a PR involves markdown files in docs/ and targets the dev branch'), satisfying the explicit-trigger anchor for the top level.

3 / 3

Trigger Term Quality

Surfaces natural trigger phrasing users would actually say — 'PR involves markdown files', 'targets the dev branch', 'invoked manually via /doc-pr' — giving good coverage of the terms a user would use to reach this skill.

3 / 3

Distinctiveness Conflict Risk

It carves out a clear niche (editorial review of docs/ markdown on dev PRs) and explicitly delegates Vale/Dale to a separate workflow, sharply reducing overlap with adjacent doc/lint skills.

3 / 3

Total

12

/

12

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.