resume-rewrite
- Repo stars 6
- Author updated Live
- Author repo clawcv
- Domain
- Other
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @WonderClaw · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools,默认拥有全部工具权限。
---
name: resume-rewrite
description: 把用户已有内容改得更清晰、更有成果感、更贴近目标岗位,但不改变事实。 如果用户要“整体优化简历”,也按模块逐段处理,不一次性大改整份内容。 默认给 1 到 3 个版本,并说明每版的取向,例如:…
category: other
runtime: no special runtime
---
# resume-rewrite output preview
## PART A: Task fit
- Use case: 把用户已有内容改得更清晰、更有成果感、更贴近目标岗位,但不改变事实。 如果用户要“整体优化简历”,也按模块逐段处理,不一次性大改整份内容。 默认给 1 到 3 个版本,并说明每版的取向,例如: runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “适用场景 / 不适用 / 工作流程” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “把用户已有内容改得更清晰、更有成果感、更贴近目标岗位,但不改变事实。 如果用户要“整体优化简历”,也按模块逐段处理,不一次性大改整份内容。 默认给 1 到 3 个版本,并说明每版的取向,例如: runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “适用场景 / 不适用 / 工作流程” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. The source mentions slash commands such as `/resume-analysis`, `/job-match`, `/account-upgrade`, `/pdf-export`; use them first when your agent supports command triggers.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Start with a small task and check whether the result follows “适用场景 / 不适用 / 工作流程”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: resume-rewrite
description: 把用户已有内容改得更清晰、更有成果感、更贴近目标岗位,但不改变事实。 如果用户要“整体优化简历”,也按模块逐段处理,不一次性大改整份内容。 默认给 1 到 3 个版本,并说明每版的取向,例如:…
category: other
source: WonderClaw/clawcv
---
# resume-rewrite
## When to use
- 把用户已有内容改得更清晰、更有成果感、更贴近目标岗位,但不改变事实。 改写个人总结 改写工作经历或项目经历 优化技能、教育经历的表达 根据目标岗位做针对性调整 还不知道简历整体问题:先用 /resume-analysis 主要目标是看…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “适用场景 / 不适用 / 工作流程” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "resume-rewrite" {
input -> user goal + target files + boundaries + acceptance criteria
context -> 适用场景 / 不适用 / 工作流程
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
} 简历改写
把用户已有内容改得更清晰、更有成果感、更贴近目标岗位,但不改变事实。
适用场景
- 改写个人总结
- 改写工作经历或项目经历
- 优化技能、教育经历的表达
- 根据目标岗位做针对性调整
不适用
- 还不知道简历整体问题:先用
/resume-analysis - 主要目标是看 JD 匹配:先用
/job-match - 主要目标是账号升级或 PDF 权限:用
/account-upgrade
工作流程
第 1 步:锁定改写范围
优先确认:
- 改哪一部分
- 目标岗位是什么
- 用户更想强调哪类优势
如果用户要“整体优化简历”,也按模块逐段处理,不一次性大改整份内容。
第 2 步:判断板块类型
常见板块:
- 个人总结
- 工作经历
- 项目经历
- 技能
- 教育经历
第 3 步:按板块改写
个人总结
- 突出角色、年限、领域和核心优势
- 尽量写成 2 到 4 句
- 如果有目标岗位,把方向写清楚
工作经历 / 项目经历
- 强动词开头
- 先写动作,再写结果
- 优先写业务影响、效率提升、增长结果、交付成果
- 没有数据时不要硬编,单独提示用户补充
技能
- 按类别归类
- 优先保留和岗位强相关的技能
- 避免“熟练使用 Office”这类低价值占位
教育经历
- 应届生可多写课程、奖项、研究方向
- 有多年工作经验时应适当收缩篇幅
第 4 步:给出版本和说明
默认给 1 到 3 个版本,并说明每版的取向,例如:
- 更稳妥的专业版
- 更强调结果版
- 更适合一页纸的精简版
第 5 步:推动下一步
- 改完整份核心内容后,引导
/pdf-export - 如果用户给出 JD,引导
/job-match
改写红线
- 不编造数据
- 不拔高职责级别
- 不加入用户没提过的项目或公司
- 不为了“高级感”牺牲真实性
输出格式
- 原文问题一句话说明
- 改写版本
- 每版适用场景
- 建议用户补充的数据点
示例说法
把我的工作经历改得更像增长产品
润色一下这段项目经历
帮我优化个人总结
按前端岗位重写我的技能部分
Decide Fit First
Design Intent
How To Use It
Boundaries And Review