AF csv-inspect
Inspect delimited tables (CSV/TSV) before any analysis: column names, encodings, delimiters, row counts, inferred types, and first/last rows. Use when the user asks to peek a CSV, list headers, show head/tail, preview schema, check dtypes, or before pandas work on .csv/.tsv/.tab files. Use when the user runs /csv-inspect. Do not use for Excel workbooks (.xlsx) or for writing statistical reports — inspect only, then stop or hand off.
Inspect delimited tables (CSV/TSV) before any analysis: column names, encodings, delimiters, row counts, inferred types, and first/last rows.
As a process F 52/100 · Will not run — References files that are not bundled: scripts/csv-inspect
How to improve
- The text references files that are not there: add them or drop the references.
- 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: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: scripts/csv-inspect
Process rating: all ten parameters 52/100
- 0Tools and files. 1 referenced file(s) missing: scripts/csv-inspect
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 65Failures and branches. 3 branches
- 100Steps. 15 steps
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 535 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
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 436: enough signal without eating the budget
- +4Structure: 6 headings
- +3Step-by-step instructions: 15 items
- +4Has examples (1 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 83.