CtrlK
BlogDocsLog inGet started
Tessl Logo

nix-profile-manager

Expert guidance for agents to manage local Nix profiles for installing tools and dependencies. Covers flakes, profile management, package searching, and registry configuration.

76

1.42x
Quality

72%

Does it follow best practices?

Impact

74%

1.42x

Average score across 3 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./nix-profile-manager/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%

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

The content is highly actionable with copy-paste commands and well-structured progressive disclosure into real reference files, but it carries some conceptual padding and lacks validation checkpoints around destructive profile operations.

Suggestions

Add explicit verification steps before/after destructive or batch operations, e.g. run 'nix profile list --profile "$AGENT_PROFILE"' to confirm the index before 'nix profile remove' and re-list after to verify.

Trim or move the Profiles/Flakes/Packages-vs-Flakes concept explanations into the existing references to keep SKILL.md focused on commands and workflow.

DimensionReasoningScore

Conciseness

The body is largely lean and command-driven, but the Profiles/Flakes/Packages-vs-Flakes concept sections explain Nix basics that could be tightened or pushed into references, so it is mostly efficient rather than fully lean.

2 / 3

Actionability

It provides copy-paste-ready, fully executable commands throughout — 'nix profile add --profile "$AGENT_PROFILE" "nixpkgs#git"', 'nix search nixpkgs python3 --json | jq ...', 'nix profile upgrade --all' — with concrete flags and arguments.

3 / 3

Workflow Clarity

The General Workflow lists a clear sequence (resolve profile path, search, add, use) and a useful 'ask the user' checkpoint, but destructive/batch operations like 'nix profile remove ... 0' and 'nix profile upgrade --all' lack verification steps, which caps workflow clarity at 2.

2 / 3

Progressive Disclosure

The body is an overview that clearly signals one-level-deep references — flakes.md, package-search.md, profile-internals.md, registry.md — each of which exists in ./references/ with a descriptive label, giving clean navigation.

3 / 3

Total

10

/

12

Passed

Description

72%

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 and distinctive with good natural trigger terms, but it omits an explicit 'Use when...' trigger clause, capping its completeness. Adding when-to-use guidance would raise it to a top-tier description.

Suggestions

Append an explicit 'Use when...' clause, e.g. 'Use when the user asks to install tools or dependencies via Nix, manage a local Nix profile, search nixpkgs, or configure the Nix registry.'

Strengthen action verbs from 'manage/covers' to concrete operations like 'install, search, list, remove, and upgrade packages in a local Nix profile' to lift specificity to 3.

DimensionReasoningScore

Specificity

The description names the domain and several capabilities ('manage local Nix profiles for installing tools and dependencies', 'package searching', 'registry configuration'), but the verbs 'manage' and 'covers' are less concrete than the score-3 anchor's explicit action list ('Extract text... fill forms... merge documents').

2 / 3

Completeness

It clearly answers 'what' the skill does but lacks any 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

It surfaces natural terms a user needing this skill would actually say — 'Nix profiles', 'installing tools', 'flakes', 'package searching', 'registry' — giving good coverage of likely trigger phrasing.

3 / 3

Distinctiveness Conflict Risk

Local Nix profile management is a distinct, well-bounded niche unlikely to conflict with or trigger other skills.

3 / 3

Total

10

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

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.