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

73%

Does it follow best practices?

Impact

93%

1.03x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.github/skills/doc-sync-all/SKILL.md

Quality

Content

63%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 skill delivers a genuinely actionable, well-sequenced documentation sync workflow with concrete commands, templates, and validation checkpoints. Its main weaknesses are verbosity from heavily duplicated sections and the absence of any progressive disclosure — everything lives in one long SKILL.md instead of split reference files.

Suggestions

Consolidate the three repeated file-pattern listings (Phase 2.1, Phase 2.2, and "File Detection Patterns") into a single reference table, and drop the redundant "Sample Invocation Phrases" section that duplicates the description and "When to Use" triggers.

Split detail content into one-level-deep reference files (e.g., references/doc-inventory.md for the file-layout catalogs and references/sync-rules.md for the per-document rules), keeping SKILL.md as a concise overview with clearly signaled links.

Replace the nonexistent tool names ("replace_string_in_file", "multi_replace_string_in_file", "file_search") with the actual available file tools, and add an explicit validate-fix-retry loop to the Verify step for failed cross-reference checks.

Dimension	Reasoning	Score
Conciseness	The body is mostly dense operational guidance with little concept-explanation padding, but duplication is extensive: file globs appear three times (Phase 2.1, Phase 2.2, "File Detection Patterns"), trigger phrases twice ("When to Use This Skill" and "Sample Invocation Phrases"), and the full sample report is illustrative bulk. Anchor 3 ('mostly efficient... could be tightened') fits better than 4 given the scale of repetition.	3 / 5
Actionability	Concrete git commands, per-document sync rules, decision-entry and change-manifest templates are directly usable, matching anchor 4. Not 5: Step 4 names tools that don't exist in this environment ("replace_string_in_file", "multi_replace_string_in_file", "file_search"), so the guidance isn't fully executable as written.	4 / 5
Workflow Clarity	A clear five-phase sequence with an explicit Verify step ("re-read modified files", "check for broken cross-references", "no duplicate sections") and a completion checklist covers validation for this batch operation, satisfying anchor 4. Not 5: there is no explicit validate-fix-retry feedback loop, so checkpoints lack error-recovery guidance.	4 / 5
Progressive Disclosure	There are no external reference files at all — the 370-line monolith inlines detailed file inventories, glob catalogs, and a full sample report that clearly belong in separate files, fitting anchor 3 ('some structure... content that should be separate is inline'). Section structure itself is good, so not 2.	3 / 5
	Total	14 / 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 and explicitly states both capability and usage triggers with natural phrasing. Minor room for improvement in adding common trigger synonyms and more concrete action verbs.

Dimension	Reasoning	Score
Specificity	"scan local git changes and propagate updates to ALL design docs, task lists, specs, diagrams, and planning artifacts" names the domain and enumerates concrete targets, but the verbs ("scan", "propagate updates") are more generic than anchor 5's fully concrete action list. It clearly exceeds anchor 3's '1-2 concrete actions' coverage.	4 / 5
Completeness	Explicitly answers both what ("scan local git changes and propagate updates to ALL design docs...") and when ("Use when finishing a feature, after merging, or when design docs are out of date") with concrete trigger phrases, matching anchor 5 exactly. Not 4, since the 'when' clause is already explicit and specific.	5 / 5
Trigger Term Quality	"finishing a feature", "after merging", "design docs", "specs", "task lists" are natural user phrasings matching anchor 4's 'good keyword coverage; a few natural terms missing' — common variants like "sync docs" or "update docs" are absent. Not anchor 5, which requires comprehensive synonyms.	4 / 5
Distinctiveness Conflict Risk	Git-change-driven propagation to design artifacts is a clear niche with distinct triggers, but "documentation" is a broad domain where doc-update skills overlap, fitting anchor 4's 'mostly distinct; minor overlap risk'. Not 5, since related doc-editing/sync skills would compete for the same phrasing.	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: aa16c9e

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