CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

dependencies

Maintain PsychSift dependencies safely by checking compatible stable versions, release notes, peer and engine constraints, old API usage, lockfile integrity, security, and focused verification. Use for dependency updates or reviews.

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

78%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.

An exceptionally lean, well-sequenced skill body whose main weakness is actionability: it tells Claude what to inspect but rarely how, leaving key commands and details implicit. Adding a failure-handling feedback loop would round out workflow clarity.

Suggestions

Add the specific commands for each inspection step (e.g., `npm outdated`, `npm view <pkg> versions --json`, `npm audit`, `npm ls --long`) so the guidance is executable rather than directional.

Replace vague phrases like "group risky ecosystems coherently" and "broader local gates" with concrete criteria or named commands (e.g., which scripts count as local gates: `npm test`, `npm run lint`).

Add an explicit feedback loop after verification, e.g., 'If focused behavior fails, revert the offending update, re-verify, and report which dependency broke.'

DimensionReasoningScore

Conciseness

Six terse numbered directives with zero padding and no explanation of concepts Claude already knows — every token earns its place, matching the anchor-5 'lean and efficient' example.

5 / 5

Actionability

Concrete artifacts are named ("package.json", lockfile, npm configuration, Node/npm versions) but no executable commands are given (e.g., npm outdated, npm audit, npm view <pkg> versions, grep patterns for old APIs), and phrases like "group risky ecosystems coherently" and "broader local gates" are underspecified — anchor 3's 'some concrete guidance but incomplete; missing key details'.

3 / 5

Workflow Clarity

A clear 6-step sequence with an explicit verification checkpoint ("verify install integrity, focused behavior, then broader local gates") and branch handling for review-only vs update requests, but no error-recovery feedback loop for when verification fails — anchor 4 ('most checkpoints present; minor validation gaps') rather than anchor 5's explicit feedback loops.

4 / 5

Progressive Disclosure

The skill is under 50 lines, single-task, and needs no external references; the well-organized numbered list satisfies the rubric's simple-skill exception, which allows a score of 5 with just well-organized sections.

5 / 5

Total

17

/

20

Passed

Description

83%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: specific, third-person, and comprehensive on capabilities with an explicit use-when clause. The trigger coverage and the when-clause's specificity are the only areas with room to grow.

DimensionReasoningScore

Specificity

"checking compatible stable versions, release notes, peer and engine constraints, old API usage, lockfile integrity, security, and focused verification" lists seven concrete, domain-specific actions with comprehensive coverage, matching the anchor-5 example rather than anchor 4's 'minor gaps in coverage'.

5 / 5

Completeness

Both a clear "what" (the full checking list) and an explicit "when" ("Use for dependency updates or reviews") are present, but the when-clause is terse with only two trigger phrases and could be more explicit, matching anchor 4 rather than anchor 5's multiple concrete trigger phrases.

4 / 5

Trigger Term Quality

"Use for dependency updates or reviews" covers the core natural phrases, but common variations users would say — "upgrade", "packages", "outdated", "vulnerable" — are missing, fitting anchor 4 (good coverage, a few natural terms missing) rather than anchor 5's synonym/extension coverage.

4 / 5

Distinctiveness Conflict Risk

"PsychSift dependencies" scopes the skill to a specific project's dependency maintenance — a clear niche with distinct triggers and minimal conflict risk with other skills, matching anchor 5.

5 / 5

Total

18

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

BigSimmo/PsychSift

Path

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