AC driver-card-tachograph
Parses EU Digital Tachograph driver card files (.ddd) and imports data into SQLite. Use when working with driver card data, tachograph records, or digital tachograph files for: (1) Parsing .ddd files to JSON, (2) Importing tachograph data into SQLite, (3) Exporting driving activities to CSV, (4) Analyzing driver hours, violations, or vehicle usage
As a process C 54/100 · Has gaps — weak spots: result and completion, when it triggers, failures and branches
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: 9. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: Parses EU Digital Tachograph driver card files (.ddd) and imports … ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
Process rating: all ten parameters 54/100
- 0Result and completion. Does not say what the result is
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 12 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 387 tokens
- 100Running it twice. No mutating operations
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
- -32 of 5 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 349: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 12 items
- +4Has examples (2 code blocks)
- +4Reference files are cited in the instructions (2 of 2)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.