New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Official agent skill

Brag Sheet

by github in github/awesome-copilot

Turn vague "what did I do?" into evidence-backed impact statements for performance reviews, self-reviews, promotion packets, and weekly updates.

OfficialMITAuto-check passedBusiness, Finance & HR

Install Brag Sheet

skills CLI
$ npx skills add github/awesome-copilot --skill brag-sheet -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install github/awesome-copilot brag-sheet --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/brag-sheet .claude/skills/brag-sheet && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
brag-sheet
GitHub stars
40k
Used in
1 other repo
Token cost
~3k tokens
SKILL.md length
1,336 words
Files
1
Skills in repo
417
Repo updated
First seen
Licence
MIT

At a glance

Turn vague "what did I do?" into evidence-backed impact statements for performance reviews, self-reviews, promotion packets, and weekly updates.

  • Works in 5 steps: Scan available sources → Group related work → Draft entries → …
  • Backfill my work history
  • SKILL.md covers Quick Start, Agent Behavior Rules, Entry Format and Evidence Ladder, plus 7 more sections
  • Calls git and gh

What it does

Brag Sheet is an agent skill from github/awesome-copilot, published by the product's own GitHub organization. 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 do", "backfill my work history", "performance review", "self-review", "self assessment", "write impact statement"…

Its SKILL.md is about 3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: Cross-platform (Windows, macOS, Linux). Works with any GitHub Copilot CLI session. Optional: git, gh CLI.

It sits in Business, Finance & HR, covering Internal communications, Performance reviews and Commit messages. It works with GitHub. The repository describes itself as: Community-contributed instructions, agents, skills, and configurations to help you make the most of GitHub Copilot. The licence is MIT.

When your agent uses it

  • Backfill my work history
  • Performance review
  • Self assessment
  • Write impact statement

Example prompts

  • “what did I do?”
  • “log work”
  • “what did I do”
  • “/brag-sheet”

Requirements

  • Compatibility (from SKILL.md): Cross-platform (Windows, macOS, Linux). Works with any GitHub Copilot CLI session. Optional: git, gh CLI.

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Scan available sources
  2. Group related work
  3. Draft entries
  4. Present and refine
  5. Output

What it can do on your machine

Read from SKILL.md and the folder at commit 727ff2e. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git
    • gh

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • github.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Cross-platform (Windows, macOS, Linux). Works with any GitHub Copilot CLI session. Optional: git, gh CLI.

    From compatibility in the SKILL.md frontmatter.

Context cost

Brag Sheet loads about 3k tokens when it runs. Until then it costs about 215 tokens; SKILL.md has 1,336 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~215
When it runs · the whole SKILL.md, loaded when a task matches
~3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from github/awesome-copilot at commit 727ff2e, republished under its MIT licence (© github). 1,336 words, ~2,959 tokens.

