Menu
Generate an original, clean joke on demand. Use when the user asks for a joke, wants something funny, or says they need cheering up.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Cut a new yolop release. Prepares the release PR, runs publish-readiness checks, monitors CI publish to crates.io and the everruns Homebrew tap. Use when the user asks to release, cut a version, publish, or ship to crates.io / brew.
Write effective ast-grep patterns for the built-in `ast_grep` structural-search tool. Use when searching code by shape rather than text — call expressions, function/struct declarations, wrappers, imports — or when `grep_files` is too noisy, and when a pattern returns nothing or the wrong nodes.
Install, inspect, update, or search for Yolop skills in workspace and global scopes. Use when the user asks to manage skills, import a skill from a registry or GitHub, or upgrade skills.
View and change yolop's own configuration — default provider and model, per-provider API tokens and models, endpoint base URLs, attribution, and harness capabilities. Use when the user asks to configure yolop, set a default provider/model, store an API key, point at a custom endpoint, enable/disable capabilities, or asks "what is your config / what can you configure".
Configure Yolop hooks from natural-language self-configuration requests, especially block, allow, mutate, or audit rules around tool calls.
Built-in guide to using yolop — slash commands, keyboard shortcuts, CLI flags, tools, and session controls. Use when the user asks how yolop works, what commands or shortcuts are available, what yolop can do, or wants help using the terminal UI.
| name | joke |
| description | Generate an original, clean joke on demand. Use when the user asks for a joke, wants something funny, or says they need cheering up. |
| user-invocable | true |
Tell the user an original, genuinely funny joke. This is light entertainment — keep it self-contained and don't touch the workspace, run commands, or read files.
If $ARGUMENTS is provided, treat it as the topic or style to riff on (e.g.
programming, puns, dad joke about coffee). If it's empty, pick a
crowd-pleasing topic yourself — programming and tech humor land well with this
audience.
Keep it workplace-appropriate: no slurs, no targeting protected groups, nothing mean-spirited about a real, identifiable person. Self-deprecating and absurdist humor are great defaults.
