菜单
The brag nudge. Use when something real has just shipped, a PR train merged, a deploy gone live, a project delivered. Writes a brag brief and nags the human to go post about it.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
基于 SOC 职业分类
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/StuMason/skills --skill brag-nudge命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
Cheapest technique first, LLM last. Use before designing any feature that classifies, matches, routes, dedups, ranks, scores, or extracts, anything where the first instinct is "call the LLM per item". Forces enumeration of deterministic and classical-stats options, with costs and a measurement plan, before a model is allowed in.
Commit with a Conversation Decision Record. Use for every commit in repos that keep CDRs, or whenever a commit may land with no PR, no review, and no human reading the diff. Writes the decision record, stages it with the code, and adds machine-parseable provenance trailers.
Stop forwarding raw AI output to humans. Use when the session's result needs to go to another person, "summarise this for the team", "give me something to send my PM", "distill and link". Writes a short summary the sender can own and ships the full working behind one link. Never uploads the transcript.
| name | brag-nudge |
| description | The brag nudge. Use when something real has just shipped, a PR train merged, a deploy gone live, a project delivered. Writes a brag brief and nags the human to go post about it. |
The human just shipped something real. They will never tell anyone, because people who ship do not stop to market. So the agent does the thinking and the human does the human bit. Never post on their behalf. The nudge is the product.
Something real shipped: a merged PR train, a production deploy, a delivered project. One brief per shipped thing. The test for brag-worthy: would someone who might hire this person find it impressive? Devs being impressed is nice. Buyers being impressed is the point.
Write to brags/YYYY-MM-DD-<slug>.md in the project or workspace:
# Go brag: <headline of what shipped>
<Two or three sentences of nudge. Direct, cheeky, "go brag about this, mate"
energy. Say why it is impressive TO A BUYER, not to a dev.>
## Receipts
- <Verified facts only. Pull real PR counts, real dates, real features live.
Never invent a number. No metric available means a qualitative receipt.>
## Angles
- **LinkedIn (buyer frame):** <the business implication: speed, cost, risk,
delivery capacity>
- **X (peer frame):** <the technical war story or gotcha>
- **Video:** <yes or no, and the beat if yes>
## Rough draft, REWORD ME, do not post as-is
<One rough post draft in the human's voice. Deliberately rough. Editing a
wrong draft beats staring at a blank box.>
Deliver it however this environment reaches the human: a notification hook, a messaging tool, or simply ending the session with the headline and the file path in your final message. Loud beats polite.