CtrlK
BlogDocsLog inGet started
Tessl Logo

skill-sync

Sync Clawdbot skills between local installation and the shared skill repository. Use when asked to install, update, list, or push skills.

69

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

The canonical home for this skill is skill-sync in jdrhyne/agent-skills

SKILL.md
Quality
Evals
Security

Quality

Content

76%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 clean, actionable CLI reference with good structure and the implementation appropriately externalized to a bundle script. The main weakness is the absence of validation/verification checkpoints for the batch install --all and destructive overwrite operations.

Suggestions

Add an explicit verification step after destructive/batch operations (e.g., confirm overwrite before 'install --all' or 'install <name>' when the skill already exists, and verify the pushed PR diff before merging).

Collapse the redundant 'Examples' section into the 'Quick Reference' or convert it into genuinely distinct worked examples to recover token budget.

Note the 'gh' CLI and git authentication as prerequisites for 'push' so the workflow is executable end-to-end without guesswork.

DimensionReasoningScore

Conciseness

The body is lean with no concept over-explanation, but the "Examples" section largely restates the "Quick Reference" commands, a minor redundancy that could be trimmed.

4 / 5

Actionability

Copy-paste ready commands ("skill-sync list", "skill-sync install <name>", "skill-sync install --all", "skill-sync push <name>") are given with concrete per-command behavior, covering the common cases.

5 / 5

Workflow Clarity

Sequences for push and install are listed, but the batch "install --all" and the destructive overwrite ("Overwrites if already exists") lack validation/verification checkpoints, capping this dimension at 3 per the batch/destructive rule.

3 / 5

Progressive Disclosure

Content is organized into clear sections (Quick Reference, Commands, Configuration, Setup, Examples) with the executable implementation correctly externalized to scripts/skill-sync; minor redundancy between Quick Reference and Examples keeps it just below the top anchor.

4 / 5

Total

16

/

20

Passed

Description

92%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 concise, well-formed description that covers what the skill does, when to invoke it, and concrete actions without padding. Minor room to broaden trigger-term synonyms, but it cleanly satisfies the highest anchors.

DimensionReasoningScore

Specificity

"Sync Clawdbot skills between local installation and the shared skill repository" names the domain and pairs it with four concrete actions ("install, update, list, or push"), giving comprehensive coverage.

5 / 5

Completeness

It explicitly answers both what (sync skills between local and repo) and when ("Use when asked to install, update, list, or push skills") with concrete trigger phrases.

5 / 5

Trigger Term Quality

"Use when asked to install, update, list, or push skills" uses natural request phrasing a user would actually say, though it lacks synonyms or common variations of the verbs.

4 / 5

Distinctiveness Conflict Risk

The "Clawdbot skills" + shared-repository syncing niche is distinct with trigger verbs unlikely to fire for unrelated skills.

5 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
bap-jorkim/agent-skills-fork-feb-25
Reviewed

Table of Contents

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.