export-resume
Skill0 starsChanged 4 months agoMITView on GitHub
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.
In this repository7 other files it gives its agents.
- audit-career-evidenceSkill
- capture-sessionSkill
- craft-starSkill
- initSkill
- quiz-projectSkill
- tilSkill
- update-projectSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 5 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Create a Markdown resume artifact from reviewed evidence.
- Very specific: line 20
Read relevant PROJECT.md, OWNERSHIP.md, EVIDENCE.md, and STAR.md files.
- Very specific: line 21
Use only reviewed stories or sessions and [confirmed] claims by default.
- Very specific: line 23
If the user explicitly wants to include an unresolved claim, show it separately as a draft and require confirmation before it enters the …
- Distinctive: line 51
Prefer two or three strong bullets over exhaustive task lists.
- Distinctive: line 54
Do not expose private evidence references in the public-facing bullets.
- Distinctive: line 58
Before presenting the draft, verify:
- Distinctive: line 60
Every bullet maps to a reviewed, confirmed source claim.
- Distinctive: line 76
Do not overwrite an existing export without explicit confirmation.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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:
## <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:
- Every bullet maps to a reviewed, confirmed source claim.
- Personal and team outcomes are not conflated.
- Numbers match their source and include meaningful context.
- The same accomplishment is not repeated across projects.
- Language and tense are internally consistent.
- Confidential information is generalized or omitted.
- 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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

