Name: content-fix
Rating: 85.6 (1 reviews)
Author: netwrix

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.

1.60x

Quality

80%

Does it follow best practices?

Impact

96%

1.60x

Average score across 3 eval scenarios

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/content-fix/SKILL.md

Quality

Content

88%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 content is highly actionable with executable commands, a clearly sequenced workflow, and explicit validation/stop checkpoints that appropriately guard the file-editing operation. It is concise and well-structured, with only minor room to tighten the output example.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence, with every line contributing actionable guidance; only the worked output example adds minor length that could be trimmed.	4 / 5
Actionability	Provides fully executable, copy-paste-ready commands (gh issue view, git checkout -b, git push -u origin), concrete URL-to-path mapping rules, and an exact BRANCH_NAME output contract covering the common cases.	5 / 5
Workflow Clarity	A clear six-step sequence with explicit validation checkpoints (clarity check, STOP conditions, 'do NOT stop until...') and feedback loops for ambiguous or image-dependent requests, including a skip-on-meaning-change guard for the file-edit step.	5 / 5
Progressive Disclosure	No bundle files exist, so the skill is a single self-contained SKILL.md that is well-sectioned and easy to navigate; it is slightly longer than the simple-skill sweet spot, keeping it just below a perfect score.	4 / 5
	Total	18 / 20 Passed

Description

71%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 is specific and distinctive, clearly conveying both its autonomous-fix role and its GitHub-issue-based triggers. Its main weakness is that the triggers are structural labels and @mentions rather than natural language a user would actually say, which weakens trigger-term quality.

Suggestions

Add a natural-language 'Use when...' clause with phrases a user would say (e.g., 'Use when fixing documentation issues reported via GitHub issues').

Include natural keyword variants like 'documentation fixes', 'doc issues', or 'content corrections' so the skill surfaces on conversational requests.

Dimension	Reasoning	Score
Specificity	Names several concrete actions ('identifies affected files, applies fixes following Netwrix writing standards, and pushes a branch') rather than vague language, with only minor coverage gaps.	4 / 5
Completeness	Clearly states what the skill does (read issue, find file, apply fix, push branch) and when it triggers (content_fix issues / @claude comments), though the trigger is structural rather than a natural 'Use when...' phrase.	4 / 5
Trigger Term Quality	Triggers are structural ('content_fix issues (documentation + fix labels) or @claude comments') rather than natural-language phrases a user would say, so common keyword variations are missing.	3 / 5
Distinctiveness Conflict Risk	A clearly bounded niche tied to Netwrix documentation issues and GitHub Actions, with distinct triggers that make conflict with other skills minimal.	5 / 5
	Total	16 / 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/content-fix/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.