CtrlK
BlogDocsLog inGet started
Tessl Logo

deps-health-inline

Inline orchestration workflow for dependency audit and updates with Beads integration. Provides step-by-step phases for dependency-auditor detection, priority-based updates with dependency-updater, and verification cycles.

62

Quality

73%

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 ./.claude/skills/deps-health-inline/SKILL.md
SKILL.md
Quality
Evals
Security

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.

The body is a well-sequenced, highly actionable workflow with strong validation and feedback loops. The only leverage point is mild verbosity in the inline TodoWrite and summary templates, which keeps conciseness and progressive disclosure at 4 rather than 5.

Suggestions

Condense the Phase 1 TodoWrite JSON to a compact bullet list of the eight tracked items instead of the full JSON array to trim tokens.

Shorten the Phase 7 summary template to the essential fields, or note that it is a template to fill rather than reproducing the full markdown block.

Consider splitting the Beads command reference (currently the Quick Reference table plus inline commands) into a short references section so the core phase flow reads leaner.

DimensionReasoningScore

Conciseness

The body is dense with commands and procedural steps with almost no concept-padding, though the full TodoWrite JSON array and the markdown summary template could be trimmed slightly.

4 / 5

Actionability

Provides copy-paste-ready shell commands (bd create, pnpm type-check, pnpm build) and fully-specified Task-tool subagent prompts whose template variables are clearly substitutable, covering the common cases.

5 / 5

Workflow Clarity

Seven phases are clearly sequenced with explicit quality-gate validation, a verification feedback loop (Phase 6 retry up to 3 iterations), rollback procedures, and a TodoWrite checklist — matching the explicit-validation-with-feedback-loops anchor.

5 / 5

Progressive Disclosure

No bundle files exist, so all content is inline in one well-sectioned file with an overview and quick-reference table; good structure, but the ~300-line single-file form leaves minor organization gaps versus a cleanly split layout.

4 / 5

Total

18

/

20

Passed

Description

58%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 clearly communicates the skill's purpose and concrete phases but lacks an explicit 'when to use it' trigger clause and leans on internal tool names rather than natural user keywords. Adding a 'Use when...' sentence with common terms would lift the two capped dimensions.

Suggestions

Add an explicit 'Use when...' trigger clause (e.g., 'Use when auditing or updating project dependencies, fixing vulnerable or outdated packages, or running a dependency health check').

Replace or supplement tool-jargon terms (dependency-auditor, dependency-updater, Beads) with natural user phrasing like 'dependency audit', 'update outdated packages', 'fix security vulnerabilities'.

Mention concrete scope items (security vulnerabilities, outdated major versions, unused/deprecated packages) to push specificity toward comprehensive coverage.

DimensionReasoningScore

Specificity

Names the dependency-audit domain and several concrete actions ('dependency-auditor detection', 'priority-based updates with dependency-updater', 'verification cycles'), landing just below the comprehensive-coverage anchor.

4 / 5

Completeness

The 'what' is clearly stated, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

'dependency audit' and 'updates' are natural user terms, but the description leans on tool jargon (dependency-auditor, dependency-updater, Beads) and omits common synonyms like 'outdated packages', 'security vulnerabilities', or 'upgrade dependencies'.

3 / 5

Distinctiveness Conflict Risk

The dependency-health-orchestration niche with Beads integration is mostly distinct, with only minor overlap risk against generic dependency-management skills.

4 / 5

Total

14

/

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

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
maslennikov-ig/claude-code-orchestrator-kit
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.