Download SKILL.mdSave it as .claude/skills/brag-sheet/SKILL.md (or your agent's skills folder).
name
brag-sheet
description
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 do", "backfill my work history", "performance review", "self-review", "self assessment", "write impact statement", "review prep", "promo packet", "promotion case", "weekly update", "status report", "accomplishments", "what did I ship", "I forgot to log my work", "summarize my work", "track my wins", "what should I highlight", "end of half", "career growth", "work journal", or any request to document, summarize, or organize work accomplishments.
compatibility
Cross-platform (Windows, macOS, Linux). Works with any GitHub Copilot CLI session. Optional: git, gh CLI.
license
MIT
metadata.version
1.1
argument-hint
Optional: time range ("last 2 weeks", "this half"), category ("infrastructure"), "backfill", or "review prep"

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...ModeOutput
Log one accomplishmentCapture1 impact-first entry
"What did I do last week?"BackfillEntries grouped by week, mined from git/PRs/sessions
Prep for review or promoReview PackEntries grouped by impact theme + STAR narratives

Agent Behavior Rules

  1. DO confirm the time range and scope before scanning sources. Don't assume "last week" — ask.
  2. DO check which tools are available (save_to_brag_sheet, git, gh) before choosing a workflow.
  3. DO always include all three parts: action → result → evidence. If evidence is missing, write (evidence needed) — never silently omit.
  4. DO show drafted entries to the user before saving. Never auto-save without confirmation.
  5. DO group related commits into a single entry. Ten commits on the same feature = one entry.
  6. DO preserve the user's voice. Reframe for impact, but don't invent accomplishments or inflate scope.
  7. DO NOT fabricate metrics, team sizes, or impact numbers. If the user doesn't provide a number, don't invent one.
  8. 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?"
  9. DO NOT skip the backfill scan steps or draft entries before scanning is complete.
  10. 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 commitGroup 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 usedState the outcome: "Migrated 4 services to IaC → deploy time 45min → 8min"
Silently drop weak entriesMark (evidence needed) and present for user to fill in

Evidence Ladder

Not every entry needs a metric. Use the strongest evidence available:

StrengthEvidence typeExample
🥇 BestQuantified metric"Reduced P95 latency from 800ms to 120ms"
🥈 StrongPR, commit, or doc link"PR #312, design doc in wiki"
🥉 GoodObservable outcome"Unblocked Team X", "Resolved Sev2 incident Y"
✅ AcceptableQualitative + context"Reduced toil for on-call rotation — see updated runbook"
⚠️ WeakActivity 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

IDEmojiUse 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:

  1. If save_to_brag_sheet tool is available → use extension tools directly (save_to_brag_sheet, review_brag_sheet, generate_work_log). Do not reference or attempt to call these tools unless they are confirmed available.

  2. If git or gh CLI is available → backfill from commits and PRs (see Backfill section below)

  3. Otherwise → guided interview: "What did you work on?", "Who benefited?", "What's the evidence?"

For each entry, walk through: What (the deliverable) → Why (who benefits) → Evidence (PR, metric, link). Output formatted markdown the user can paste into a review doc.

Backfill Workflow

When the user asks "what did I do last week" or "backfill my history":

Follow these steps in order. Do not draft entries until scanning is complete.

Step 1: Scan available sources

Check what's available, then mine each source:

bash
git --version 2>/dev/null         # for commit mining
gh --version 2>/dev/null          # for PR mining
ls ~/.copilot/session-state/ 2>/dev/null  # Copilot session logs

Git commits — recent commits by the user in the current repo:

bash
git log --author="$(git config user.email)" --since="2 weeks ago" \
  --pretty=format:'%h|%ad|%s' --date=short --no-merges

PR history — merged PRs across repos:

bash
gh pr list --author @me --state merged --limit 20 \
  --json number,title,repository,mergedAt

Copilot session history (unique to this skill):

  • Path: ~/.copilot/session-state/<session-id>/workspace.yaml
  • Read fields: summary, cwd, repository, branch
  • Skip sessions without a summary field
  • Note: this directory may not exist on all machines

If none of these sources are available, fall back to the guided interview.

Show full SKILL.md (553 more words)Show less

Cluster related signals into one entry:

  • Same PR + its commits → 1 entry
  • Multiple commits on the same file/feature within 3 days → 1 entry
  • Copilot sessions referencing the same repo + branch → merge into PR entry if one exists
Step 3: Draft entries

Write impact-first entries for each group. Assign categories.

Step 4: Present and refine

Show all drafted entries to the user. Adjust based on feedback.

Step 5: Output

Format as markdown grouped by week:

markdown
## Week of 2025-04-14

### 🚀 PRs & Features
- **Migrated auth service to managed identity** → eliminated 3 secret rotation incidents/quarter → PR #312

### 🏗️ Infrastructure
- **Built CI pipeline for copilot-brag-sheet** → 107 tests across 3 OSes × 3 Node versions → shipped v1.0.0

Performance Review Prep

When the user is preparing for a performance review (Connect, annual review, etc.):

Structure
  1. Gather — collect entries from the work log (or backfill using the workflow above)
  2. Select — pick the top 3–5 highest-impact items
  3. Rewrite each item with three parts:
    • What I did — the specific action
    • Why it mattered — who benefited, what changed
    • Proof — PR number, metric delta, dashboard link, customer outcome
  4. Organize by impact theme (not chronologically):
    • Delivering results / operational excellence
    • Customer / team impact
    • Collaboration / mentoring / leadership
    • Growth / learning
  5. Ask for gaps — if evidence is missing, prompt the user: "What metric changed?", "Who was unblocked?", "What's the PR or incident ID?"
Strong vs weak entries
✅ Strong❌ Weak
Outcome-first, quantifiedActivity list ("worked on X")
Tied to customer/team impactNo beneficiary mentioned
Includes evidence (PR, metric)No measurable result
Shows ownership or leadershipPure task completion
Narrative format

For longer narrative sections, use STAR: Situation → Task → Action → Result.

For Microsoft employees using the Connect preset, frame entries around Core Priorities: delivering results, customer obsession, teamwork, and growth mindset.

Output Contract

Before finishing, ensure:

  1. Every entry has action → result → evidence (mark (evidence needed) if missing)
  2. No fabricated metrics — only user-provided or source-verified data
  3. Entries shown to user before saving
  4. Time range explicitly stated
  5. Output is pasteable markdown with categories assigned

Gotchas

No recent commits in the current repo

The user may work across multiple repos. Before concluding there's nothing to backfill:

  1. Ask if they want to scan a different repo or branch
  2. Check gh pr list --author @me --state merged for cross-repo PRs
  3. Fall back to the guided interview — not all impactful work leaves git traces (design docs, incident response, mentoring)
Review period doesn't match git history

Performance reviews often cover 6–12 months. Explicitly set the date range:

bash
git log --author="$(git config user.name)" --since="2024-07-01" --until="2025-01-01" --oneline

PR history (gh pr list --state merged) is more reliable for long time ranges than commit logs.

User can't quantify impact

Not every entry needs a number. See the Evidence Ladder above. Acceptable evidence includes PR links, "unblocked Team X", or qualitative outcomes with context. Never invent a metric to fill the gap.

Copilot session directory doesn't exist

~/.copilot/session-state/ only exists if the user has run Copilot CLI sessions. Don't error — silently skip and note: "No Copilot session history found; scanning git and PRs only."

"brag" might mean something else

The user might say "brag about this feature to my team" (a launch announcement, not a work entry). Confirm intent if ambiguous.

Pair programming or co-authored commits

If multiple authors appear on the same commits, ask: "Should I credit this as your work, shared work, or skip it?"

Automatic Session Tracking (Optional)

For automatic background tracking of every Copilot CLI session (files edited, PRs created, git actions), install the copilot-brag-sheet extension. It adds save_to_brag_sheet, review_brag_sheet, and generate_work_log tools to every session.

© github, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/brag-sheet of github/awesome-copilot.

Open the folder on GitHubat commit 727ff2e

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in github/awesome-copilot, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Brag Sheet next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Brag Sheet compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Brag Sheet this skillgithub/awesome-copilot40k1 repos~3kAutomated safety check: PassMIT
Engineering Manager ToolkitFerroxLabs/wayland608—~4.6kAutomated safety check: PassApache-2.0
PR Finalize Reviewmicrosoft/garnet12k—~3.1kAutomated safety check: PassMIT
React Router Pull Request Creatorremix-run/react-router57k—~2.5kAutomated safety check: PassMIT
Verdaccio Pull Request Workflowverdaccio/verdaccio18k—~1.9kAutomated safety check: PassMIT
Gh PR Metadatamodule-federation/core2.7k—~1kAutomated safety check: PassMIT

Similar skills

  • Engineering Manager Toolkit

    FerroxLabs/wayland

    Engineering management practices covering one-on-one meetings, performance reviews, team building, hiring, conflict resolution, career development frameworks, sprint planning, technical debt…

    608 GitHub stars~4.6k tokensUpdated yesterday
    Business, Finance & HRAuto-check passed

  • PR Finalize Review

    microsoft/garnet

    Official

    Checks that a pull request's title and description match its implementation and reviews the code for Garnet best practices, reporting findings without posting them.

    12k GitHub stars~3.1k tokensUpdated today
    DevelopmentAuto-check passed

  • React Router Pull Request Creator

    remix-run/react-router

    Packages finished React Router work into a draft pull request: branch, commit, push, a written PR body and the right GitHub labels.

    57k GitHub stars~2.5k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Verdaccio Pull Request Workflow

    verdaccio/verdaccio

    Takes a change through a verdaccio pull request: branch, local checks, changeset, title and body, labels, CI and review rounds, and ports to other release lines.

    18k GitHub stars~1.9k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Gh PR Metadata

    module-federation/core

    Update the current GitHub PR title and body for this repository so they match the repo's pull request template and conventional-commit title style.

    2.7k GitHub stars~1k tokensUpdated today
    DevelopmentAuto-check passed

  • Draft Pull Request Creator

    wordpress-mobile/WordPress-Android

    Commits and pushes current changes, writes a pull request title and body from the branch history and template, and opens a draft PR on GitHub after you approve it.

    3.2k GitHub stars~881 tokensUpdated today
    DevelopmentAuto-check: notes

More from github/awesome-copilot

All 417 skills in this repo

  • Acquire Codebase Knowledge

    github/awesome-copilot

    Official

    Maps an unfamiliar codebase into seven evidence-backed documents in docs/codebase/, using a scan script and templates, for onboarding or architecture write-ups.

    40k GitHub starsUsed in 1 repo~2.3k tokens
    Auto-check passed

  • Azure Architecture Autopilot

    github/awesome-copilot

    Official

    Designs Azure infrastructure from a natural-language description, or diagrams an existing resource group, then refines the design through conversation and deploys it with Bicep.

    40k GitHub starsUsed in 1 repo~1.9k tokens
    Auto-check passed

  • Draw.io Diagram Generator

    github/awesome-copilot

    Official

    Generates, edits and validates draw.io files with correct mxGraph XML, covering flowcharts, architecture, sequence, ER and UML class diagrams.

    40k GitHub starsUsed in 1 repo~4.9k tokens
    Auto-check passed

  • Credit Risk Data Cleaning

    github/awesome-copilot

    Official

    Cleans raw credit data and screens variables before loan modeling, dropping unstable, noisy or redundant features and writing an Excel report of every step.

    40k GitHub starsUsed in 1 repo~1.5k tokens
    Auto-check passed

  • Daily Focus Board

    github/awesome-copilot

    Official

    Builds a warm, browser-based daily focus board the user updates by talking to their agent, with Eisenhower priorities, a brain-dump box and kind not-today carryover.

    40k GitHub stars~3k tokensUpdated today
    Auto-check passed

  • Python Pypi Package Builder

    github/awesome-copilot

    Official

    End-to-end skill for building, testing, linting, versioning, and publishing a production-grade Python library to PyPI.

    40k GitHub starsUsed in 1 repo~4.6k tokens
    Auto-check passed

Works with

Categories

Questions about Brag Sheet

What does Brag Sheet do?

Turn vague "what did I do?" into evidence-backed impact statements for performance reviews, self-reviews, promotion packets, and weekly updates. Brag Sheet is an agent skill from github/awesome-copilot, published by the product's own GitHub organization." into evidence-backed impact statements for performance reviews, self-reviews, promotion packets, and weekly updates.

When should I use Brag Sheet?

Brag Sheet fits situations like: backfill my work history; performance review; self assessment; write impact statement.

How do I install Brag Sheet in Claude Code?

Run `npx skills add github/awesome-copilot --skill brag-sheet -a claude-code`. Or copy the skill folder (skills/brag-sheet in github/awesome-copilot) into .claude/skills/brag-sheet in your project. Claude Code loads it when a task matches its description.

How do I install Brag Sheet in Codex?

Run `npx skills add github/awesome-copilot --skill brag-sheet -a codex`. Or copy the skill folder (skills/brag-sheet in github/awesome-copilot) into .agents/skills/brag-sheet in your project. Codex loads it when a task matches its description.

Can I use Brag Sheet in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add github/awesome-copilot --skill brag-sheet -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/brag-sheet, .gemini/skills/brag-sheet, .github/skills/brag-sheet and .opencode/skills/brag-sheet in your project.

What does Brag Sheet need to run?

Going by SKILL.md and its folder, Brag Sheet needs the command-line tools its instructions call (git and gh). Compatibility (from SKILL.md): Cross-platform (Windows, macOS, Linux). Works with any GitHub Copilot CLI session. Optional: git, gh CLI..

Does Brag Sheet access the network?

SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.

Is Brag Sheet safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Brag Sheet use?

Brag Sheet is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Brag Sheet use?

About 3k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Brag Sheet?

Skills that share tags, products or a category with Brag Sheet: Engineering Manager Toolkit (FerroxLabs/wayland, 608 stars), PR Finalize Review (microsoft/garnet, 12k stars), React Router Pull Request Creator (remix-run/react-router, 57k stars) and Verdaccio Pull Request Workflow (verdaccio/verdaccio, 18k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Brag Sheet?

github (a GitHub organization, an official publisher) maintains it in github/awesome-copilot, which has 39,748 GitHub stars. The repository holds 417 skills in this directory. The repository was last updated on October 7, 2026.

Source: github/awesome-copilot on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.