AC nixomatic
Run any software instantly and without altering the current system using nixomatic. Use this skill whenever you need a tool, runtime, or utility that is not currently installed — for one-shot tasks (e.g. converting a PDF to text with poppler-utils, processing images with ImageMagick, transcoding media with ffmpeg, running a linter), for setting up development environments, or for anything else that requires software you do not have. Construct a nixomatic.com URL with the required packages and run the command inside nix develop. Any package available in nixpkgs is at your disposal. For project development environments, also maintain a "Development Environment" section in the project README.md.
Run any software instantly and without altering the current system using nixomatic.
As a process C 63/100 · Has gaps — weak spots: result and completion, inputs and preconditions, progress reporting
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 63/100
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 30Inputs and preconditions. Does not say what the process needs to start
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 85Steps. 59 steps, 1 vague phrases
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3250 tokens
- 100Running it twice. Mutating operations check current state
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 10 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (3 tags): a typed call is more reliable
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 701: enough signal without eating the budget
- +4Structure: 18 headings
- +3Step-by-step instructions: 59 items
- +4Has examples (12 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.