doc-sync-all

Comprehensive documentation synchronization - scan local git changes and propagate updates to ALL design docs, task lists, specs, diagrams, and planning artifacts. Use when finishing a feature, after merging, or when design docs are out of date.

1.03x

Quality

82%

Does it follow best practices?

Impact

93%

1.03x

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 highly actionable, well-sequenced workflow with strong validation and verification, scoring top marks on actionability and workflow clarity. Its main weakness is redundancy across trigger/invocation sections that inflates token cost without adding guidance.

Suggestions

Collapse 'Sample Invocation Phrases' and the 'When to Use' list into a single trigger section to remove duplicated phrasing and trim tokens.

Move the 'File Detection Patterns' glob blocks into a references/ file (or fold them into Phase 2's inventory) so the body keeps only the workflow logic.

Trim the example 'Documentation Update Manifest' and 'Output Report' templates to minimal skeletons, since the surrounding rules already specify their contents.

Dimension	Reasoning	Score
Conciseness	The ~360-line body is mostly efficient and free of concept-over-explanation, but 'When to Use', 'Sample Invocation Phrases', and 'File Detection Patterns' substantially duplicate triggers and globs already present elsewhere, so it could be tightened.	3 / 5
Actionability	Copy-paste-ready git commands ('git status --porcelain', 'git diff HEAD', 'git diff --name-status main...HEAD'), concrete change-type→doc mapping tables, an explicit validation pattern (T094), and a templated update manifest cover the common cases fully.	5 / 5
Workflow Clarity	Five clearly sequenced phases with an explicit 'Verify' step (re-read, cross-reference check, no duplicate sections, validate markdown), a completion checklist, and a cross-reference validation report provide feedback loops for this batch operation.	5 / 5
Progressive Disclosure	Well-organized into labeled phases and tables with no nested references, but it is a long monolith with no bundle files and a few sections (glob patterns, sample phrases) that read as inlined reference material.	4 / 5
	Total	17 / 20 Passed

Description

83%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 description that clearly states both capability and trigger conditions with concrete, natural phrasing. It is slightly held back by limited action variety and modest overlap risk with sibling doc-maintenance skills.

Dimension	Reasoning	Score
Specificity	Quotes 'scan local git changes and propagate updates to ALL design docs, task lists, specs, diagrams, and planning artifacts' name the domain and concrete action with comprehensive target coverage, but the core verbs are limited to scan + propagate rather than several distinct actions, so it sits just below the comprehensive multi-action anchor.	4 / 5
Completeness	It explicitly answers both what ('scan local git changes and propagate updates...') and when ('Use when finishing a feature, after merging, or when design docs are out of date') with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	'Use when finishing a feature, after merging, or when design docs are out of date' provides several natural trigger phrases a user might say, though common variations like 'sync docs' or 'update docs' are not included.	4 / 5
Distinctiveness Conflict Risk	The git-change-driven doc propagation niche is clearly carved and mostly distinct, but the broad 'ALL design docs, task lists, specs, diagrams, planning artifacts' scope creates minor overlap risk with closely related repo/doc-sync skills.	4 / 5
	Total	17 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: 0xrabbidfly/eric-cartman
Path: .github/skills/doc-sync-all/SKILL.md
Commit: 0b8453f

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