CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

update-instructions

update-instructions

Quality

57%

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

Fix and improve this skill with Tessl

tessl review fix ./.github/skills/update-instructions/SKILL.md
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 a lean, highly actionable instruction set with concrete git commands, a clear two-phase workflow, and an exact fallback response. Only minor edge-case handling (missing instructions directory, detecting a non-default upstream branch) is left unspecified.

DimensionReasoningScore

Conciseness

The ~18-line body is lean and assumes Claude's competence — "determine the merge base with the default branch... using `git merge-base HEAD origin/main`" — with no git concept explanations or padding, so every token earns its place; not 4 because there are no over-explanations to trim, only a trivial stylistic hedge ("equivalent of").

5 / 5

Actionability

Gives exact commands (`git diff`, `git diff --cached`, `git merge-base HEAD origin/main`, `git diff <merge-base>...HEAD`), a concrete target ("read every instruction file under `.github/instructions`"), and an exact output requirement ("respond exactly with: `No updates needed`") — copy-paste ready with no gaps for this task.

5 / 5

Workflow Clarity

A clear ordered sequence (uncommitted diffs → merge-base diff → read instruction files → propose updates or decline) with an explicit gate ("After understanding all of these changes") and exact conditional responses; it misses 5 because edge-case checkpoints are absent — no handling of a missing `.github/instructions` directory and no way to detect a non-`origin/main` default branch beyond "unless configured otherwise".

4 / 5

Progressive Disclosure

Under 50 lines, single task, no bundle files exist, and the body is well organized (numbered scope list, "Guidance" bullets, closing directive), which per the simple-skill guideline merits a 5 with no external references needed.

5 / 5

Total

19

/

20

Passed

Description

3%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 merely repeats the skill name as a bare slug. It conveys no capabilities, no usage triggers, and no when-to-use guidance, scoring at or near the bottom of every dimension. It needs a full rewrite as a third-person capability statement with an explicit trigger clause.

Suggestions

State concrete capabilities in third person, e.g. "Reviews uncommitted and unpushed changes on the current branch and proposes minimal wording updates to instruction files under .github/instructions that those changes invalidate."

Add an explicit "Use when..." clause, e.g. "Use when the user asks to update or refresh .github/instructions after recent branch changes."

Include natural trigger keywords users would actually say: "instructions", "guidelines", ".github/instructions", "branch changes", "update the docs".

DimensionReasoningScore

Specificity

The description is only the slug "update-instructions" — no concrete actions or objects beyond "instructions", matching the anchor "Entirely vague; no concrete actions; pure abstract language"; it is thinner than the anchor-1 example "Helps with documents", so it cannot reach 2.

1 / 5

Completeness

Neither a real "what" (just a vague verb "update") nor any "when"/"Use when..." guidance is present, matching "Missing both what and when"; the missing-trigger cap of 3 is moot since it sits at the floor.

1 / 5

Trigger Term Quality

It contains no natural keywords or phrases a user would actually say, only the name slug — matching "No natural keywords; only technical jargon or entirely generic language"; it does not reach 2 because not even one generic keyword phrase is present.

1 / 5

Distinctiveness Conflict Risk

"update-instructions" names one task domain but provides zero differentiating triggers, so it overlaps any instruction/doc-update skill — "Very broad; high overlap risk" fits better than anchor 1 because it is not entirely generic (it would not trigger for unrelated skills).

2 / 5

Total

5

/

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

description_field

'description' is very short (19 chars), consider making it more detailed

Warning

Total

15

/

16

Passed

Repository

microsoft/vscode

Path

.github/skills/update-instructions/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.