# Start Career Proof Inventory

> Builds a Career Proof Inventory from your CV and your memory, with one row per piece of past work, who saw it, what you may say in public and what stays confidential, and the three strongest proofs you choose. Use for "run start-career-proof-inventory", "turn my CV into proof", "what can I say about my old job", "I have no case studies yet", "my track record belongs to my old employer", "list my past work", "what proof do I have", part of the Claude Guide for New Founders Pack by 90n.

- Skill: `polar-bear-org/start-career-proof-inventory` (Agent Skill)
- Install (CLI): `npx get-skill add polar-bear-org/start-career-proof-inventory`
- Raw SKILL.md: https://api.skillmd.com/api/skills/polar-bear-org/start-career-proof-inventory/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: polar-bear-org (https://skillmd.com/u/polar-bear-org)
- Updated: 2026-11-14
- Page: https://skillmd.com/skills/polar-bear-org/start-career-proof-inventory

---


# Career Proof Inventory

## When To Use
Your whole track record sits inside a former employer, and you cannot say what you are allowed to point to. Run this first, before any profile, offer or message. It answers: what did I really do, what changed because of it, and which parts may I say out loud under my own name?

## When Not To Use
If you already know your proofs and need them on your profile, go to LinkedIn Experience Section. If the question is what your contract forbids, run Former Employer Terms Check; this inventory only marks what you believe is confidential.

## Inputs
- Your CV or a list of roles, with the projects you remember best in each
- What you know about confidentiality for each: your contract, a client's name, a number that was never public
- Optional: performance reviews or thank-you notes addressed to you personally
If you have none of this, I start from three pieces of work you describe from memory and mark the output as a first draft.

## Approach
Each piece of work is written as situation, task, action and result, the form university career offices teach for interviews, turned from "hire me" into "this is a problem I have solved". The judgement is in two columns most people skip: who saw the work, and what you may say about it. The failure it prevents is the founder who quotes a former employer's revenue figure in a first meeting, or the opposite, who says nothing concrete at all because everything feels confidential. Nothing here comes from a former employer's files: only your memory, your CV and papers addressed to you.

## Workflow
1. Ask at most three questions: which roles to cover, which three pieces of work you are proudest of, and whether any contract or exit paper limits what you may say.
2. Write one row per piece of work: the situation you walked into, the task that was yours, the action you personally took (not the team's), and the result. Where "we" hides your part, I ask what you did.
3. Tag each result: "mine to state" (you saw it and can stand behind it) or "would they confirm it?" (a figure only the employer holds). Figures you cannot source become words: "shorter", "fewer", "decided".
4. Add who saw it, as roles: a manager, a client sponsor, a supplier, a peer. These are the people who can vouch for the work later; nobody is assessed.
5. Mark each row: may say in public, may say in a private conversation, or stays confidential, with the reason (contract, client name, non-public number). When unsure, the row is marked "check" and stays out of public use.
6. Rewrite each public row with identifying detail removed: no client name, no figure that was never published.
7. You pick the three strongest proofs for the kind of client you want next.

## Output Format
```markdown
# Career Proof Inventory
Roles covered: [roles, years] | Prepared: [date] | Source: my CV and memory only
## Past work
| # | Situation | My task and action | Result | Mine to state? | Who saw it (roles) | May say |
|---|---|---|---|---|---|---|
| [1] | [what was happening] | [what I did] | [what changed] | [yes / would they confirm it?] | [manager, client sponsor] | [public / private / confidential: reason] |
## Public wording
- [#]: [the proof in two sentences, no client name, no unpublished figure]
## To check before use
- [#]: [what is unclear, and who could tell me]
## My three strongest proofs
1. [#]: [why it matters to the client I want]
## Decision
[Your name] confirms the three proofs and the "may say" mark on every row by [date], and takes the "check" rows to a qualified adviser or the terms check before using them.
```

## Done When
- Every row separates your own action from the team's.
- Every result is marked as yours to state or not.
- Every row has a "may say" mark with its reason.
- Three proofs are chosen by you, each in public wording.

## Quality Bar
- No number appears unless you can say where it came from and that you may use it.
- Witnesses are listed as roles who saw the work; no comment on anyone's character or performance.
- Doubt means "check", never "probably fine".
- Whether a confidentiality clause applies is a legal question: check with a qualified adviser.
- Your career from your own memory and papers, never a former employer's files; you choose the proofs and the words.

## Next
Run start-ideal-client-profile (Ideal Client Profile) to decide who these proofs are for.

## About the makers

This pack is made by 90n ([90n.ai](https://90n.ai)): AI-native ways of working and tools for Product, Marketing and HR teams, built by ex-McKinsey founders. We map where time and money leak, redesign the work around AI and stay until your people run it themselves, and we run our own company on Claude. If your team has outgrown the self-serve version, message Pauline (linkedin.com/in/paulinebertry).

