What’s inside

One SKILL.md (the playbook) + one starter template. A preview:

Chinese Resume, One Page

> The final deliverable is a Chinese-language resume. This skill file is in English so English-speaking agents can run it — all resume text you produce must be written in Chinese, following Chinese hiring conventions.

When to use

• The user says "help me fix my resume" or "write me a resume," and can provide work-history material (or is willing to fill in items one by one).
• The user is applying to Chinese-speaking roles and needs a one-page, printable A4 resume that can be exported straight to PDF.
• An existing resume runs over one page or reads as an unfocused work log, and needs compressing, prioritising, and tailoring to the role.
• The user has an English resume they want rewritten for Chinese hiring norms — not translated literally.
• The user has a target job description (JD) and wants experience re-ordered and reworded against its keywords.

Workflow

Ask for: ① the target job's JD or a one-sentence role description; ② the existing resume or a raw work-history log; ③ shareable quantified numbers (results, scale, rankings, headcount). Chase whichever is missing first — never invent experience to "fill in the gaps."

Fixed order: basics (1 line) → one-line summary (≤ 2 lines, echoing JD keywords) → work experience, reverse-chronological (takes ~60% of the page) → project experience (keep only the 1–2 most relevant) → education → skills/certificates. Cut experience unrelated to the target role, or compress it to a single line.

Break each entry into S (context in one sentence) + T (your task) + A (what you actually did, verb-led) + R (outcome, must include a number). Prefer these strong verbs: 主导 (led), 落地 (shipped/delivered), 从0到1 (built from scratch), 推动 (drove), 重构 (rebuilt), 翻倍 (doubled), 砍掉 (cut/killed). Without an exact number, give scale (team size, user volume, project timeline); if there is genuinely nothing, describe duties honestly — never fabricate an outcome.

Delete adjectives and weak verbs like 负责/参与 ("responsible for", "participated in"), merge duplicates, 1–2 lines per bullet. When over one page, cut the least relevant project/experience — never force-fit by dropping the font below 9px or margins below 12mm. A printout nobody can read is work wasted.

1. Collect materials (input: user's existing resume/JD/verbal description → action: ask for three things → output: materials checklist)
2. Set the skeleton (input: materials + JD → action: prioritise by inverted pyramid → output: section order)
3. Write the experience (input: each raw experience entry → action: STAR rewrite → output: 2–4 bullets)
4. Squeeze to one page (input: first draft → action: cut, don't shrink → output: one-page draft)
5. Produce the HTML (input: one-page copy → action: fill te

Download the full skill pack (ZIP)