diff --git a/disclose-gen-ai/SKILL.md b/disclose-gen-ai/SKILL.md index a54da46..bc1bf51 100644 --- a/disclose-gen-ai/SKILL.md +++ b/disclose-gen-ai/SKILL.md @@ -34,9 +34,9 @@ Generated-by: Claude Opus 5.5 trailer only on those commits. Don't add it to every commit. - **PR descriptions:** say which parts were AI-generated. The commit trailers stay the record that counts. -- **Unreviewed PRs are drafts.** When an agent opens a PR the human - hasn't read yet, open it as a draft (`gh pr create --draft`) and - start the description with: +- **Unreviewed PRs are drafts.** When an agent opens a PR under the + human's GitHub account and the human hasn't read it yet, open it as + a draft (`gh pr create --draft`) and start the description with: ``` > [!WARNING] @@ -45,6 +45,9 @@ Generated-by: Claude Opus 5.5 ``` The human removes the caveat and marks it ready after reviewing. + The caveat exists because the PR appears to come from the human. + A PR opened from a bot account already shows who wrote it, so it + doesn't need the caveat. - **The human stays responsible.** The commit author vouches for the contribution. That includes disclosing material that is not their original creation, and making sure the tool's terms grant enough diff --git a/hackmd-deck/SKILL.md b/hackmd-deck/SKILL.md index c4e91d2..4289fe4 100644 --- a/hackmd-deck/SKILL.md +++ b/hackmd-deck/SKILL.md @@ -1,6 +1,6 @@ --- name: hackmd-deck -description: HackMD slide deck for a light talk — use when asked to draft slides, a deck, or a talk for show & tell, office hours, or a demo; when someone says "hackmd deck", "whip up some slides", or names a talk title and points at work to present (repos, git history, session transcripts). Covers the flashback story arc, emoji retro tags, and real artifacts as eye candy. Not for .pptx files or polished conference talks. +description: HackMD slide deck for a light talk — use when asked to draft slides, a deck, or a talk for show & tell, office hours, or a demo; when someone says "hackmd deck", "whip up some slides", or names a talk title and points at work to present (repos, git history, session transcripts). Covers the flashback story arc, emoji markers for wins and friction, and real artifacts as eye candy. Not for .pptx files or polished conference talks. --- # HackMD deck @@ -32,19 +32,11 @@ A talk at something like Agoric's engineering show & tell: "Presentations should ## Problem -**A deck has to hook the room and carry a technical story in a few minutes, without hours of prep.** - -## Forces - -- A TADA from a side thread leaves the audience waiting for a payoff that never comes. -- Designed, built in dev, and deployed look alike on a slide. -- Real code and real output convince; paraphrase doesn't. -- Every slide costs attention ([grice-maxims](../grice-maxims/SKILL.md)). -- Images in a repo don't show up in HackMD until uploaded. +**I have done a bunch of stuff I think is interesting, but I can't justify the time to make a polished presentation.** ## Therefore -**Tell it as a flashback, built from real artifacts, with emoji tags that add up to a retro.** +**Let an agent do a quick-n-dirty one: a flashback, built from the record.** The arc: @@ -55,13 +47,13 @@ The arc: Ground every slide in the record: quote code and test output verbatim (trim with `...`), check claims against the code and git history, and mark what's only designed or not deployed with ⏳. -Tag slides and bullets as you go; the last slide gathers them: +Mark wins, losses, challenges, and friction with emojis: visually appealing, intuitive at a glance. -- wins: 🎉 the TADA · ✅ shipped · ✨ insight · 🙌 help, or a gift from someone else's work -- friction and follow-ups: ⏳ delays, not yet · 🧰 fragile tooling, ceremony · 💤 silent failures · 📘 docs · 🔔 alerts · 📈 observability · 🪄 surprises · 🔧 fixes owed · 🧱 walls +- wins: 🎉 the TADA · ✅ shipped · ✨ sparkle, delight · 💡 aha: now I see how to address the issue · 🙌 help, or a gift from someone else's work +- friction and follow-ups: ⏳ delays, not yet · 🧰 fragile tooling, ceremony · 💤 silent failures · 📘 docs · 🔔 alerts · 📈 observability · 🪄 a wish, often one a problem brings to mind · 🔧 fixes owed · 🧱 walls Write the deck in the repo the talk is about (e.g. `docs/-slides.md`), images beside it, and commit it. ## Resulting context -The deck takes an hour, not a day, and the retro slide doubles as a to-do list. The user pastes it into HackMD and uploads the images. +The deck takes 15 minutes: the agent spends 5, the presenter polishes for 10. The user pastes it into HackMD and uploads the images.