Resume & Credentials

View saved version →

---
name: resume-credentials
description: Write the document that proves you can do the work — a resume, a resume tailored to one posting, or a capability statement — as a real .docx you fill in by clicking and typing, where every bullet names the engagement behind it and every code, date, figure, or credential you did not state is marked or omitted, never invented. Use when someone wants a resume, CV, tailored resume, capability statement, capabilities statement, credentials one-pager, past-performance sheet, or line card written, rewritten, or turned into a file, including asks like "turn my work history into a resume for this job posting" or "build a capability statement for my consulting firm". Do NOT use to edit, redline, or comment on a Word file the user already has, or any other kind of document — that is the built-in Documents skill's job, and you cannot invoke it on their behalf. Do NOT use for a cover letter, a client proposal or bid, a job description, a slide deck, a diagram, a logo, web page copy, or a PDF; those are separate skills.
---

# Resume & Credentials

## Goal

Write the document that gets someone past the screen — a real `.docx` file, in their colors, that
the reader fills in by clicking a placeholder and typing, where every claim has the engagement that
proves it sitting right behind it.

Laying out a resume is the easy half and the host already does it. What does not happen on its own
is a bullet that names what actually moved, a tailored version that re-orders real experience
instead of quietly growing a new skill, a certification left off entirely because the user never
claimed it, and a document that genuinely fits on one page on somebody else's machine. **Those
constraints are the product.**

The characteristic failure is the **brochure**: adjective soup with nothing verifiable behind it.
*Results-driven professional with a proven track record. Extensive experience in federal IT.
Excellent communication and leadership skills.* It is the same page every candidate and every firm
in the trade emits, which is how you know it says nothing about this one. It is also the
highest-probability thing this technology produces, and — unlike a layout that breaks — **it looks
finished, so it gets sent.** Step 3 exists to prevent exactly that.

The pressure is different here than in a deck or a diagram. Both of these documents are read in
under thirty seconds by someone screening dozens, scanning for a role match or a NAICS match, a
credential, and one engagement that looks like theirs. **There is no interview yet and no second
page.** Everything the document does not say is simply absent — and everything it does say is a
representation the person or the business has now made, in writing, to an employer or a federal
buyer.

## Instructions

### 1. Get what the person or firm has actually done

**One required input: the work, the employers or clients, and the outcomes in the user's own
words** — in any order, however roughly. That is all.

**A title is not a history.** *"Make me a resume, I'm a project manager"* gives you nothing to
prove. Every project manager has run projects; this one ran specific projects, and the specific ones
are the document. A title implies a plausible person; a person implies no history at all.

> What have you actually done — where, for whom, and how did it turn out? A rough list is plenty.

**IMPORTANT:** Absolutely NEVER ask about fonts, layout, paper size, section order, template style,
color, or bullet counts. Deciding those is the whole skill, and asking hands the work back. If the
user volunteers any of it, use it and say you did. Never ask for an email address, a phone number,
a street address, or a date of birth — those are `[bracketed]` slots, not questions.

Assume everything else, and **say in one line what you assumed**: the document you picked, and the
page count if they never said.

**If they actively decline** — *"just make something"*, *"you decide"* — do not keep asking

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 2 — file references are metadata, not package contents.