CtrlK
BlogDocsLog inGet started
Tessl Logo

content-fix

Autonomous fixer for documentation content issues. Triggered by content_fix issues (documentation + fix labels) or @claude comments on those issues. Reads the issue, identifies affected files, applies fixes following Netwrix writing standards, and pushes a branch. A separate workflow step creates the PR. Asks clarifying questions if the request is ambiguous.

93

1.60x
Quality

Does it follow best practices?

Impact

96%

1.60x

Average score across 3 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

A lean, highly actionable, well-sequenced workflow with executable commands, explicit validation/stop checkpoints, and a clean single-file structure. It defers writing standards to an external file rather than restating them and provides an exact output contract.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — 'Read `docs/CLAUDE.md` before starting — it has the writing standards' defers rather than restates standards, and there is no padding or explanation of concepts Claude already knows. Not below 3 because every section earns its place.

3 / 3

Actionability

It provides fully executable commands (gh issue view, gh api, git checkout -b, git commit, git push -u), a concrete file-path mapping rule ('10_8 → 10.8'), and an exact copy-paste-ready output format (BRANCH_NAME=...). The only placeholders are justified slugs.

3 / 3

Workflow Clarity

A clear numbered sequence (1–6) with explicit validation checkpoints and stop conditions — step 2C (can't find → STOP), step 3 (too vague → STOP, needs images → STOP), the 'Do NOT stop until...' guard, and the meaning-change skip rule — providing feedback loops for the fragile edit/push operation.

3 / 3

Progressive Disclosure

The skill is a single self-contained SKILL.md with well-organized sections (Input, Workflow, Rules) and no nested multi-level references — the only external pointer is docs/CLAUDE.md, an out-of-skill repo file. Per the rubric's simple-skills note, well-organized single-file content with no bundle references scores 3.

3 / 3

Total

12

/

12

Passed

Description

85%

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 specific, complete, and distinctive description with an explicit trigger condition. Its only weakness is that the trigger terms are internal workflow/label jargon rather than phrases a user would naturally say, which limits trigger-term quality.

Suggestions

Add natural-language trigger terms a user might actually say (e.g., 'Use when fixing documentation issues, typos, or outdated wording in Netwrix docs') alongside the label-based triggers.

Rephrase so the trigger reads as user-facing guidance rather than only GitHub-internal mechanics ('documentation + fix labels').

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'Reads the issue, identifies affected files, applies fixes following Netwrix writing standards, and pushes a branch' — matching the anchor for listing several specific concrete actions.

3 / 3

Completeness

It clearly answers both what (autonomous fixer that reads issues, finds files, applies fixes, pushes a branch) and when with explicit triggers ('Triggered by content_fix issues ... or @claude comments'), matching the anchor that requires explicit triggers for both what and when.

3 / 3

Trigger Term Quality

Trigger language is 'Triggered by content_fix issues (documentation + fix labels) or @claude comments on those issues' — these are internal GitHub label/workflow terms rather than natural keywords a user would actually say, and common user-facing variations are missing. Not a 1 because 'documentation content issues' is a relevant term; not a 3 because the triggers lean on technical label jargon instead of natural user phrasing.

2 / 3

Distinctiveness Conflict Risk

It carves a clear niche — documentation content fixes gated on specific issue labels and @claude mentions — making it unlikely to fire for unrelated skills.

3 / 3

Total

11

/

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.