Documents & Data · IN-DEPTH PROFILE

brag-sheet

Evidence-backed impact statements reconstructed from work history without invented metrics.

Best for

Knowledge workers preparing performance or promotion evidence

What you get

Capture one accomplishment + Backfill work history

Main limitation

Local logs and repository history cannot capture unrecorded collaboration or business outcomes.

First risk

Sensitive work history aggregation. Combining sessions, commits, pull requests, incidents, and metrics creates a concentrated profile of internal work. Confirm scope, redact confidential details, and obtain approval before saving or sharing.

EVIDENCE FRESHNESS

Three checks, kept separate

A recent source check is not a runtime test or security audit.

Upstream sourceChecked 2026-08-20

Pinned revision · 318066d2

Open pinned commit
SkillSignal profileEditorial metadata

Updated 2026-08-20

Runtime & securityNot independently verified

Source review does not certify behavior or safety.

30-SECOND BRIEF

What it does—and when it fits

Brag Sheet is a GitHub Awesome Copilot workflow for reconstructing work and turning it into evidence-backed impact statements for weekly updates, self-reviews, and promotion packets. It can mine Copilot sessions, git commits, and GitHub pull requests while forbidding invented metrics.

INSTALL BY AGENT

Choose your Agent

Paths come from official Agent docs or the universal installer behind skills.sh. Compatibility still follows this Skill's record.

Native

This Skill's current record explicitly names this Agent. Still inspect scripts, permissions, and external dependencies first.

Project scope.agents/skills/brag-sheet/
Personal scope~/.copilot/skills/brag-sheet/

Use project scope for team sharing and personal scope across repositories. The installer defaults to project scope; add -g for personal scope.

Install command (project scope)npx skills add github/awesome-copilot --skill brag-sheet --agent github-copilot
Official agent docs

Copilot also accepts .github/skills and .claude/skills at project scope. Preview untrusted Skills before enabling scripts.

View path evidence

TYPICAL WORKFLOW

A practical workflow

01

Capture one accomplishment

Frame action, result, and evidence in one impact-first entry.

02

Backfill work history

Group related sessions, commits, and pull requests by week and outcome.

03

Prepare a review pack

Select strong entries and organize them by impact theme or STAR narrative.

THE TRADEOFFS

Advantages and tradeoffs

Notable strengths

  1. Requires action, result, and evidence for every accomplishment.
  2. Groups related technical activity into outcome-level entries instead of commit lists.

Limitations

  1. Local logs and repository history cannot capture unrecorded collaboration or business outcomes.
  2. Impact still needs user confirmation; qualitative evidence may remain incomplete.

BEST FIT

Who it is for

Knowledge workers preparing performance or promotion evidence

Developers reconstructing recent accomplishments from technical traces

BEFORE YOU USE IT

Risks to review before use

High

Sensitive work history aggregation

Combining sessions, commits, pull requests, incidents, and metrics creates a concentrated profile of internal work. Confirm scope, redact confidential details, and obtain approval before saving or sharing.

SECURITY

What the permission profile means

  • Do not scan unrelated repositories or time periods without consent.
  • Never invent metrics, team sizes, or shipped status.

Not a security certification. External ratings are attributed references. SkillSignal has not independently executed or security-reviewed this Skill.

INSIDE THE PACKAGE

Indexed files

SKILL.mdUpstream package contentSource-linked

TAGS

performance-reviewwork-journalimpact

Original SkillSignal editorial profile grounded in GitHub Awesome Copilot commit 318066d2, checked 2026-08-20; not independently executed or security-certified.