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.

71

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 efficient, fully actionable workflow with appropriate dry-run validation. The only gap is a missing explicit feedback loop for handling breaking changes or customization overwrites surfaced by the dry-run.

Suggestions

Add an explicit error-recovery step: if the dry-run shows breaking changes or local customization overwrites, back up the affected SKILL.md and abort or confirm before proceeding.

Integrate the 'back up customizations before syncing' gotcha into the workflow as an ordered step rather than only mentioning it in Gotchas.

DimensionReasoningScore

Conciseness

Lean and efficient: no concept over-explanation, direct bash code blocks, and every section (Goal, Guardrails, Workflow, Gotchas) earns its place.

5 / 5

Actionability

Fully executable, copy-paste-ready `npx ai-agent-skills` commands covering both single-skill and bulk update cases.

5 / 5

Workflow Clarity

Clear 5-step sequence with explicit dry-run and review-before-apply validation checkpoints, but no explicit error-recovery branch for when a dry-run reveals breaking changes or local overwrites.

4 / 5

Progressive Disclosure

Under 50 lines, single-purpose, with no need for external references and well-organized sections.

5 / 5

Total

19

/

20

Passed

Description

82%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 well-structured, explicitly pairing a 'Use when' trigger with concrete capability statements and a distinctive niche. Trigger-term synonym coverage is the main weakness.

DimensionReasoningScore

Specificity

Names the domain ('syncing or updating previously installed skills') plus two concrete actions ('dry-run updates', 'check for breaking changes'), but coverage is limited and not comprehensive.

3 / 5

Completeness

An explicit 'Use when...' trigger answers 'when', and the body states 'what' (sync/update to latest version, dry-run, check breaking changes) with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural terms 'syncing', 'updating', 'installed skills', and 'latest version' are present, but synonyms like 'upgrade' or 'outdated' are missing.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (updating previously installed skills) with distinct triggers and minimal overlap risk against other skills.

5 / 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.

Validation15 / 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.