Tessl • The management layer for AI agent skills

SkillPublic

npm-deploy

Audit the Pi extension packages against npm, land their version bumps, tag them so the publish workflow runs, refresh and verify.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Quality

Content

88%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 highly actionable, well-sequenced deployment runbook: nearly every instruction is an exact command with explicit validation gates, stop conditions, and recovery loops for a batch publish operation. Its only real costs are repeated explanations of the tag-push/dispatch mechanics and an inline admin section that would fit better as a reference file.

Dimension	Reasoning	Score
Conciseness	The body is dense with operational content and explains no general concepts, but the publish-workflow dispatch mechanics are restated across 'Hard rules', Audit step 5, Publish steps 1-4 and 'Trusted publishing', and 'tools/publish-npm --help' is cited three times — repetition that could be trimmed.	4 / 5
Actionability	Every step carries copy-paste-ready commands ('npm view <name> version', 'kendex version-compare', 'git diff --name-only <tag>..<base> -- pi-extensions/<dir>', the exact 'gh run list' jq invocation, 'kendex refresh --global --yes') plus the exact PR subject and tag naming with an example, and edge cases (E404, moved tags, first-release) are explicitly handled.	5 / 5
Workflow Clarity	Audit → documentation check → validation → bump → publish/tag/refresh/verify is clearly sequenced with explicit stop conditions ('Hold every package's verdict before touching anything'), validation gates ('Do not proceed on a failing validation'), and feedback loops for error recovery (failed run → read --log-failed → fix or re-dispatch; 'kendex update-pi --check' must report every package up to date).	5 / 5
Progressive Disclosure	A single well-sectioned SKILL.md with one-level-deep external links (CHECKS.md, changelog README, D003), but no bundle files exist and the admin-facing 'Trusted publishing' section — whose first-release bootstrap content duplicates Audit step 7 — could live in a separate reference.	4 / 5
	Total	18 / 20 Passed

Description

70%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 specific, third-person description naming five concrete actions for a distinct niche. Its one structural weakness is the missing 'when' — no explicit trigger clause tells Claude when to reach for this skill.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to publish, release, or deploy the Pi extension packages to npm, or to audit which packages need an npm release.'

Give 'refresh and verify' concrete objects, e.g. 'refresh the installed copies and verify them with kendex update-pi --check', so every named action is fully concrete.

Include natural synonyms users would say — 'release', 'publish to npm', 'deploy' — alongside 'publish' and 'version bumps' to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	It lists five concrete actions ('Audit the Pi extension packages against npm', 'land their version bumps', 'tag them so the publish workflow runs', 'refresh and verify'), but 'refresh and verify' carry no objects, leaving minor gaps versus the comprehensive anchor 5.	4 / 5
Completeness	The 'what' is clear and multi-part (audit, bump, tag, publish, refresh, verify), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	Natural terms users would say are present — 'npm', 'publish', 'version bumps', 'tag', 'extension packages' — but common synonyms such as 'release', 'deploy' or 'ship' are missing, short of the anchor-5 synonym-and-extension coverage.	4 / 5
Distinctiveness Conflict Risk	'Pi extension packages against npm' plus 'publish workflow' carves out a clear niche tied to one repository's package set, so the risk of triggering for a different skill is minimal.	5 / 5
	Total	16 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: vanillagreencom/kendex
Path: .agents/skills/npm-deploy/SKILL.md
Revision: 32d7bc7

Reviewed: 13 hours ago

Discovery Implementation Validation

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.

npm-deploy

Table of Contents

Is this your skill?