本文へ移動
cccskills
無料GitHub で公開

career-inventory

Interview someone about their working life and turn the answers into a master CV inventory: every role, project and achievement with real numbers, before any CV is tailored. Use when asked to build my master CV, get my experience down properly, I don't know what to put on my CV, or as the first step before a tailored CV. Produces a structured inventory of roles, achievements in a fixed shape with evidence and numbers, skills with proof, and a list of gaps to fill. Never invents a number.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md4.3 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Career Inventory

Most weak CVs are weak at the input, not the writing. People remember duties, not results, and they undersell the numbers they do know. This skill interviews the person, one role at a time, and builds a master inventory that every tailored CV is cut from.

First step of the pm-cv bundle. company-tailored-cv and the format skills read its output.

What This Skill Produces

  • A master inventory: every role with dates, scope and the achievements inside it
  • Achievements in one shape: what changed, how much, by what action, with what evidence
  • Skills with proof: each skill tied to a place it was used, not a bare keyword list
  • A gaps list: the numbers and facts the person could find out but has not yet
  • A saved file (career-inventory.md) so the interview never has to be repeated

Required Inputs

Ask for these if not provided:

  • What exists already: an old CV, a LinkedIn export, or nothing
  • The roles to cover: start with the last ten years unless the person says otherwise
  • Whether it is for a change of direction, which changes what is worth probing

Framework: The Interview

Work one role at a time, newest first. For each role ask, in this order:

  1. Scope: team size, budget, users, revenue or volume you were responsible for
  2. The before: what was broken, slow, missing or risky when you arrived
  3. What you did: the decisions and actions that were yours, not the team's
  4. The after: what changed, and how anyone could tell
  5. The number: if there is one. If not, ask for the nearest honest proxy (time saved, count, percentage, rank, before and after)
  6. The evidence: a document, a dashboard, a quote, an award, a reference

Probing rules:

  • Ask "how do you know?" once per claimed result. It turns adjectives into evidence.
  • Accept "I don't know the number". Record it in the gaps list with where to find it.
  • Separate "I" from "we". Both are allowed on a CV; the person must know which is which.
  • One achievement per answer. Split compound answers.

Achievement shape: [Result, with number] by [action you took], [context or constraint]. Evidence: [source].

Output Format

Career inventory: [name], updated [date]

Role: [title], [organisation], [start] to [end]

  • Scope: [team, budget, users, volume]
  • Achievements:
    1. [achievement in the shape above] · Evidence: [source] · Confidence: confirmed / estimated / to find
  • Skills used here: [skill, with the achievement number it proves]

(repeat per role)

Skills index: | Skill | Proven in | Strongest example |

Gaps to fill: | Fact needed | Role | Where to find it |

Next step: "Run company-tailored-cv with this inventory and the job you are applying for."

Quality Checks

  • Every achievement has an action the person personally took
  • Every number is marked confirmed, estimated or to find
  • No number appears that the person did not give
  • Each skill in the index points to at least one achievement
  • The gaps list exists, even if short

Anti-Patterns

  • Inventing or rounding up numbers. An estimate is labelled as an estimate. A missing number goes in the gaps list.
  • Recording duties. "Responsible for reporting" is a job description, not an achievement. Ask what changed.
  • Interviewing all roles at once. One role at a time gets detail; a wall of questions gets summaries.
  • Tailoring too early. The inventory is complete and neutral. Tailoring happens later, per job.
  • Flattery. Accurate is more useful than impressive. An interviewer will test every line.

Example Trigger Phrases

  • "Help me get all my experience down before I write a CV."
  • "I never know what to put on my CV. Interview me."
  • "Build my master CV from my old one and LinkedIn."
  • "I am changing careers. What have I actually achieved?"

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Design a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.

日本語の概要は準備中です。原文の説明を表示しています。

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

Decode a 401k or workplace retirement plan — the real cost of its funds, the match's fine print, vesting math, and the plan features worth using or avoiding. Use when someone asks 'is my 401k any good', 'decode my 401k plan', 'which funds should I look at', or 'what fees am I paying'. Produces a fee decode in dollars-over-time, match and vesting math, a fund-lineup triage by cost, and the questions for HR or the plan administrator.

日本語の概要は準備中です。原文の説明を表示しています。

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

Design statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.

日本語の概要は準備中です。原文の説明を表示しています。

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

Analyse a finished A/B test and write the readout — the result, whether it's statistically and practically significant, what it means, and the ship/no-ship call. Use when asked to analyse experiment results, write an A/B test readout, interpret test data, or decide whether to ship a variant. Produces a clear verdict with the lift and confidence, segment cuts, the risks (peeking, novelty, sample), and a recommendation. Distinct from planning a test — this reads results.

日本語の概要は準備中です。原文の説明を表示しています。

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

Build or tailor an academic CV for faculty, postdoc, research or fellowship applications: publications, grants, teaching, supervision and service in the order the field expects, with consistent citations. Use when asked to write my academic CV, update my CV for a lectureship, tenure-track or postdoc application, format my publications list, or adapt my academic CV for an industry research role. Produces the full academic CV, a field-appropriate section order, a clean publications list in one citation style, and a two-page summary version when asked.

日本語の概要は準備中です。原文の説明を表示しています。

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

Generate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.

日本語の概要は準備中です。原文の説明を表示しています。

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

mohitagw15856 のスキルをすべて見る

このスキルの問題を報告する