CtrlK
BlogDocsLog inGet started
Tessl Logo

skill-sync

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

87

6.69x
Quality

84%

Does it follow best practices?

Impact

87%

6.69x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

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 compact, actionable CLI reference with good structure and copy-paste commands. Its main weakness is the absence of explicit validation/verification guidance for the batch and repo-mutating operations.

Suggestions

Add a short validation step for `push` (e.g., confirm the PR was created and report its URL) and a dry-run/confirm note for `install --all` to satisfy the destructive/batch workflow checkpoint expectation.

Explicitly point to the bundled implementation, e.g. "See scripts/skill-sync for the full implementation," so the bundle path is clearly signaled.

Collapse the per-command one-liners into the Quick Reference or merge them to remove the mild duplication between the two sections.

DimensionReasoningScore

Conciseness

Lean body that assumes competence and avoids over-explanation; the Commands section lightly duplicates the Quick Reference block and could be tightened slightly.

4 / 5

Actionability

Quick Reference provides copy-paste-ready, executable commands (list, install <name>, install --all, push, update) covering the common cases, backed by the bundled script.

5 / 5

Workflow Clarity

Commands are documented as a reference rather than a sequenced workflow, and the body surfaces no validation checkpoints for the batch `install --all` or repo-mutating `push` operations, capping it at 3 per the destructive/batch guidance.

3 / 5

Progressive Disclosure

Well-organized into Quick Reference, Commands, and Configuration sections, but the bundled `scripts/skill-sync` file is not explicitly referenced by path, leaving a minor navigation gap.

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 strong, third-person description that clearly states both capability and trigger conditions with concrete action verbs. Minor room for improvement only in synonym coverage of trigger terms.

DimensionReasoningScore

Specificity

Lists four concrete actions — "install, update, list, or push" — giving comprehensive coverage of the skill's capabilities, matching the anchor for multiple specific concrete actions.

5 / 5

Completeness

Explicitly states what ("Sync skills between local installation and the GitHub source-of-truth repository") and when ("Use when asked to install, update, list, or push skills") with concrete trigger phrases.

5 / 5

Trigger Term Quality

"install, update, list, or push skills" are natural user phrases with good coverage, but common synonyms like "download" or "manage" are absent, so it falls just below comprehensive.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (skill<->GitHub repository sync) with distinct triggers, making conflict with unrelated skills unlikely.

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
jdrhyne/agent-skills
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.