# Export Resume

> Export reviewed Chronicle projects and STAR stories into concise Korean or English Markdown resume sections. Use when drafting project experience bullets, assembling a Markdown resume, selecting defensible career claims, or refreshing resume content from the local Chronicle story bank.

- Skill: `r-jelly/export-resume` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add r-jelly/export-resume`
- Raw SKILL.md: https://api.skillmd.com/api/skills/r-jelly/export-resume/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Docs & Writing
- Author: r-jelly (https://skillmd.com/u/r-jelly)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/r-jelly/export-resume

---


# Export Resume

Create a Markdown resume artifact from reviewed evidence. This MVP does not
generate DOCX, PDF, LaTeX, or job-specific claims that are absent from Chronicle.

## Resolve the Export

Determine:

- target language, defaulting to the conversation language;
- selected projects or stories;
- target role or emphasis, if supplied;
- destination filename.

Read relevant `PROJECT.md`, `OWNERSHIP.md`, `EVIDENCE.md`, and `STAR.md` files.
Use only `reviewed` stories or sessions and `[confirmed]` claims by default.

If the user explicitly wants to include an unresolved claim, show it separately
as a draft and require confirmation before it enters the export. Never silently
promote `[inferred]` or `[needs-evidence]`.

## Select and Write

Prioritize claims that demonstrate:

- a meaningful problem and constraint;
- clear personal ownership;
- a specific technical or product action;
- a verified result or defensible qualitative outcome;
- decisions and trade-offs the user can explain in an interview.

For each project, write:

```markdown
## <Project name>

<one-line scope and context>

- <action + scope + verified result>
- <decision or technical depth + trade-off + outcome>
- <ownership or collaboration + impact>

**Tech:** <only technologies evidenced by the project>
```

Prefer two or three strong bullets over exhaustive task lists. Preserve units
and measurement context. Avoid first-person pronouns, vague adjectives,
keyword stuffing, duplicated achievements, and unsupported leadership verbs.
Do not expose private evidence references in the public-facing bullets.

## Quality Gate

Before presenting the draft, verify:

1. Every bullet maps to a reviewed, confirmed source claim.
2. Personal and team outcomes are not conflated.
3. Numbers match their source and include meaningful context.
4. The same accomplishment is not repeated across projects.
5. Language and tense are internally consistent.
6. Confidential information is generalized or omitted.
7. The user could answer “why,” “what,” and “how” for every bullet.

List excluded claims and why they were excluded.

## Save

Preview the complete Markdown before writing. Save only after approval to:

`<vault>/chronicle/resume/YYYY-MM-DD-<target>.md`

Do not overwrite an existing export without explicit confirmation. Report the
projects included, claims excluded, output path, and whether any review remains.