CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

npm

npm registry ops: login, whoami, names, publish; 1Password tmux.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Medium

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

92%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 an exemplary operations skill: dense, imperative guidance with copy-paste commands, explicit validation and failure-recovery behavior delegated to verified helper scripts, and clean one-level-deep structure. Its only real costs are duplicated npm-11 prompt-piping guidance and a few implementation-detail bullets (symlink resolution, machine-specific absolute paths) that could be trimmed.

Suggestions

State the npm-11 prompt-piping brittleness once (in Auth) and drop the duplicated note in Reservation.

Use relative script paths consistently (e.g. scripts/publish-package.sh) instead of mixing in the machine-specific /Users/steipete/... absolute path.

Consider moving the symlink resolution internals (NPM_AUTH_SCRIPT_DIR, --preserve-symlinks-main) into a short reference note; Claude rarely needs the mechanism, only the guarantee.

DimensionReasoningScore

Conciseness

The body is lean and telegraphic with no padding of concepts Claude already knows, but npm-11 prompt-piping brittleness is stated twice (Auth bullets and Reservation Notes) and the symlink resolution internals are borderline over-detail.

4 / 5

Actionability

Copy-paste-ready bash for publishing, reservation, and the offline test harness (mktemp, env -i, trap), plus exact 1Password item/vault names, the OP_SERVICE_ACCOUNT_TOKEN default, and the npm-service.sh invocation pattern — common cases are fully covered.

5 / 5

Workflow Clarity

Explicit preconditions ("From the package root, inside the same auth tmux window") and enumerated validation/feedback behavior: verify identity, refuse existing versions, retry one expired OTP, verify registry visibility including restricted packages, continue after per-package failures, plus a stop-and-ask checklist.

5 / 5

Progressive Disclosure

A short overview delegates all execution detail to one-level-deep scripts/ files; every referenced path (npm-auth.sh, npm-auth-login.mjs, npm-service.sh, publish-package.sh, reserve-packages.sh, and the .test files) exists in the bundle.

5 / 5

Total

19

/

20

Passed

Description

66%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 a terse, telegraphic capability list that names real actions and a distinct niche, but it omits any "when to use this" trigger clause and uses compressed jargon ("names", "ops") that forces inference. It is well above generic one-liners yet below the good examples, which pair concrete actions with explicit use-when phrases.

Suggestions

Add an explicit trigger clause, e.g. "Use when publishing npm packages, checking name availability, reserving package names, or debugging npm registry auth."

Expand "names" to "package name availability/reservation" so the trigger term matches what users would naturally say.

Include the body's other covered tasks (org checks, auth debugging) so the description's capability list matches actual scope.

DimensionReasoningScore

Specificity

"login, whoami, names, publish" names several concrete actions in the npm registry domain, but "names" is cryptic and body-covered capabilities (org checks, auth debugging, package reservation) are absent from the description.

4 / 5

Completeness

The "what" is clear (registry login/whoami/publish operations), but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3.

3 / 5

Trigger Term Quality

Good natural keywords — "npm", "login", "whoami", "publish", "1Password" — that users would actually say; a few natural terms like "package", "reserve", or "registry" variants are missing.

4 / 5

Distinctiveness Conflict Risk

The pairing of npm registry operations with "1Password tmux" carves a distinct niche with minimal conflict; minor overlap risk remains with generic npm or release-automation skills.

4 / 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

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository

steipete/agent-scripts

Path

skills/npm/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.