CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

update-skills

Create or update repository skills and instructions when major learnings are discovered during a session. Use when the user says "learn!", when a significant pattern or pitfall is identified, or when reusable domain knowledge should be captured for future sessions.

Quality

83%

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

75%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 well-structured, lean instructional skill with concrete commands, path conventions, and ready-to-use templates, organized as a clear decision tree with a pre-save quality checklist. Its main gaps are minor: some redundancy between the decision and quality-check sections, a placeholder in the grep example, and no worked example of an actual captured learning despite the skill itself advising concrete examples.

Suggestions

Replace the "related-keyword" placeholder in the grep example with a realistic concrete term to make the search step fully copy-paste executable.

Deduplicate the Decision section and the Quality Checks, which both cover scope/duplication criteria — merging them would trim tokens and sharpen conciseness.

Include one short worked example of a captured learning (right vs. wrong phrasing), since the skill's own step 4 asks for exactly that when creating entries.

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence — no padding explaining what skills are — but the Decision section and Quality Checks partially restate each other, and the boilerplate customization comment adds a few trimmable tokens, keeping it below anchor 5.

4 / 5

Actionability

Provides executable `ls`/`grep` commands, exact directory-path conventions, and copy-ready frontmatter templates for both skills and instructions; the placeholder "related-keyword" in the grep example and the absence of a worked right-vs-wrong learning example leave minor gaps versus fully copy-paste coverage.

4 / 5

Workflow Clarity

The sequence (identify learning → check existing files → branch 3a/3b/3c → quality checks → inform user) is clear and ends with an explicit pre-save checklist, satisfying anchor 4; it lacks the validate-and-retry feedback loop that would merit a 5, though the task is non-destructive so no cap applies.

4 / 5

Progressive Disclosure

Well-organized sections with appropriately inlined decision trees and templates, and no bundle files to reference — good structure matching anchor 4; at ~110 lines it exceeds the under-50-line simple-skill case that would allow a 5 on organization alone.

4 / 5

Total

16

/

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.

A strong description that clearly states what the skill does and gives multiple explicit, natural triggers, headlined by the distinctive "learn!" keyword. Its only weakness is moderate action specificity — "create or update skills and instructions" stays at the artifact level rather than enumerating the concrete operations involved.

Suggestions

Enumerate the concrete actions more specifically (e.g., "add learnings to existing instruction files, scaffold new SKILL.md files with frontmatter, choose between .github/skills and .agents/skills locations") to raise specificity.

Add one or two common user phrasings as triggers, such as "remember this" or "save this for future sessions", to broaden natural keyword coverage.

DimensionReasoningScore

Specificity

"Create or update repository skills and instructions" names the domain plus 1-2 concrete actions, but coverage is not comprehensive — it lacks the fuller enumeration of concrete actions seen at anchor 4 (e.g., multiple distinct operations with object-level detail).

3 / 5

Completeness

Explicitly answers both what ("Create or update repository skills and instructions") and when ("Use when the user says \"learn!\", when a significant pattern or pitfall is identified, or when reusable domain knowledge should be captured") with concrete trigger phrases, matching the anchor-5 example structure.

5 / 5

Trigger Term Quality

Includes the natural trigger phrase "learn!" plus "significant pattern or pitfall" and "reusable domain knowledge" — good keyword coverage, though common user variations like "remember this" or "save this learning" are missing, so it falls short of anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

It occupies a clear meta-niche — persisting session learnings into skills/instructions — anchored by the highly distinctive "learn!" trigger, giving minimal conflict risk with domain-specific skills.

5 / 5

Total

17

/

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

posit-dev/positron

Path

src/vs/sessions/skills/update-skills/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.