CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

repo-sync

Manage automatic Git syncing on macOS with repo-sync. Use only when the user explicitly invokes /repo-sync.

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%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 content body is exemplary: lean, fully executable, with explicit validation checkpoints and error-recovery guidance for every workflow, and a clean single-reference progressive-disclosure structure that matches the actual bundle. No dimension shows anchor-level weakness; the only improvement lever sits in the frontmatter description, not the body.

DimensionReasoningScore

Conciseness

The body is dense imperative prose with zero concept explanations and no padding — lines like "Installed help is the command contract" and "Flags precede positional arguments" assume Claude's competence. Every token is operational; not 4 because there is no over-explanation to trim.

5 / 5

Actionability

Every workflow ships copy-paste-ready commands with concrete arguments, e.g. `repo-sync add --config "/absolute/path/to/config.json" "/absolute/path/to/notes"`, `brew install --cask vectal-labs/tap/repo-sync`, and `repo-sync skill install`. The common cases (fresh install, existing clone, custom config) are all covered with exact commands.

5 / 5

Workflow Clarity

Each workflow is sequenced with explicit validation: a "Check first" gate (`command -v repo-sync`, `repo-sync help`), `repo-sync status` after every mutating action, and error-recovery loops such as "add may save registration despite restart failure. Check fresh status; if setup is needed, use the same config." Not 4 because checkpoints are explicit and feedback loops for failure cases are present, matching the top anchor.

5 / 5

Progressive Disclosure

The body is a well-organized overview with a single clearly signaled one-level-deep reference ("Read [references/operations.md](references/operations.md) for custom settings, unsupported commands, legacy removal, upgrades, or failed checks"), and the referenced file exists with matching sections (Legacy removal, Agent skill installation). Section-level pointers like "follow **Legacy removal** in the reference" make navigation exact.

5 / 5

Total

20

/

20

Passed

Description

61%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 honest, tightly scoped, and has an unambiguous explicit-invocation trigger that eliminates conflict risk, but it under-sells the skill's concrete capabilities. Specificity and trigger-term coverage are the weak points: a user describing their need in everyday words would not naturally match this description.

Suggestions

State the concrete operations in the description, e.g. "Commits, rebases, and pushes changes to shared repos automatically; registers repos via repo-sync add/remove and manages the launchd service" — this lifts specificity from anchor 2 to 4.

Add natural trigger keywords users would actually say, such as "auto-commit", "automatically push my notes/repo", or "keep my team repo in sync", so the description matches real user phrasing rather than only the slash-command name.

Briefly name what is synced (team documents, notes, skills, and context repos) in the description itself; currently that scope only exists in the body.

DimensionReasoningScore

Specificity

"Manage automatic Git syncing on macOS" names the domain but the action is generic; no concrete operations (commit, rebase, push) are stated. Fits anchor 2 rather than 3 because only one vague action is listed instead of 1-2 concrete ones.

2 / 5

Completeness

A clear "what" ("Manage automatic Git syncing on macOS with repo-sync") is paired with an explicit "when" ("Use only when the user explicitly invokes /repo-sync"), satisfying both halves. Not 5 because the "what" lacks the concrete capability detail of the top anchor.

4 / 5

Trigger Term Quality

"Git syncing", "macOS", and "/repo-sync" are relevant keywords, but natural user phrasings like "auto-commit", "sync my repo", or "push my notes" are missing. Not 4 because common variations and synonyms are absent, not 2 because the terms are domain-specific rather than purely generic.

3 / 5

Distinctiveness Conflict Risk

The trigger is an explicit user invocation of /repo-sync, a distinct niche with minimal overlap risk with other skills. The scoping to macOS and a single named tool further separates it from generic Git skills.

5 / 5

Total

14

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

davidondrej/skills

Path

skills/ops-and-setup/repo-sync/SKILL.md

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.