CtrlK
BlogDocsLog inGet started
Tessl Logo

package-npm-nix

Package npm/TypeScript/Bun CLI tools for Nix. Use when creating Nix derivations for JavaScript/TypeScript tools from npm registry or GitHub sources, handling pre-built packages or source builds with dependency management.

92

1.63x
Quality

88%

Does it follow best practices?

Impact

100%

1.63x

Average score across 3 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with a clear, validated workflow, but it suffers from redundancy across sections and keeps all reference-style content inline rather than splitting it into bundle files. Tightening duplicates and externalizing some sections would improve it.

Suggestions

De-duplicate recurring guidance: consolidate the shebang replacement, dontStrip, and chmod examples that currently appear in quick_start, common_patterns, and anti_patterns into a single canonical location.

Move troubleshooting, common_patterns, and metadata_requirements into separate reference files (e.g. TROUBLESHOOTING.md, PATTERNS.md) linked from SKILL.md to apply progressive disclosure and keep the main file as a lean overview.

Trim the anti_patterns section, which largely re-states guidance already covered in common_patterns, keeping only genuinely distinct pitfalls.

DimensionReasoningScore

Conciseness

Mostly efficient executable code, but guidance is repeated across sections — shebang replacement, dontStrip, and chmod each recur in quick_start, common_patterns, and anti_patterns, with the anti_patterns section largely re-treading common_patterns.

2 / 3

Actionability

Two complete copy-paste-ready Nix derivations plus concrete commands (nix-prefetch-url, nix hash convert, nix build, nix flake check) give fully executable, specific guidance.

3 / 3

Workflow Clarity

A clear 5-step sequenced workflow with explicit validation (build checklist, nix flake check, test commands) and feedback loops in troubleshooting (hash mismatch -> rebuild; lib.fakeHash -> build -> update hash -> rebuild).

3 / 3

Progressive Disclosure

Well-organized section tags, but the ~590-line body is a monolith with no bundle files or external references, and content that could be split (troubleshooting, common patterns, metadata) is inline; the under-50-line simple-skill exemption does not apply.

2 / 3

Total

10

/

12

Passed

Description

100%

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 specific, complete, and distinctive: it states concrete capabilities and gives an explicit "Use when" trigger with natural keywords. It is a strong, well-targeted skill description.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "handling pre-built packages or source builds with dependency management" across "npm registry or GitHub sources" — rather than vague language.

3 / 3

Completeness

Explicitly answers both what ("Package npm/TypeScript/Bun CLI tools for Nix") and when via an explicit "Use when creating Nix derivations..." trigger clause.

3 / 3

Trigger Term Quality

Covers natural terms a user would say (npm, TypeScript, Bun, JavaScript, CLI, Nix, GitHub), not just technical jargon, though "Nix derivations" is mildly jargon-heavy.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear, narrow niche (npm/TS/Bun CLI tooling packaged for Nix) with distinct triggers, making conflict with other skills unlikely.

3 / 3

Total

12

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (591 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository
YPares/agent-skills
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.