AB persian-resume
Generate professional Persian (RTL) resumes/CVs that render correctly with mixed Persian-English content. Use this skill whenever the user asks to create, rewrite, polish, or transform a Persian resume/CV, or when a resume contains mixed Persian and English/technical content that must remain readable and correctly ordered in RTL. Also trigger when the user provides career info in any language and wants a professional Persian CV, or asks to fix RTL/bidi issues in a Persian resume. This skill is NOT for general Persian documents — use persian-documents for reports, letters, articles, and technical docs.
Generate professional Persian (RTL) resumes/CVs that render correctly with mixed Persian-English content.
As a process B 77/100 · Nearly there — weak spots: inputs and preconditions, progress reporting
How to improve
- 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: 6. 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 77/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 55Failures and branches. 1 branches
- 60Result and completion. Output format stated, no completion criterion
- 100Tools and files. No external tools needed
- 100Steps. 92 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 1878 tokens
- 100Running it twice. Mutating operations check current state
- low 18 top-level sections: this looks like several domains in one skill
- medium 4 test cases, all positive: not one "should refuse" or "should ask first"
- low No test case covers injection arriving through data
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
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 608: enough signal without eating the budget
- +4Structure: 21 headings
- +3Step-by-step instructions: 92 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (2 of 2)
- +3All 2 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 98.