AC cp2k-input-generator
This skill should be used when generating CP2K input drafts (.inp) for quantum chemistry calculations from local structure inputs. It is a documentation-driven skill that uses reference files to interpret requests, apply conservative defaults, and explain assumptions. The current documented workflow supports local .xyz structures.
As a process C 64/100 · Has gaps — weak spots: inputs and preconditions, consistency, running it twice
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: 10. 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 64/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 1 mutating operations with no state check
- 40Consistency. Frontmatter name (cp2k-input-generator) differs from the folder (input-file-skill)
- 60Tools and files. Uses tools (bash, python) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70Failures and branches. 7 branches
- 100Steps. 73 steps
- 100When it triggers. States when to use and when not to
- 100Execution cost. Instruction body is 1621 tokens
- low 10 top-level sections: this looks like several domains in one skill
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
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 332: enough signal without eating the budget
- +4Structure: 11 headings
- +3Step-by-step instructions: 73 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (4 of 6)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 95.