# Build an Evidence-Based Brag Document

Performance reviews are difficult when accomplishments are scattered across commits, pull requests, and personal notes. This skill organizes that evidence into a Markdown draft and marks missing outcomes for follow-up.

## Install

```bash
npx skillstore add agentkitco/brag-doc-from-git
```

## Metadata

- Status: approved
- Slug: agentkitco-brag-doc-from-git
- Version: 1.0
- Author version: 1.0
- Skillstore revision: r1
- Version status: invalid
- Tree hash: a5b60503d481de59827630c20a644dda937b15365631e6a88e843351ae3c8d70
- Author: agentkitco
- GitHub username: agentkitco
- License: MIT
- Repository: https://github.com/agentkitco/agentkit-dev-skills/tree/3de707c7875147b65ddff504d86b0d0dbf713fa7/skills/brag-doc-from-git
- Ref: 743429f75b17204d47661a86b577a575ad67517f
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands
- Quality score: 70
- Public page: https://skillstore.pages.dev/skills/agentkitco-brag-doc-from-git
- Manifest: https://skillstore.pages.dev/api/skills/agentkitco-brag-doc-from-git/manifest

## Capabilities

- Collect merged pull request metadata with GitHub CLI or author-filtered commit history with git log.
- Combine repository evidence with user-provided notes about mentoring, incidents, reviews, and other work.
- Group accomplishments by theme, preserve dates and links, and merge related follow-up items.
- Draft contribution statements, supported results, evidence links, and evidence-backed scope signals.
- Mark missing outcomes with visible gaps and finish with ranked gaps and three priority questions.
- Offer to adapt the completed document into a self-review, promotion packet outline, or resume bullets.

## Use Cases

- Prepare a Self-Review: Organize six months of engineering work into themes with supporting links and questions about missing outcomes.
- Develop a Promotion Narrative: Separate supported ownership and collaboration signals from missing evidence before preparing a promotion packet outline.
- Refresh Resume Accomplishments: Turn shipped work and supplied results into concise resume candidates without inventing metrics or overstating team contributions.

## Prompt Templates

### Start a Brag Document

```
Build my brag document for the last six months using only [owner/repository]. Restrict GitHub searches to that repository and mark missing outcomes.
```

### Use Local Git History

```
Use local Git history in [repository] for [author] since [date]. Group accomplishments by theme and include these additional notes: [notes].
```

### Prepare Promotion Evidence

```
Draft a promotion packet outline for [date range] using only [approved repositories]. Apply repository filters, separate individual contributions from team work, and rank evidence gaps.
```

### Create an Audience-Specific Draft

```
Use [approved repositories], [date range], and [verified outcomes] to draft a brag document, then adapt it into [self-review or resume bullets]. Restrict all searches to approved repositories. Exclude confidential details, preserve evidence links, and end with the three highest-value questions.
```

## Limitations

- GitHub collection requires an authenticated GitHub CLI; local history collection requires access to the relevant repositories.
- The documented GitHub query lacks repository filters and limits results to 200 pull requests; enforce scope and check completeness.
- History alone cannot establish business impact, individual credit, or work outside Git; user context is required.
- The skill produces a draft, not a verified performance assessment or guaranteed promotion outcome.

## Best Practices

- Name approved repositories and a time window; ensure every GitHub search includes repository filters before execution.
- Provide verified outcomes and notes about work outside Git, including your specific contribution to team efforts.
- Review every claim, link, and confidentiality boundary before sharing the draft.

## Anti Patterns

- Running the unfiltered GitHub search across all accessible repositories without confirming scope.
- Treating commit counts or pull request titles as proof of business impact or individual ownership.
- Replacing visible evidence gaps with invented metrics, inflated leadership claims, or unauthorized confidential details.

## Security Audit

- Audited at: 2026-10-17T19:42:43.522\+00:00
- Summary: All six static findings are false positives involving Markdown formatting, read-only history queries, or ordinary prose. The GitHub search lacks repository filters and can return private repository metadata outside the named scope, despite an explicit prohibition. No evidence found of malicious exfiltration, destructive commands, or prompt injection.

## Stats

- Views: 0
- Downloads: 0
- Favorites: 0
- Popularity score: 0