CtrlK
BlogDocsLog inGet started
Tessl Logo

update-installed-skills

Use when syncing or updating previously installed skills to their latest version. Always dry-run updates before applying, and check for breaking changes.

72

Quality

88%

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

SKILL.md
Quality
Evals
Security

Quality

Content

93%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 an exemplary lean operational skill: fully executable commands, a clearly sequenced workflow with a dry-run validation checkpoint, and well-organized sections with no bundle overhead. The only gap is the absence of a post-apply verification step and an explicit bulk-apply command in the workflow.

DimensionReasoningScore

Conciseness

The body contains no concept explanations Claude already knows and no padding — every line is a command, an operational guardrail, or a gotcha. It matches anchor 5 ('lean and efficient; every token earns its place') and is clearly above anchor 4's 'minor instances of over-explanation'.

5 / 5

Actionability

All five workflow steps are copy-paste-ready executable commands (e.g., "npx ai-agent-skills sync <skill-name> --dry-run", "npx ai-agent-skills list --installed --format json --fields name") covering list, check, dry-run, apply, and bulk cases. This matches anchor 5 ('fully executable; copy-paste ready; covers the common cases').

5 / 5

Workflow Clarity

A clear five-step sequence with an explicit validation checkpoint (dry-run → review output → apply), so the destructive/batch cap of 3 does not apply. It falls short of anchor 5 because there is no post-apply verification, no error-recovery feedback loop, and the bulk path shows only the dry-run without the corresponding apply command.

4 / 5

Progressive Disclosure

The skill is under 50 lines, has no bundle files (references/, scripts/, assets/ do not exist) and references none, and is organized into clear Goal/Guardrails/Workflow/Gotchas sections. Per the simple-skill guideline this matches anchor 5 for well-organized single-file structure.

5 / 5

Total

19

/

20

Passed

Description

83%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 description: it leads with an explicit 'Use when' trigger containing natural user phrasing, states concrete operational behaviors (dry-run, breaking-change checks), and occupies a distinct update-installed-skills niche. The only improvements are adding missing natural synonyms ('upgrade', 'check for updates') and sharpening the what as a standalone capability statement.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions — "syncing or updating previously installed skills to their latest version", "dry-run updates before applying", "check for breaking changes" — with minor gaps (no mention of listing, backup, or rollback). This matches anchor 4 ('several specific actions; minor gaps') better than 3 (only 1-2 actions) or 5 (comprehensive coverage).

4 / 5

Completeness

Both what (update installed skills to their latest version, dry-run, check breaking changes) and when ("Use when syncing or updating previously installed skills") are explicitly answered with concrete trigger phrases. Anti-drift check: anchor 4's 'when could be more explicit' does not fit — the when-clause here is fully explicit, so anchor 5 is the best match.

5 / 5

Trigger Term Quality

"syncing", "updating", "installed skills", and "latest version" are phrases users would naturally say, matching anchor 4's good coverage; common variations like "upgrade skills" or "check for skill updates" are missing, keeping it below anchor 5.

4 / 5

Distinctiveness Conflict Risk

"previously installed skills" and "latest version" carve a distinct update-vs-install niche with natural triggers, but there is minor overlap risk with a closely related skill-installation skill. Anchor 4 fits; not 5 because the update/install boundary is implicit rather than sharply distinguished.

4 / 5

Total

17

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
MoizIbnYousaf/ai-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.