Record your contribution separately from the team result.
Attach source pointers and mark what may be made public.
Draft a claim, then remove anything the evidence does not support.
WORKED EXAMPLE
What a useful result looks like
Fictional example: a marketer rebuilt campaign naming and a reporting checklist for a small team. The files and change log support the claim that the process was created. A shorter reporting time was discussed informally, but was not measured. Safe wording: “Created a campaign naming standard and a weekly reporting checklist used by the team.” Avoid “Cut reporting time by 50%” or attributing revenue growth to the checklist. A public case can show a blank schema and synthetic rows after permission review; it should not show account IDs or client figures. This is a teaching example, not Mark’s achievement.
Scope and compatibility
Helps structure and review evidence. Job applications, hiring outcomes and permission to publish employer material remain your responsibility.
The files are editable Markdown and CSV. The optional original plugin contains one skill for Codex; its instructions can also be used in a regular AI chat. No accounts are connected automatically.
Want help applying it?
Have Mark review one CV or portfolio case against your sources and a target role. Scope and price are agreed first.