Clearly distinguish "easier to parse" recommendations from "guaranteed to pass screening," and keep candidate facts unchanged.
Read first
Read the Resume Fact Contract and ATS output rules in the writing guidelines. If the current environment is a source repository or has the full npm package installed @chasen-liao/resume-skills, you can use the in-package scripts for automated checks:
python skills/resume-builder/scripts/validate_resume.py --html <resume.html> --mode ats
python skills/resume-builder/scripts/validate_resume.py --pdf <resume.pdf>
The above scripts are published with the npm package (
skills/resume-builder/scripts/). When running in the package directory, replacenode_modules/@chasen-liao/resume-skills/with theskills/prefix; environments that install only SKILL.md vianpx skills adddo not have these scripts, so in that case just do the structured checks per the workflow below; do not treat the script paths as a required step.
Collaboration entry point
This is thequality gateafter master version generation and after JD-tailored version generation. By default, check and report parsing risks and keyword/fact gaps, but do not silently modify the resume; only after user confirmation, hand presentation fixes back to resume-builder or jd-tailorer。
When there is no JD, check only parseability and structure; when there is a JD, report "presentation issues that can be improved directly" separately from "genuine capability gaps that must be retained." It does not replace JD analysis, nor does it decide whether to apply.
Workflow
- Check the input format, whether extractable text exists, standard section headings, and body reading order.
- For HTML, check risks such as text carried by images, tables, complex positioning, headers and footers, and non-copyable text; for PDF, check page count and text extraction.
- Read keywords from the JD analysis, and report coverage as "exact match in confirmed candidate facts / related expression / missing."
- Give two types of recommendations: presentation fixes (can be done directly) and fact gaps (can only be probed or left as gaps).
- When export is needed, generate ATS-safe HTML/PDF with a single column, standard headings, and plain text from the same fact source; do not add skills to improve match rate.
Output format
# ATS 审计报告
## 解析与格式
- 通过：…
- 风险：…
## 关键词覆盖
| 关键词 | JD 来源 | 简历证据 | 状态 |
## 建议
1. 可直接修复：…
2. 需要候选人确认：…
Constraints
- "ATS-safe" means reducing known parsing risks; it does not mean any specific system will definitely read it correctly.
- Do not use images, charts, or visual layout to carry key information; do not change claim content or evidence status.
- Do not replace readable natural expression with keyword stuffing.