SKILLEMALL.ai
GitHub ↗ RU Sign in

AC tailor

Write a resume, and optionally a cover letter, for one or more queued jobs from the user's profile. Use when the user says /tailor, "tailor my resume for this job", "write a cover letter for", or wants the application to carry a resume written for the posting. Every claim is checked against the profile before the PDF is made.

qbeka/jev-job-search Agent Skills author: qbeka 1 file body ≈ 512 tokens Open the sourcegithub.com↗ analyzed 17 h ago

Write a resume, and optionally a cover letter, for one or more queued jobs from the user's profile.

As a process C 55/100 · Has gaps — weak spots: result and completion, inputs and preconditions, failures and branches

GeneratorWriting and documentstype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
A
95/100
safety, quality, tests
Safety 60%
100
Quality 40%
88
Run on models
none yet
Process rating
C
55/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

How to improve

    For the model run — optional
    • 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: 1. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • note frontmatter-key unknown frontmatter key "effort"

    Process rating: all ten parameters 55/100

    • 0Result and completion. Does not say what the result is
    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Failures and branches. Linear process with no failure handling
    • 30Running it twice. 1 mutating operations with no state check
    • 70When it triggers. States when to use, but not when not to
    • 75Steps. 3 steps
    • 100Tools and files. No external tools needed
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 512 tokens
    • 100Progress reporting. Reports progress
    • low The response is described with custom markup (6 tags): a typed call is more reliable

    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
    • +1No license
    • +2Single-language instructions
    • +5Description quotes 2 example trigger phrases
    • +3Description length 327: enough signal without eating the budget
    • +4Structure: 4 headings
    • +3Step-by-step instructions: 3 items
    • +4Has examples (1 code blocks)

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 88.