CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pi-update

Load to check the kendex Pi extensions against a Pi release, fix what breaks, and record the verdict.

Quality

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/pi-update/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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 exceptionally lean and dense with project-specific knowledge, and the record/report formats are exact and reusable. However, it functions as a policy shell around workflows/audit-release.md, which is missing from the bundle, leaving the operational sequence unreachable and capping actionability, workflow clarity, and progressive disclosure.

Suggestions

Ship workflows/audit-release.md in the bundle (or inline its step sequence), since the body delegates the entire audit procedure to it and cites its steps 1, 4, 6, and 7 by number.

Inline a short numbered overview of the audit order (capture target version → fetch changelogs → classify entries → test extensions → fix forward → record verdict → notify fleet) so the sequence is explicit even if the workflow file is not loaded.

Add explicit validation checkpoints between phases, e.g. verify the record passes pi-extensions/package-policy.test.mjs before notifying the fleet and before the git status clean check.

DimensionReasoningScore

Conciseness

58 lean lines cover release policy, input handling, an exact verdict template, the report spec, and genuinely non-obvious notes ("Pi releases every package in lockstep under one version", "kendex installs extensions as path packages"), with no padding and no explanation of concepts Claude already knows — every token earns its place.

5 / 5

Actionability

Concrete artifacts abound (pi-extensions/pi-update.audit.md, @earendil-works/pi-coding-agent@<version>, pi-extensions/package-policy.test.mjs, lane-mail notice, a copy-ready verdict template), but the core procedure is delegated: "To audit a Pi release, follow [workflows/audit-release.md]" — and that file is absent from the bundle, so how to fetch changelogs, classify entries, and test extensions is missing. This fits anchor 3's 'some concrete guidance but incomplete; missing key details' better than anchor 4, where gaps would be minor.

3 / 5

Workflow Clarity

The actual step sequence lives in the missing workflows/audit-release.md (the body cites "step 1", "step 4", "step 6", "step 7" of a workflow that isn't there) and the body's own sections are thematic rather than sequential. Some validation exists ("tests run with pass counts", "git status --short is clean"), but checkpoints between phases are implicit, and for a fix-forward/publishing workflow the rubric caps workflow clarity at 3 when validation loops are incomplete.

3 / 5

Progressive Disclosure

Sections are well-organized and the single external reference is clearly signaled and one level deep, but scored against the actual bundle structure the sole reference, workflows/audit-release.md, does not exist — navigation dead-ends at the file holding the whole procedure. A wholly dangling reference is more than anchor 4's 'minor organization gaps', while the structure is far better than anchor 2's minimal/unorganized.

3 / 5

Total

14

/

20

Passed

Description

62%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 concrete, third-person, and highly distinctive, but it never states when to load the skill and omits the natural trigger vocabulary (update/upgrade/compatibility) a user would actually say. Adding an explicit 'Use when a new @earendil-works/pi-coding-agent release lands' clause with those synonyms would lift the two capped dimensions.

Suggestions

Add an explicit trigger clause, e.g. "Use when a new @earendil-works/pi-coding-agent release is published or Pi extensions break against a release."

Include the natural synonyms users would say — "update Pi", "upgrade Pi", "Pi compatibility" — so the description matches how the request is phrased.

Mention the downstream actions (notify the fleet, hand publication to npm-deploy) that currently live only in the summary field, for full coverage of what the skill does.

DimensionReasoningScore

Specificity

"check the kendex Pi extensions against a Pi release", "fix what breaks", "record the verdict" are three concrete actions naming the domain, matching anchor 4's 'several specific actions; minor gaps' — the fleet-notification and npm-deploy handoff (present only in the summary field) are left out, keeping it below anchor 5's comprehensive coverage.

4 / 5

Completeness

The "what" is clear (check extensions against a release, fix breakage, record a verdict) but there is no "Use when..." clause or equivalent explicit trigger guidance, which the rubric says caps completeness at 3.

3 / 5

Trigger Term Quality

"Pi extensions" and "Pi release" are relevant domain keywords, but the natural phrases a user would say — "update Pi", "upgrade Pi", "compatibility" — are missing (the skill is even named pi-update, yet "update" never appears), fitting anchor 3's 'some relevant keywords but missing common variations'.

3 / 5

Distinctiveness Conflict Risk

"kendex Pi extensions" scoped against "a Pi release" carves out a clear niche with distinct triggers and minimal conflict risk with any generic skill.

5 / 5

Total

15

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 2 missing

Warning

Total

14

/

16

Passed

Repository

vanillagreencom/kendex

Path

.agents/skills/pi-update/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.