Brag

Memorialize something you just built by generating a self-contained "showcase" page for it — a persuasive, good-looking deep dive: what it is, why it's impressive, how it works — with a screenshot if one can be found or captured, and links to related showcase pages. This is the sales/hype-leaning counterpart to /write-post (which drafts a neutral, no-BS technical post); reach for /brag when you want it to sell. Fast by design, like /idea: ask only what's needed, build the page, don't turn it into a project. Triggers on `/brag <subject>`, "brag about this", "make a showcase page for X", "write

37 stars 7 forksWriting & Content

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add iamneilroberts/claude-skills --skill brag
Manual install
git clone --depth 1 https://github.com/iamneilroberts/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/skills/brag ~/.claude/skills/brag

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# /brag — memorialize something clever, fast

Builds one deep-dive showcase page about the subject and links it into a running index. Treat it
like `/idea`: capture quickly, ask only when blocked, never spiral into a rabbit hole.

## Output location (resolve once, up front)

- Default: a local `showcase/` directory at the repo root — `showcase/<YYYY-MM-DD>-<slug>.html`
  plus a `showcase/index.html` that lists every page.
- If the project defines a showcase/demo output another way (a `SHOWCASE_DIR` env var, a
  `showcase/.config`, or an existing `showcase/`/`demo/` dir), use that instead.
- Deploying to a live site is **optional and separate** — see step 6. Never assume a deploy target.

## Steps

1. **Take the subject.** `<subject>` is the thing being bragged about. Infer a short `slug`
   (kebab-case) and a working title from it.

2. **Clarify only if needed (0–2 questions, then stop).** Ask only when you can't build a good page
   without the answer — e.g. what makes it notable, where the code/artifact lives, or who it's for
   (a teammate vs. a public demo). Skip straight to building if context already answers these. Don't
   interview for polish.

3. **Gather the substance (read-only, quick).** Pull the concrete details the page needs:
   - `git log --oneline -10` and `git diff --stat` (and `git show` on the relevant commit) to see
     what actually changed.
   - Read the key file(s) the subject touches — enough to describe the mechanism honestly, not a
Read the full skill on GitHub

Details

Skill name
brag
Path
skills/brag/SKILL.md
Repo updated
21 August 2026

FAQ

What does the Brag skill do?

Memorialize something you just built by generating a self-contained "showcase" page for it — a persuasive, good-looking deep dive: what it is, why it's impressive, how it works — with a screenshot if one can be found or captured, and links to related showcase pages. This is the sales/hype-leaning counterpart to /write-post (which drafts a neutral, no-BS technical post); reach for /brag when you want it to sell. Fast by design, like /idea: ask only what's needed, build the page, don't turn it into a project. Triggers on `/brag <subject>`, "brag about this", "make a showcase page for X", "write

How do I install the Brag skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add iamneilroberts/claude-skills --skill brag. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Brag popular?

It lives in iamneilroberts/claude-skills, which has 37 GitHub stars and 7 forks.

Related skills

Branch

37

iamneilroberts/claude-skills

Create an isolated git worktree for a task and log it to a shared work journal, so multiple Claude Code sessions run in parallel without racing on HEAD, uncommitted edits, or the index. Subcommands: `list`, `done <slug>`, `update` (heartbeat), `coord <message>` / `coord clear <slug>` (cross-session constraints). Triggers on `/branch`, "start in a worktree", "isolate this work", "parallel session", "heartbeat the journal".

Git & Code Review

Claude Code Best Practices

37

iamneilroberts/claude-skills

Use when asked about Claude Code workflow, prompt caching cost, session economics, CLAUDE.md hygiene, context-window management, plan mode, permission modes, hooks, skills, subagents, checkpointing/rewind, parallel sessions, worktrees, headless/CI usage, the Agent SDK, slash commands, MCP configuration, or "what's the right way to use Claude Code for X". Also use proactively BEFORE suggesting /model, /compact, fast-mode toggle, or editing CLAUDE.md mid-session, since those bust the system cache.

AI, LLMs & Agents

Codex

37

iamneilroberts/claude-skills

Delegate a task or question to the OpenAI Codex CLI running as an isolated subagent, then relay its answer. Use when the user invokes /codex <prompt>, says "ask codex", "have codex look at / do X", or wants a second independent model to investigate a question or make a self-contained edit. Read-only by default; /codex --write lets Codex edit the working tree. Distinct from /codex-review, which is the structured JSON review gate — /codex is a general-purpose Codex delegate.

Software Development

Session Pause

37

iamneilroberts/claude-skills

Write a detailed session handoff file by hand so the next session can pick up where this one left off. Use when the context window is filling up, you're switching phases, or you're stopping for a break.

Writing & Content

Unity Surface Preflight

40

Nice-Wolf-Studio/unity-claude-skills

Use when about to touch a Unity project for the first time in a session; before editing any scene, prefab, or asset file in a Unity repo; when a status probe reports no instances; when more than one Editor may be running; when a command returns AMBIGUOUS_EDITOR, exit 6, or times out; when deciding between running something headless and driving an open Editor.

Writing & Content

Sitrep

37

iamneilroberts/claude-skills

Use when the user invokes /sitrep — an occasional "state of the union" re-orientation sweep. Verifies what has actually shipped versus what handoffs, specs, memory, and chat history claim shipped (across git in one or more repos, handoff docs, specs, optional chat-history/memory MCPs, and open issues), surfaces loose ends and loss-risk (unpushed commits, stale/stray worktrees & branches, unchecked plan boxes, never-closed handoff pending sections), then resets what matters next as a milestone-anchored list plus a bounded off-roadmap-drift section. Writes a report to docs/digests/ and proposes

Writing & Content

Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.