brag

Build a yearly brag document from daily recaps, PR activity, and git history.

4|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/Ni-Bu/skills --skill brag
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brag
Source: https://github.com/Ni-Bu/skills/tree/main/brag
Command: npx skills add https://github.com/Ni-Bu/skills --skill brag

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you capture meaningful accomplishments without relying on memory, turning recaps, PR activity, and case work into a structured yearly brag document for reviews and self-advocacy.

Core Features & Use Cases

  • Brag-worthy filtering: Separates real impact from routine activity so only strong, review-ready accomplishments are kept.
  • Evidence-backed entries: Pulls substance from daily recaps, PR descriptions, git history, and Monday cases to avoid vague or inflated claims.
  • Obsidian document maintenance: Appends entries into a year-based brag note with category sections, quarter grouping, summaries, and a timeline view.
  • Use Case: After a busy week, you can ask it to review your recap and add the few accomplishments that are actually worth bringing up in a performance conversation.

Quick Start

Ask the brag skill to review today’s recap and append any genuinely brag-worthy accomplishments to your yearly brag document.

Frequently Asked Questions about brag

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build a brag document from daily recaps for a performance review?

A brag document tracks career-ready accomplishments by filtering daily recaps and git history for high-signal impact. It separates real contributions from routine work, appending evidence-backed entries into a structured yearly note for performance reviews.

How do I track accomplishments in Obsidian for performance reviews?

To track accomplishments in Obsidian, append evidence-backed entries from daily recaps and PR descriptions into a year-based brag note. The skill routes this data into category sections, quarter grouping, summaries, and a timeline view for performance review preparation.

Can I use git history and pull request descriptions to backfill impact for a yearly review?

Yes, you can backfill impact across dates, ranges, quarters, and year-to-date periods by extracting substance from git history and verifying PR descriptions. This ensures your performance review contains evidence-backed accomplishments rather than vague claims.

Does this accomplishment tracking approach filter out routine pull request activity?

Yes, this accomplishment tracking approach applies brag-worthy filtering to separate real impact from routine pull request activity. It uses duplicate detection and careful filtering of low-signal work to ensure only strong, review-ready entries are kept.

How do I add Monday case data to my yearly brag document?

You add Monday case data to your yearly brag document by feeding optional Monday case information into the tracking process. The system extracts substance from these cases, appending them as evidence-backed entries grouped by category and quarter.