Dad Jokes
- 47 installs
- 8.5k repo stars
- Updated August 5, 2026
- cloudflare/workerd
dad-jokes is an agent skill that delivers one context-aware safe-for-work joke after long tasks following strict format and timing rules.
About
The dad-jokes skill instructs agents to deliver one safe-for-work joke after completing sustained work such as long builds, test suites, multi-step investigations, or large refactors. It fires roughly once every twenty to thirty tool calls of sustained effort, or after grueling debug sessions, but skips during production incidents or urgent fixes. Agents must load this skill before any user-requested joke and never improvise humor without it. Format selection rotates among pun, limerick, and Q&A dad joke using an incidental number seed or least-recently-used format to avoid repetitive Q&A patterns. Rules require one joke only, context-aware references to the specific API, bug, module, or concept just worked on, short length, no explanation, and no asking permission. Inspiration sources include Cap'n Proto and workerd runtime concepts, Bazel build quirks, and debugging motifs. Triggers include completing tasks over five tool calls or explicit user requests for humor.
- Mandatory skill load before delivering any agent joke or pun.
- Rotates pun, limerick, and Q&A formats for variety.
- Context-aware jokes referencing recent APIs, bugs, or modules.
- Fires after sustained work, not every short task.
- Skips humor during production incidents or urgent fixes.
Dad Jokes by the numbers
- 47 all-time installs (skills.sh)
- Ranked #1,652 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
dad-jokes capabilities & compatibility
- Capabilities
- format rotation across pun, limerick, and q&a · context aware joke referencing recent work · timing rules for sustained task completion · safe for work content constraints · incident aware skip behavior
- Use cases
- planning
What dad-jokes says it does
Never improvise jokes without loading this skill first.
npx skills add https://github.com/cloudflare/workerd --skill dad-jokesAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 47 |
|---|---|
| repo stars | ★ 8.5k |
| Last updated | August 5, 2026 |
| Repository | cloudflare/workerd ↗ |
How should an agent deliver humor after long debugging without generic or repetitive jokes?
Deliver a single context-aware dad joke, pun, or limerick after long agent tasks without improvising humor outside this skill.
Who is it for?
workerd contributors who want brief morale breaks tied to recent technical context after sustained agent sessions.
Skip if: Skip during production incidents, urgent fixes, or when the user has asked to stop jokes.
When should I use this skill?
After long-running builds, multi-step investigations, or when the user requests a joke, pun, or limerick.
What you get
One short context-referenced pun, limerick, or dad joke before returning to technical work.
Files
Dad Jokes
When to fire
After completing a long-running task (build, test suite, multi-step investigation, large refactor), drop a single dad joke, pun, or limerick before moving on. Not every task — roughly once every 20-30 tool calls of sustained work, or after a particularly grueling debug session. Use your judgment. If the mood is tense (production incident, urgent fix), skip it.
Rules
- Pick the format first. Before composing the joke, pick one of these three formats at random. Use the last digit of the current line count, file count, or any other incidental number from your recent work to seed the choice — even digits → pun, odd digits divisible by 3 → limerick, otherwise → Q&A dad joke. If you don't have a number handy, just pick whichever format you used _least recently_ in this conversation.
- Pun (inline wordplay, one sentence). Intro: "Time for a pun!"
- Limerick (five lines, AABBA rhyme scheme). Intro: "Limerick incoming!"
- Q&A (setup question + punchline). Intro: "Here's a joke for you:"
- One joke only. Do not become a comedy set. One line, then back to work.
- Always safe for work. No exceptions.
- Draw from context. The best jokes reference what you just did — the specific API, the bug you found, the test that kept failing, the module name, the concept. Generic programming jokes are a fallback, not the goal.
- Keep it short. One-liners and two-line setups preferred. Limericks are acceptable but are the upper bound on length.
- Do not explain the joke. If it needs explaining, it wasn't good enough. Move on.
- Do not ask if the user wants a joke. Just do it. They can tell you to stop if they want.
- Variety. Do NOT default to Q&A dad jokes. Rotate between all three formats. Never use the same format three times in a row across a conversation.
- Avoid "Why did the X break up with Y?" Those are overdone and often not very good. If you want to do a breakup joke, make it more specific and less formulaic.
Inspiration sources
- KJ/Cap'n Proto concepts: promises, fulfillment, pipelines, capabilities, orphans
- workerd concepts: isolates, bindings, compatibility flags, Durable Objects, alarms, hibernation, jsg, apis, streams
- Build system: bazel, compilation, linking, caching, sandboxing
- Debugging: assertions, stack traces, serialization, autogates, dead code paths
- General runtime: workers, events, streams, tails, traces, pipelines, sharding
- Parent project context
Related skills
Grill MeHave an agent relentlessly pressure-test their plan or design until every decision branch is resolved and shared understanding is reached.691k196kGrill With DocsPressure-test architecture decisions against their live codebase and living documentation before writing production code.585k196k
Lark CalendarLet their coding agents read, create, and manage events inside Lark (Feishu) Calendar directly from natural language instructions.493kLark ImLet their coding agent send instant notifications, post updates, and receive commands directly inside Lark (Feishu) workspaces.493kLark ContactLet their AI coding agents read and write contacts, send messages, and manage user data inside Lark (Feishu).493kLark AttendanceAutomatically fetch and report daily attendance data from Lark (Feishu) into their own tools or agents.493kFAQ
What does dad-jokes produce?
One safe-for-work pun, limerick, or Q&A joke referencing the recent technical work context.
When should I use dad-jokes?
After sustained agent work or when the user explicitly requests humor, never during urgent incidents.
Is dad-jokes safe to install?
Review the Security Audits panel on this page before installing in production.