メニュー
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 に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/StuMason/skills --skill brag-nudgeコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
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.
SOC 職業分類に基づく
SKILL.md を表示中
| 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.