AB edid-parser
Parse and analyze EDID (Extended Display Identification Data) from monitors and displays. USE WHEN: (1) User wants to read/parse display EDID information; (2) Checking display capabilities and supported modes; (3) Debugging display/HDMI/CEC issues; (4) Listing available video outputs; (5) Validating EDID data and generating diagnostic reports; (6) Batch processing multiple EDID files; (7) Working with DRM/KMS/display subsystems. SUPPORTS: Linux sysfs (/sys/class/drm/*/edid), binary EDID files (.bin), raw hex data. OUTPUT: Human-readable reports, JSON data, validation results.
As a process B 66/100 · Nearly there — weak spots: result and completion, when it triggers, 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: 11. 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 66/100
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. No external tools needed
- 100Steps. 22 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1260 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
- +1No license
- +2Single-language instructions
- +3Description length 586: enough signal without eating the budget
- +4Structure: 27 headings
- +3Step-by-step instructions: 22 items
- +4Has examples (18 code blocks)
- +4Reference files are cited in the instructions (3 of 3)
- +3All 6 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 91.