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

brag-doc

Keep a running brag document of your accomplishments so reviews and promo cases write themselves. Use when asked to start or update a brag doc, log a win, track accomplishments, or prep evidence for a review/promotion. Produces a structured, dated accomplishment log — impact-first entries with metrics, scope, and the evidence link — grouped so it drops straight into a self-review or promo packet.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md3.5 KB

SKILL.md(原文)

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

Brag Doc Skill

Nobody remembers in December what they shipped in March — so good work goes uncredited at review time. A brag doc is the fix: a running, dated log of what you did and the impact it had, captured while it's fresh. This skill turns a pile of "stuff I did" into impact-first entries you can paste straight into a self-review or promotion-packet.

Required Inputs

Ask for these only if they aren't already provided:

  • The win(s) — what you did (rough notes are fine; the skill structures them).
  • Impact — the outcome and any metric (before → after, time saved, revenue, users) — even a rough one.
  • Scope & role — your specific contribution vs. the team's, and who it affected.
  • Date / period and any evidence (PR, doc, dashboard, kudos, ticket link).

Output Format

Brag Doc — [your name], [period]

Entries newest-first, grouped by theme (or quarter). Each entry is impact-first:

[Verb-led headline — the outcome, not the task] · [date]

  • What I did: [the specific action and your role in it]
  • Impact: [metric / outcome — before → after where possible]
  • Scope: [who/what it affected — team, org, customers]
  • Evidence: [link]
  • Maps to: [the competency / ladder level it demonstrates — e.g. "cross-team influence"]

Example:

Cut onboarding drop-off 18% → 9%, unlocking ~$140k ARR · Mar 2026

  • What I did: led the redesign of the 3-step signup flow; wrote the PRD, drove eng + design alignment.
  • Impact: activation 41% → 52%; drop-off halved (measured over 6 wks, 20k users).
  • Scope: owned end-to-end; affected all new signups.
  • Evidence: [PRD] · [dashboard]
  • Maps to: drives measurable product outcomes; cross-functional leadership.

End with a "Themes this period" summary — the 3–4 narrative threads your wins ladder up to.

Quality Checks

  • Every entry leads with impact/outcome, not the activity
  • Metrics include the baseline (before → after), not a bare percentage
  • Your specific contribution is distinguished from the team's
  • Each entry links real evidence
  • Entries are tagged to a competency/ladder level, so the doc feeds a review or promo case directly

Anti-Patterns

  • Do not log tasks ("attended planning", "wrote code") — log outcomes ("shipped X, which moved Y")
  • Do not wait until review season — capture wins within a week, while the metrics and context are fresh
  • Do not inflate or claim team wins as solo — overstated credit is worse than none when a manager checks
  • Do not omit the metric because it's imperfect — a rough, labelled estimate beats "improved things"
  • Do not bury the evidence — an unlinked claim is one a busy manager can't verify or champion

Based On

Brag-document practice (Julia Evans) and impact-first accomplishment tracking.

Example Trigger Phrases

  • "Update a brag doc."
  • "Log a win."
  • "Track accomplishments."
  • "Prep evidence for a review/promotion."

レビュー

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

同じリポジトリのスキル

概要と使いどころ

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 のスキルをすべて見る

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