Career Evidence Toolkit

View saved version →

---
name: ats-professional-resume
description: Create a polished, ATS-safe one- or two-page resume from the bundled single-column Word template and verified candidate content. Use when the user selects the ATS template or requests a conventional application resume.
---

# ATS Professional Resume

Clone `assets/reference.docx`; never overwrite it.

## Workflow

1. Read `artifact-template.json` and resolve its paths relative to this skill.
2. Use an available document capability to clone and populate the reference. If none is available, explain the missing capability instead of recreating the design.
3. Use only approved, verified candidate content. Remove unused optional fields and unresolved placeholders.
4. Treat the resume as a continuous document. Choose one or two pages from useful evidence, not a fixed canvas.
5. Render and inspect every page before finalizing.

## ATS contract

- Preserve real text, conventional headings, bullets, single-column reading order, and printable bounds.
- Do not place important content in headers, footers, floating text boxes, charts, graphics, or multi-column containers.
- Keep a heading with enough following content to establish its section. Roles and projects may split between bullets when necessary.
- Do not add filler, force a page break, or shrink typography merely to hit a page count.
- Correct large avoidable page-one whitespace, nearly empty second pages, orphan headings, awkward title splits, clipping, and inconsistent spacing.

User instructions control content. The retained reference controls unrequested visual decisions.

Referenced files: 4

View saved version →

---
name: career-onboarding
description: Set up a private career workspace, import approved professional evidence, initialize a master resume, and approve resume templates. Use for first-time Career Evidence Toolkit setup or when the user asks to reconfigure its storage, sources, or templates.
---

# Career Onboarding

Configure the toolkit without placing personal data inside the plugin repository.

## Boundaries

- Require one durable private storage destination before generating career files.
- Explain the exact source and intended use before accessing an external profile or account.
- Treat public-profile review, authenticated-profile review, uploads, file organization, and document writes as separate permissions.
- Never request passwords, one-time codes, API keys, tokens, private keys, or payment information.
- “Credentials” in this workflow means professional certificates, not authentication secrets.
- Do not fork, clone, star, publish, share, or change repository visibility without explicit authorization for that action.

Read [references/onboarding-flow.md](references/onboarding-flow.md) for the staged interview. Read [references/workspace-contract.md](references/workspace-contract.md) before creating the workspace.

## Workflow

1. Detect available storage and profile/document capabilities. Do not claim a connector is available until a harmless read confirms it.
2. Ask the questions in short stages: identity, profiles, storage, existing evidence, career direction, permissions, and templates.
3. Show the proposed workspace location and structure. Create it only after approval.
4. Import or link only user-approved sources. Preserve originals.
5. Create a structured evidence inventory that records source, confidence, attribution, date precision, maturity, and verification status.
6. Invoke `master-resume-maintainer` in `INITIALIZE` mode. Do not mark the result canonical until factual and document validation pass and the user approves it.
7. Audit certificate evidence with `certificate-registry-sync`. Write or organize files only when authorized.
8. Preview the bundled ATS and Executive templates. Let the user approve the defaults, make restrained customization, or provide a `.docx` template.
9. For a custom template, preserve the original, sanitize a clone, replace personal content with placeholders, render every page, and obtain approval before activation.
10. Verify that the six bundled skills are discoverable. Provide storage, evidence, master-resume, registry, template, integration, and future-command status.

## Completion

Return a concise onboarding report. Never include sensitive source contents in the report merely to prove they were read.

Referenced files: 3

View saved version →

---
name: certificate-registry-sync
description: Audit professional certificate files and public credential records, maintain a deduplicated certification registry, and report discrepancies with a master resume or professional profile. Use when the user asks to check, sync, enrich, organize, or reconcile certificates.
---

# Certificate Registry Sync

Maintain verified professional credential evidence without assuming one provider contains the complete archive.

Read [references/registry-schema.md](references/registry-schema.md) before creating or changing a registry.

## Modes

- `AUDIT`: read approved sources and report findings without external writes.
- `SYNC`: update the registry and approved archive after confirming write scope.

## Source roles

- Stored certificate file: primary evidence that an artifact is archived.
- Public verification page: primary evidence for title, issuer, date, and credential ID.
- Official course page: enrichment for description, objectives, and provider-listed skills.
- Professional profile: discovery and reconciliation source.
- Master resume: reconciliation target, not primary certificate authority.

## Workflow

1. Resolve approved certificate locations and registry destination.
2. Inventory certificate files without deleting anything.
3. Inspect approved profiles and public credential links when accessible.
4. Match records by credential ID; otherwise use normalized platform, issuer, title, and date.
5. Preserve discrepancies until a stronger source resolves them.
6. Separate provider-listed `Official Skills` from conservative `Resume Skills`.
7. In `SYNC` mode, update registry rows and rename only clearly matched files when explicitly authorized. Never delete evidence automatically.
8. Report verified, enriched, missing-file, missing-profile, duplicate, conflicting, and unresolved records.

If master-resume editing was not explicitly requested, report resume discrepancies without changing the resume.

Referenced files: 2

