source-command-sync

Check guide/landing synchronization status

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/source-command-sync/SKILL.md

Quality

Content

75%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 body is highly actionable with concrete commands and copy-paste remediation, and it is organized into clear, navigable sections. Its main weakness is verbosity from duplicated full output templates and slight overlap between the "What to Check" and "Implementation" sections.

Suggestions

Collapse the two full output templates into one, using inline placeholders (e.g. "Status: ✅/⚠️ per component") instead of repeating the entire block for the mismatch case.

Merge "What to Check" and "Implementation" to remove the restatement of the same execute-and-format steps.

Add an explicit validation checkpoint (e.g. "If the script exits non-zero or reports ⚠️/❌, switch to the mismatch format") to make the branch condition unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with clear sections, but the two full ASCII output templates (success and mismatch) repeat the entire header and structure, and the "Implementation" section restates "What to Check", so it could be tightened.	3 / 5
Actionability	It gives a concrete command ("./scripts/check-landing-sync.sh") and copy-paste-ready remediation including exact file paths, line numbers, and git commit/push commands, fully covering the common success and mismatch cases.	5 / 5
Workflow Clarity	The numbered "Implementation" steps give a clear sequence (execute, capture, parse, format, branch on issues, add next steps), but validation checkpoints are implicit rather than explicit; this is a read-only check so the destructive/batch cap does not apply.	4 / 5
Progressive Disclosure	The single file is well-organized into labeled sections (What to Check, Output Format, If Mismatches, Implementation, Related Commands) with no nested references; at ~120 lines the large inline output templates are appropriate but keep it just short of the lean-overview ideal.	4 / 5
	Total	16 / 20 Passed

Description

48%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 concise and names a specific niche, but it states only a single generic action and omits any explicit "Use when..." trigger guidance, leaving the "when" half of completeness unaddressed. It is recognizable but under-specifies capabilities and trigger phrases.

Suggestions

Add concrete actions beyond "check", e.g. "Report mismatches and suggest exact fixes for guide/landing synchronization".

Append an explicit trigger clause: "Use when the user asks to verify guide and landing site are in sync, or mentions sync status, version mismatches, or template/quiz counts."

Include natural synonyms ("sync", "in sync") and concrete artifacts (template counts, quiz questions, versions) to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The phrase "Check guide/landing synchronization status" names the domain (guide/landing) but offers only one minimal, generic action ("check ... status"), matching the anchor for naming a domain with minimal actions rather than listing concrete capabilities.	2 / 5
Completeness	The "what" is reasonably clear (check sync status between guide and landing) but the "when" is entirely absent with no "Use when..." clause; per the guideline a missing trigger clause caps completeness, and the clear-what/no-when pattern matches the anchor at 3.	3 / 5
Trigger Term Quality	It includes relevant natural terms ("guide", "landing", "synchronization") that a user might say, but misses common variations/synonyms like "sync" and lacks the explicit "Use when..." trigger phrasing, so coverage is partial.	3 / 5
Distinctiveness Conflict Risk	The guide/landing synchronization niche is fairly specific and unlikely to trigger for unrelated skills, though the generic word "synchronization" leaves minor overlap risk with other sync-related skills, fitting the "mostly distinct" anchor.	4 / 5
	Total	12 / 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: FlorianBruniaux/claude-code-ultimate-guide
Path: .agents/skills/source-command-sync/SKILL.md
Commit: e828d7f

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.