菜单
创建、制作、生成、编写或优化简历；输出有效的 Reactive Resume JSON 或可直接打开、静态部署的单文件 HTML 简历。适用于用户说“制作简历”“生成简历”“创建简历”“写一份简历”“优化简历”或需要简历网站时。
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/0xcjl/resume-creator --skill resume-creator命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
| name | resume-creator |
| description | 创建、制作、生成、编写或优化简历；输出有效的 Reactive Resume JSON 或可直接打开、静态部署的单文件 HTML 简历。适用于用户说“制作简历”“生成简历”“创建简历”“写一份简历”“优化简历”或需要简历网站时。 |
| version | 1.0.0 |
| author | 0xcjl |
| license | MIT |
| metadata | {"hermes":{"tags":["resume","html","reactive-resume","static-site","bilingual","accessibility","print"],"related_skills":["agent-skill-publisher"]}} |
Build professional resumes through conversational AI for Reactive Resume, a free and open-source resume builder, or as a standalone HTML resume site.
For a new resume, do not generate an artifact before collecting the choices that are still missing. Ask in this order and do not repeat a choice the user has already supplied:
For JSON, the user chooses one of the 15 Reactive Resume templates. For single-file HTML, the user chooses either a named Reactive Resume visual adaptation or a native HTML style. A visual adaptation is a newly authored, self-contained HTML rendition guided by the selected template; it is not an export from the Reactive Resume app or a claim of pixel-exact parity.
Never silently apply a visual default. An agent may recommend five options, but must wait for the user's selection unless the user explicitly delegates the choice. Once all choices are known, briefly restate the chosen deliverable, language, and presentation before generating.
Select the output from the user's requested destination; do not silently replace one mode with the other.
.html file that can be opened directly with file://; do not require a build step, server, JavaScript framework, remote stylesheet, image CDN, font download, credential, or external service.For HTML mode, first gather the same factual content needed for a resume. Write only facts the user has provided or explicitly approved; preserve uncertainty as a question or omit the claim. Do not invent employers, dates, degrees, credentials, metrics, links, contact details, or project outcomes. A polished visual treatment must not imply experience that the source material does not support.
<!doctype html>, a declared document language, UTF-8 viewport metadata, a descriptive <title>, and all CSS inside one <style> block. Keep scripts out unless they are necessary for an explicitly requested, local-only interaction; the resume must remain readable without JavaScript.<header>, <main>, named <section> elements with headings, lists for achievements, and native <a> links for supplied email, phone, and URLs. Escape user-provided text before inserting it into HTML.@media print rules for clean A4/Letter-friendly printing: remove screen-only decoration, retain link destinations where useful, use sensible margins, and avoid splitting a role or major heading from its content where CSS support permits. Do not claim that the output is a generated PDF unless one has actually been generated and checked.h1, sequential headings, meaningful link text, visible keyboard focus, and no essential information conveyed only by color, hover, image, or icon. Treat a supplied headshot as optional and include meaningful alt text only when the user supplied a factual description; otherwise omit it or use empty alt text for decoration.Before delivering an HTML file, verify that it is a single self-contained file, parses as HTML, contains the expected semantic landmarks, and can be opened locally in a browser or an equivalent local renderer. For the final visual and alignment review, read references/html-quality-check.md. Report any unverified visual or print/PDF aspect clearly.
When the user explicitly authorizes static deployment, use the same source file for the deployed artifact and read the deployment review in references/html-quality-check.md. Verify the public URL separately from local rendering: DNS/TLS when a custom domain is involved, HTTP success, content identity or an equivalent source-to-public check, and a clean-browser visual pass. Confirm whether personal contact details are intended to be public before publishing; omit them from the public variant when the user requests it. Do not attribute browser-extension DOM injection to the deployed file without comparing against an extension-free renderer.
Keep the resume language aligned with the user's target reader. Support Chinese, English, and bilingual output; ask which one to use when the supplied facts do not make it clear. For bilingual output, preserve proper names, URLs, dates, credentials, and numbers exactly; translate only claims that the user supplied or approved.
Match the interaction language to the user's latest substantive resume message: reply in Chinese to Chinese interaction and in English to English interaction. This applies to the visual-path explanation, all option descriptions, recommendations, questions, progress updates, and delivery note. Preserve template names, product names, code, URLs, and user-provided proper names. For a genuinely mixed-language request, follow the language the user uses for the request itself, unless they explicitly ask for another response language.
For HTML output, read references/template-selection.md before the presentation question. Show the full requested comparison, then wait for one named Reactive Resume visual adaptation or one native HTML style. Read references/html-styles.md when the user selects a native style. If the user explicitly delegates the choice, recommend and state the selected option before generating.
When the user explicitly asks to track or manage job applications, read references/application-tracking.md. Do not load or mention application-tracking operations for ordinary resume creation.
This shared skill is available to Codex and Hermes. Use Reactive Resume MCP application tools only when the current client explicitly exposes them. If they are unavailable, do not invent tool calls or claim that an application was created or updated; gather the required facts and generate valid Reactive Resume JSON instead.
Ask for essential details first, unless the user has already provided them:
For each section the user wants to include, gather specific details. Never invent dates, company names, or achievements.
Experience: company, position, location, period (e.g., "Jan 2020 - Present"), description of responsibilities/achievements
Education: school, degree, area of study, grade (optional), location, period
Skills: name, proficiency level (Beginner/Intermediate/Advanced/Expert), keywords
Projects: name, period, website (optional), description
Other sections: languages, certifications, awards, publications, volunteer work, interests, references
Skip this step for HTML-only output. For JSON output, ask about:
Read references/template-selection.md, then the selected HTML style guidance if applicable. Create one accessible, responsive, print-ready file from the verified resume facts. Do not copy an external template or make the HTML depend on external assets.
Output must conform to the Reactive Resume schema. See references/schema.md for the complete schema structure.
Key requirements:
id fields must be valid UUIDsurl and label propertiesrgba(r, g, b, a) formatShare these tips when helping users craft their resume content:
For most professionals:
For students/recent graduates:
For JSON output, produce a complete object that conforms to the Reactive Resume schema. The user can then import it directly into Reactive Resume at https://rxresu.me. For HTML output, deliver the requested .html file and briefly state the chosen language and style.
Example minimal structure:
{
"picture": { "hidden": true, "url": "", "size": 80, "rotation": 0, "aspectRatio": 1, "borderRadius": 0, "borderColor": "rgba(0, 0, 0, 0.5)", "borderWidth": 0, "shadowColor": "rgba(0, 0, 0, 0.5)", "shadowWidth": 0 },
"basics": { "name": "", "headline": "", "email": ""
...
... ...
For the complete schema, see references/schema.md.
When information is missing, ask specific questions:
Avoid compound questions. Ask one thing at a time for clarity.