AC work-application
CV generation, job scraping, offer analysis, and application tracking. Use when: (1) generating or adapting a CV/resume for a job offer, (2) scraping job offers from French platforms, (3) analyzing and ranking job offers, (4) generating a full analysis report for a single offer (skills, company, location, salary), (5) tracking candidatures and their status, (6) validating CV content against formatting guardrails. NOT for: cover letter generation (planned), LinkedIn direct messaging, job application submission, salary negotiation coaching.
CV generation, job scraping, offer analysis, and application tracking.
As a process C 58/100 · Has gaps — weak spots: result and completion, inputs and preconditions, 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 · 3
✓ No critical or high findings
Medium and low: 3
-
low Dangerous commands
cmd-privilegescripts/_analyzer.py:745Privilege escalation / world-writable permissions (detector / deny-list definition; string literal in code, not executed)args=["--no-sandbox", "--disable-setuid-sandbox"],
detectorcode literal -
low Dangerous commands
cmd-privilegescripts/_report.py:296Privilege escalation / world-writable permissions (detector / deny-list definition; string literal in code, not executed)args=["--no-sandbox", "--disable-setuid-sandbox"],
detectorcode literal -
low Dangerous commands
cmd-privilegescripts/_report.py:401Privilege escalation / world-writable permissions (detector / deny-list definition; string literal in code, not executed)args=["--no-sandbox", "--disable-setuid-sandbox"],
detectorcode literal
Files scanned: 19. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "homepage" - note
frontmatter-keyunknown frontmatter key "ontology"
Process rating: all ten parameters 58/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 5 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (web, python) that frontmatter does not declare
- 85Steps. 37 steps, 1 vague phrases
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3285 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 16 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
- +3Output format is not stated: the model decides each time
- -311 of 14 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 544: enough signal without eating the budget
- +4Structure: 26 headings
- +3Step-by-step instructions: 37 items
- +4Has examples (7 code blocks)
- +4Reference files are cited in the instructions (2 of 2)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.