CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

npm-release

Create, review, and validate npm release workflows. Use when preparing or publishing npm packages, release channels, dist-tags, provenance, or 2FA-protected publishes.

Quality

74%

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 ./Skills/agent-ops/npm-release/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%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-organized, token-efficient runbook contract with a sensible fail-fast philosophy, but it contains no concrete npm commands or named validation gates, making it generic process boilerplate rather than an executable runbook. Its progressive-disclosure pointer targets a nonexistent path while the real bundle files go unsignaled.

Suggestions

Add concrete npm commands to the Workflow and Validation sections (e.g., `npm pack` + `npm publish --dry-run` as preflight gates, `npm publish --provenance --access public --tag beta`, `npm dist-tag ls <pkg>` and `npm view <pkg>@<version>` as publish verification).

Name the 2-3 inspection surfaces explicitly (package.json scripts, .npmrc / auth config, CI publish workflow) so "Inspect 2-3 focused surfaces" becomes a concrete step, and enumerate the inputs actually required before publish.

Fix the Progressive Disclosure path to reference the real bundle (`references/contract.yaml`, `references/evals.yaml`, `references/task-profile.json`) or move the deferred files to the path the body declares, so navigation resolves.

DimensionReasoningScore

Conciseness

The body is lean — short bullets, no concept explanations Claude already knows, no padding. Not 5 because of minor redundancy: the "broad rewrites" idea appears in Philosophy, Constraints, and Anti-Patterns, and the opening paragraph repeats the frontmatter description verbatim.

4 / 5

Actionability

No concrete commands or executable guidance anywhere — no `npm publish --provenance --access public`, `npm pack`, `npm dist-tag ls`, `npm whoami`, or dry-run equivalents; direction like "Run the narrowest real validator or command path available" stays at the hint level. Not 1 because the ordered workflow steps and fail-fast rules do instruct at a process level; not 3 because nothing in the body is npm-specific or executable.

2 / 5

Workflow Clarity

A five-step sequence exists with a stated feedback loop ("Stop at the first failed gate... Rerun the relevant validation after fixes"), so the destructive-operation cap is not triggered. Not 4 because the steps and gates are generic — "Inspect 2-3 focused surfaces" and "the narrowest real validator" name neither the concrete npm surfaces (package.json scripts, .npmrc, CI publish workflow) nor the actual gates/commands a publish runbook needs.

3 / 5

Progressive Disclosure

Section organization is clean and content is well-split into one-level sections, but the body's only bundle pointer — `Infrastructure/references/deferred-skill-context/agent-ops-npm-release/` — does not exist, and the actual bundle files (references/contract.yaml, evals.yaml, task-profile.json) are never referenced. Not 2 because nothing is inlined that belongs in a separate file and structure is good; not 4 because navigation to the real bundle is broken.

3 / 5

Total

12

/

20

Passed

Description

87%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: explicit what-and-when structure, npm-locked trigger terms, and third-person voice. Its only weakness is that the action verbs are generic, with specificity carried by domain nouns rather than concrete sub-tasks.

DimensionReasoningScore

Specificity

"Create, review, and validate npm release workflows" names several actions, and concrete domain objects ("release channels, dist-tags, provenance, or 2FA-protected publishes") add specificity. Not 5 because the verbs remain generic — no concrete sub-tasks like setting dist-tags, signing with provenance, or verifying a publish are stated as actions.

4 / 5

Completeness

Both questions answered explicitly: what ("Create, review, and validate npm release workflows") and when ("Use when preparing or publishing npm packages, release channels, dist-tags, provenance, or 2FA-protected publishes") with concrete trigger phrases. Matches the anchor-5 exemplar structure.

5 / 5

Trigger Term Quality

Natural npm-specific terms present: "npm packages", "publishing", "dist-tags", "provenance", "2FA-protected publishes". Not 5 because common variations like "npm publish", "version bump", "semver", "release notes", and "beta release" are missing.

4 / 5

Distinctiveness Conflict Risk

Clear npm-release niche with distinct, domain-locked triggers (dist-tags, provenance, 2FA-protected publishes); only trivial overlap risk with generic versioning or release-notes skills. Re-checked against anchor 4 — no closely related skill in this domain would collide on these triggers.

5 / 5

Total

18

/

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

jscraik/Agent-Skills

Path

Skills/agent-ops/npm-release/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.