AF harvard-cv-coverletter
Expert engine for creating Harvard-standard CVs (resumes) and cover letters following the official Harvard Office of Career Services guidelines. Use this skill when a user asks to create, write, build, draft, or improve a resume, CV, or cover letter. Relevant trigger phrases include: "write my resume", "help me with my CV", "draft a cover letter", "update my resume", "I need a CV for a job application", "create a professional resume", "I'm applying for a job and need a cover letter", or any explicit request involving job application documents. Also use when the user shares their background and asks for help getting it into document form. Produces .docx files matching Harvard's exact formatting guidelines, including bullet-format and paragraph-format resume variants.
As a process F 52/100 · Will not run — References files that are not bundled: references/harvard-rules.md
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: references/harvard-rules.md
Process rating: all ten parameters 52/100
- 0Tools and files. 1 referenced file(s) missing: references/harvard-rules.md
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 30Inputs and preconditions. Does not say what the process needs to start
- 60Failures and branches. 2 branches
- 85Steps. 34 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 2105 tokens
- 100Running it twice. Mutating operations check current state
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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -4Absolute local paths (C:\Users, /home/…): not portable
- +1No license
- +2Single-language instructions
- +5Description quotes 7 example trigger phrases
- +3Description length 776: enough signal without eating the budget
- +4Structure: 20 headings
- +3Step-by-step instructions: 34 items
- +4Has examples (13 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 79.