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.

1.42x

Quality

73%

Does it follow best practices?

Impact

74%

1.42x

Average score across 3 eval scenarios

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./nix-profile-manager/SKILL.md

Quality

Content

80%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 content is highly actionable with copy-paste commands and good progressive disclosure via real reference files, but its main workflow omits explicit validation/verification checkpoints for destructive profile operations, capping workflow clarity.

Suggestions

Add an explicit validation step to the General Workflow, e.g. after installing run `nix profile list --profile "$AGENT_PROFILE"` and verify the binary is on PATH before use.

Add a feedback loop for destructive operations: after `nix profile remove` or `upgrade --all`, verify the profile still resolves and report changes to the user.

Trim the inline "Packages vs. Flakes" and Core Concepts detail, moving deeper material to the existing reference files to tighten conciseness.

Dimension	Reasoning	Score
Conciseness	The body is mostly a lean command reference with minimal padding, but sections like "Packages vs. Flakes" and the inline Core Concepts explanations include minor over-explanation that could be trimmed.	4 / 5
Actionability	Commands are copy-paste ready and cover the common cases (add, list, remove, upgrade, search, registry), with a concrete worked example ("nixpkgs#git") in the quick start.	5 / 5
Workflow Clarity	The General Workflow lists a sequence (determine profile, search, add, use) but lacks explicit validation checkpoints; since profile operations are destructive/batch (remove, upgrade --all), workflow clarity is capped at 3 per the rubric.	3 / 5
Progressive Disclosure	SKILL.md is a clear overview with well-signaled, one-level-deep references (flakes.md, package-search.md, profile-internals.md, registry.md), all of which are real bundle files, making navigation easy.	5 / 5
	Total	17 / 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 clearly conveys what the skill does and covers a well-scoped Nix niche, but it lacks an explicit "Use when..." trigger clause, which caps completeness. Trigger-term and specificity coverage are strong but not comprehensive.

Suggestions

Add an explicit trigger clause, e.g. "Use when an agent needs to install tools or dependencies into a local Nix profile without sudo."

Include the natural term "nixpkgs" (and optionally the ".nix" extension) to broaden trigger-term coverage.

Sharpen the opening verb from "manage" to concrete actions like "install, search, and remove packages in local Nix profiles".

Dimension	Reasoning	Score
Specificity	Names the domain and lists several concrete capabilities ("installing tools and dependencies", "flakes", "profile management", "package searching", "registry configuration"), but the verbs "manage" and "covers" are generic rather than the sharp action verbs of a 5.	4 / 5
Completeness	The "what" is clear (manage local Nix profiles for installing tools/dependencies), but there is no "Use when..." clause or equivalent explicit trigger guidance, so completeness is capped at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Natural user keywords are present ("Nix", "profiles", "flakes", "package", "registry"), but common variations like "nixpkgs" and the ".nix" extension are missing, leaving a few natural terms uncovered.	4 / 5
Distinctiveness Conflict Risk	"Local Nix profiles" is a clear, narrow niche with minimal conflict risk, but the absence of explicit trigger phrasing leaves minor overlap risk with broader Nix or package-management skills rather than the clean distinct triggers of a 5.	4 / 5
	Total	15 / 20 Passed

Validation

100%

Warnings & errors only

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: YPares/agent-skills
Path: nix-profile-manager/SKILL.md
Commit: e9d2149

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.