skill-sync

Sync skills between local installation and the GitHub source-of-truth repository. Use when asked to install, update, list, or push skills.

6.69x

Quality

81%

Does it follow best practices?

Impact

87%

6.69x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

72%

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

This is a well-structured, concise CLI reference skill that efficiently documents the `skill-sync` tool's commands and configuration. Its main weaknesses are the lack of validation/verification steps in workflows (especially for the destructive `push` operation) and missing details about error scenarios, expected outputs, or how to confirm operations succeeded.

Suggestions

Add a typical workflow sequence with validation, e.g., 'Install a skill: `skill-sync install <name>` → verify with `ls ~/clawd/skills/<name>/SKILL.md` → check skill loads correctly'

Add expected output examples for at least `list` and `push` commands so Claude knows what success/failure looks like

Document error handling for the `push` command: what happens if `gh` CLI isn't authenticated, if there are merge conflicts, or if the branch already exists

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient. It assumes Claude knows what Git, PRs, and CLI tools are. Every section earns its place with no unnecessary explanation of concepts.	3 / 3
Actionability	The commands are concrete and copy-paste ready, but there's no information about how `skill-sync` is installed or where it comes from. The push workflow lacks detail on what happens with branch naming, PR creation, or conflict resolution. It describes commands but doesn't show complete workflows with expected outputs.	2 / 3
Workflow Clarity	The quick reference provides a clear list of commands, but there's no sequenced workflow for common multi-step operations (e.g., install → verify → use, or edit → push → confirm PR). No validation or error handling steps are mentioned for any operation, and the push workflow (which creates PRs) lacks verification checkpoints.	2 / 3
Progressive Disclosure	For a simple CLI wrapper skill under 50 lines, the structure is well-organized with a quick reference section followed by detailed command descriptions and configuration. No external references are needed given the scope, and the content is appropriately concise for a single file.	3 / 3
	Total	10 / 12 Passed

Description

89%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a solid, concise description that clearly communicates both purpose and trigger conditions. It uses appropriate third-person voice and includes natural trigger terms. The only minor weakness is that the specific actions could be slightly more detailed (e.g., what 'sync' or 'push' entails), but overall it performs well across all dimensions.

Dimension	Reasoning	Score
Specificity	Names the domain (skill syncing between local and GitHub) and some actions (install, update, list, push), but doesn't elaborate on what each action entails or describe the full range of capabilities.	2 / 3
Completeness	Clearly answers both 'what' (sync skills between local installation and GitHub source-of-truth repository) and 'when' (explicit 'Use when asked to install, update, list, or push skills').	3 / 3
Trigger Term Quality	Includes natural keywords users would say: 'install', 'update', 'list', 'push', 'skills', 'sync'. These are terms a user would naturally use when managing skills.	3 / 3
Distinctiveness Conflict Risk	Very distinct niche — syncing skills between local and GitHub is a specific operational task unlikely to conflict with other skills. The triggers (install/update/list/push skills) are clearly scoped.	3 / 3
	Total	11 / 12 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: jdrhyne/agent-skills
Commit: 292843f

Reviewed: about 18 hours 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.