View saved version →

---
name: executive-technical-resume
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.
---

# Executive Technical Resume

Clone `assets/reference.docx`; never overwrite it.

## Purpose

Executive 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.

## Workflow

1. Read `artifact-template.json` and resolve its paths relative to this skill.
2. Use an available document capability to clone and populate the reference.
3. Build a structured content model before filling layout cells.
4. Populate supported placeholders, preserve mixed-run formatting, and remove unused optional containers completely.
5. Render, inspect, rebalance by complete semantic blocks when needed, and re-render.

## Evidence and pagination

- Maximum two pages; never force a second page.
- Prefer fewer, stronger evidence blocks proving distinct dimensions.
- Preserve historical titles, claim strength, project maturity, and verified metrics.
- Page one establishes positioning, progression, operating model, and concise proof.
- Page two, when justified, provides project, impact, leadership, production, and education evidence.
- Do not repeat the full page-one hero or sidebar on page two.

## Visual contract

- Coral is a micro-accent; meaningful body and evidence text remains dark.
- Preserve bullet glyph and body-text run roles.
- Preserve the dynamic PAGE field in the footer.
- Do not solve overflow primarily by shrinking text, reducing contrast, crushing spacing, or narrowing evidence columns.
- Remove unresolved placeholders, empty containers, orphan headings, stranded bullets, clipping, overlap, and weak spill pages.

User instructions control content. The retained reference controls unrequested appearance.

Referenced files: 4

View saved version →

---
name: master-resume-maintainer
description: Initialize or update a comprehensive master resume from approved career evidence. Use when the user asks to create, refresh, reconcile, correct, or enrich their long-form career source of truth; do not use for a short job-specific resume.
---

# Master Resume Maintainer

Maintain a comprehensive, evidence-backed source of truth. The master resume has no artificial one- or two-page limit.

Read [references/evidence-policy.md](references/evidence-policy.md) before accepting claims. Read [references/document-model.md](references/document-model.md) before creating or restructuring the document.

## Modes

- `INITIALIZE`: create the first master resume and evidence inventory.
- `UPDATE`: compare new evidence with the current master and change only missing, stale, weaker, duplicated, or incorrect material.

## Workflow

1. Resolve the private configuration and canonical destination. If updating, read the current master first.
2. Read only user-approved sources. Build a semantic inventory of existing and candidate claims.
3. Classify each candidate as `ADD`, `ENRICH`, `CORRECT`, `IGNORE`, or `NEEDS CONFIRMATION`.
4. Accept material evidence: meaningful capability, ownership, architecture, leadership, production responsibility, verified scale, major project, employment change, education, or certification.
5. Reject routine ticket churn, speculative work, unsupported metrics, credential secrets, confidential data, and technology exposure with no meaningful use.
6. Draft factual accomplishment language using action, system or problem, personal contribution, and verified outcome or scale.
7. Preserve exact historical titles and distinguish personal ownership, team contribution, and company outcomes.
8. Show consequential corrections or unresolved conflicts before writing. Edit only when the configured permission allows it.
9. Re-read the result for duplication, chronology, attribution, maturity, unsupported claims, and storage consistency.

## Completion

Summarize added, enriched, corrected, unresolved, and intentionally skipped material. If nothing meaningful changed, say so.

Referenced files: 3

View saved version →

---
name: targeted-resume-generator
description: Analyze a target job title or specific vacancy against a verified master resume, select relevant evidence, and create truthful ATS or executive resumes. Use for generic role positioning, job descriptions, job URLs, recruiter requests, and application packages; do not silently update the master resume.
---

# Targeted Resume Generator

Use the current approved master resume and evidence inventory as the factual authority. A job description controls relevance and terminology, never candidate facts.

Read [references/analysis-and-selection.md](references/analysis-and-selection.md) before selecting content. Read [references/output-quality.md](references/output-quality.md) before generating documents.

## Modes

- `ROLE_TITLE`: create reusable positioning for a named job title without inventing an employer.
- `VACANCY`: analyze a complete job description or URL and target that opportunity.

## Workflow

1. Resolve mode, requested deliverables, template choice, and approved evidence source.
2. In vacancy mode, ingest the complete opportunity and preserve its URL when supplied.
3. Classify important requirements as `STRONG MATCH`, `PARTIAL MATCH`, or `NOT EVIDENCED`.
4. Recommend positioning and an application decision. Separate blocking gaps, learnable gaps, and irrelevant nice-to-haves.
5. Build an evidence budget. Every selected experience, project, credential, and skill must prove a target need.
6. Honor user selection preferences, but flag requested evidence that is weak, irrelevant, unverified, or redundant.
7. Choose one or two pages from evidence density. Two pages are a ceiling, not a target.
8. Invoke `ats-professional-resume`, `executive-technical-resume`, or both.
9. Render and inspect every page. Correct factual, semantic, pagination, and visual failures before delivery.
10. Report potentially valuable missing master evidence without modifying the master.

Historical titles remain exact. Target headlines may be adapted without pretending they were formal employment titles.

Referenced files: 3