brag-sheet
Helps your agent turn your work into impact statements. It's useful for creating performance reports and showing your achievements.
What it does
This tool helps you turn what you did at work into evidence-backed impact statements. It retrieves your forgotten work from session logs, commits, and pull requests (PRs) to create reports for performance reviews, promotions, and weekly updates.
When to use it
- ✓Preparing for a performance review.
- ✓Writing a summary of your work for a promotion.
- ✓Logging your weekly or monthly accomplishments.
Example of what to ask your AI
“What did I do last week?”
Want more? Open the sections below.
How to use
The easiest way: copy the message below and paste it into Claude, ChatGPT, Cursor or any AI. It reads the skill and follows the instructions.
Skill link
Ready-to-paste message
How it works
The tool checks your work records (like commits and Copilot logs) to find what you did. It then organizes this information into a format that shows what you did, what the result was, and the proof (evidence) for it (like a link to a PR).
Installation
Easiest way: copy the skill link and paste it into Claude, ChatGPT or Cursor asking it to follow the instructions.
In the terminal (Claude Code, Codex, Cursor), in your project folder:
npx skills add github/awesome-copilot --skill brag-sheetOr download just the file:
curl -L https://raw.githubusercontent.com/github/awesome-copilot/main/skills/brag-sheet/SKILL.md -o SKILL.mdTechnical content (original SKILL.md)
Original text by the author, straight from GitHub.
Brag Sheet — Work Impact Writer
Turn engineering work into evidence-backed impact statements for performance reviews, self-reviews, promotion packets, and weekly updates. Uniquely mines Copilot CLI session logs, git history, and PRs to reconstruct forgotten work.
USE FOR: "brag", "log work", "what did I do", "backfill", "performance review", "self-review", "promo packet", "weekly update", "status report", "write impact statement", "what did I ship", "I forgot to log my work", "review prep", "accomplishments" DO NOT USE FOR: project management, sprint planning, time tracking, ticket creation
Quick Start
| User wants... | Mode | Output |
|---|---|---|
| Log one accomplishment | Capture | 1 impact-first entry |
| "What did I do last week?" | Backfill | Entries grouped by week, mined from git/PRs/sessions |
| Prep for review or promo | Review Pack | Entries grouped by impact theme + STAR narratives |
Agent Behavior Rules
- DO confirm the time range and scope before scanning sources. Don't assume "last week" — ask.
- DO check which tools are available (
save_to_brag_sheet,git,gh) before choosing a workflow. - DO always include all three parts: action → result → evidence. If evidence is missing, write
(evidence needed)— never silently omit. - DO show drafted entries to the user before saving. Never auto-save without confirmation.
- DO group related commits into a single entry. Ten commits on the same feature = one entry.
- DO preserve the user's voice. Reframe for impact, but don't invent accomplishments or inflate scope.
- DO NOT fabricate metrics, team sizes, or impact numbers. If the user doesn't provide a number, don't invent one.
- DO NOT write entries for work the user only described verbally without verifying. Ask: "Did this ship? Is there a PR or doc I can reference?"
- DO NOT skip the backfill scan steps or draft entries before scanning is complete.
- DO NOT pad weak periods with trivial entries. An honest gap is better than inflated fluff.
Entry Format
Every entry uses impact-first framing with three required parts:
Did [action] → [result/impact] → [evidence]
Do not output an entry unless it includes all three parts. If evidence is missing, ask for it or mark as "(evidence needed)".
Anti-Patterns
| ❌ Don't | ✅ Do instead |
|---|---|
| "Fixed a bug in auth" | "Fixed token refresh race condition → eliminated 401s affecting 12% of API calls → PR #247" |
| "Worked on dashboards" | "Built latency dashboard in Grafana → on-call detects P95 spikes in <2min → deployed to prod" |
| Invent a metric: "saved 40% of eng time" | Ask: "Do you have a rough estimate, or should I keep this qualitative?" |
| One entry per commit | Group related commits into one entry with highest-impact framing |
| Passive voice: "The pipeline was improved" | Active voice: "Built CI matrix → caught Windows-only bug before release" |
| List technologies used | State the outcome: "Migrated 4 services to IaC → deploy time 45min → 8min" |
| Silently drop weak entries | Mark (evidence needed) and present for user to fill in |
Evidence Ladder
Not every entry needs a metric. Use the strongest evidence available:
| Strength | Evidence type | Example |
|---|---|---|
| 🥇 Best | Quantified metric | "Reduced P95 latency from 800ms to 120ms" |
| 🥈 Strong | PR, commit, or doc link | "PR #312, design doc in wiki" |
| 🥉 Good | Observable outcome | "Unblocked Team X", "Resolved Sev2 incident Y" |
| ✅ Acceptable | Qualitative + context | "Reduced toil for on-call rotation — see updated runbook" |
| ⚠️ Weak | Activity only | "Worked on auth" — reframe or mark (evidence needed) |
Never invent a metric to fill the gap. Qualitative evidence with context beats fabricated numbers.
Categories
| ID | Emoji | Use for |
|---|---|---|
pr |
🚀 | Merged PRs, shipped features |
bugfix |
🐛 | Bug fixes, incident patches |
infrastructure |
🏗️ | Infra, deployments, migrations |
investigation |
🔍 | Root cause analysis, debugging |
collaboration |
🤝 | Reviews, mentoring, design discussions |
tooling |
🔧 | Dev tools, scripts, automation |
oncall |
🚨 | Incident response, on-call wins |
design |
📐 | Design docs, architecture decisions |
documentation |
📝 | Docs, runbooks, guides |
How to Help the User
Follow this decision tree:
…
FAQ
What are 'impact statements'?
These are sentences that describe what you did, the positive outcome it generated, and the proof (evidence) for it. They clearly show the value of your work.
How does the tool find my forgotten work?
It analyzes your Copilot session logs, your Git commit history, and your GitHub pull requests (PRs) to reconstruct what you accomplished.
Can I use this for project management?
No, this tool is only for recording and presenting work you HAVE ALREADY done, not for planning or managing future tasks.
Details
Original description by the author
Turn vague "what did I do?" into evidence-backed impact statements for performance reviews, self-reviews, promotion packets, and weekly updates. Uniquely mines Copilot CLI session logs to reconstruct forgotten work, plus git commits and GitHub PRs. Enforces a 3-part impact contract (action → result → evidence). Works standalone with zero dependencies. Trigger for: "brag", "log work", "what did I d
repo: github/awesome-copilot
Popularity
- GitHub stars
- 40k
- Ranking position
- #5038
- License
- MIT
- Updated
- 10/15/2026
Comments
- …
More skills from this repository
acquire-codebase-knowledge
Helps your agent understand and document an existing code project. It's useful for onboarding new people or getting an overview of the architecture.
github/awesome-copilot
acreadiness-assess
Enables your agent to assess a project's readiness for AI and generate a report. It's useful for understanding how well a project is prepared to use AI tools.
github/awesome-copilot
acreadiness-generate-instructions
Helps your agent create instructions for AI tools based on an assessment. It's useful for improving how AI interacts with code and closing identified gaps.
github/awesome-copilot
acreadiness-policy
Enables your agent to help define or apply policies for AI project assessment. It's useful for standardizing how projects are evaluated and ensuring compliance.
github/awesome-copilot
Similar skills
intent-driven-development
Helps your agent turn ideas into clear, testable plans. Defines criteria to ensure changes are made correctly and safely.
affaan-m/ECC
product-capability
Guides your agent in turning product ideas into clear plans. It defines what needs to be done, the limits, and decisions before development.
affaan-m/ECC
article-writing
Writes long-form content like articles, guides, and blog posts with a unique style. It's useful when you need well-written texts with a consistent voice and credibility.
affaan-m/ECC