← Career Evidence ToolkitCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
Update to Career Evidence Toolkit
Snapshot Sep 30, 2026 · 23:16 UTC · version 0.1.0
Collection source: not recorded for this historical snapshot.
First saved snapshot
No earlier snapshot is available to establish a change.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Create a selective, human-facing one- or two-page senior or executive resume from the bundled Word template. Use when the user requests executive technical positioning, leadership and delivery emphasis, or this template by name.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 242
},
{
"relative_path": "artifact-template.json",
"size_in_bytes": 82
},
{
"relative_path": "assets/preview.png",
"size_in_bytes": 374645
},
{
"relative_path": "assets/reference.docx",
"size_in_bytes": 36447
}
],
"name": "executive-technical-resume",
"skill_md_contents": "---\r\nname: executive-technical-resume\r\ndescription: Create a selective, human-facing one- or two-page senior or executive resume from the bundled Word template. Use when the user requests executive technical positioning, leadership and delivery emphasis, or this template by name.\r\n---\r\n\r\n# Executive Technical Resume\r\n\r\nClone `assets/reference.docx`; never overwrite it.\r\n\r\n## Purpose\r\n\r\nExecutive mode should answer why the candidate is unusually valuable for the target role. Emphasize progression, judgment, business-to-technical translation, leadership, delivery ownership, and selected proof. Do not pour an ATS resume into a decorative layout.\r\n\r\n## Workflow\r\n\r\n1. Read `artifact-template.json` and resolve its paths relative to this skill.\r\n2. Use an available document capability to clone and populate the reference.\r\n3. Build a structured content model before filling layout cells.\r\n4. Populate supported placeholders, preserve mixed-run formatting, and remove unused optional containers completely.\r\n5. Render, inspect, rebalance by complete semantic blocks when needed, and re-render.\r\n\r\n## Evidence and pagination\r\n\r\n- Maximum two pages; never force a second page.\r\n- Prefer fewer, stronger evidence blocks proving distinct dimensions.\r\n- Preserve historical titles, claim strength, project maturity, and verified metrics.\r\n- Page one establishes positioning, progression, operating model, and concise proof.\r\n- Page two, when justified, provides project, impact, leadership, production, and education evidence.\r\n- Do not repeat the full page-one hero or sidebar on page two.\r\n\r\n## Visual contract\r\n\r\n- Coral is a micro-accent; meaningful body and evidence text remains dark.\r\n- Preserve bullet glyph and body-text run roles.\r\n- Preserve the dynamic PAGE field in the footer.\r\n- Do not solve overflow primarily by shrinking text, reducing contrast, crushing spacing, or narrowing evidence columns.\r\n- Remove unresolved placeholders, empty containers, orphan headings, stranded bullets, clipping, overlap, and weak spill pages.\r\n\r\nUser instructions control content. The retained reference controls unrequested appearance.\r\n"
}SHA-256 of public snapshot: 01e75578648f46465eb9daa063bea88546de1005de0fdbd5e2ae999d0f9c75a0