making-waffles/SKILL.md
Generates WAFFLES Declarations for social media posts — preemptive lists of what a post does NOT say. Use when users mention WAFFLES, ask for clarifications on their post, want to prevent misinterpretation, or request disclaimers for controversial/nuanced takes.
npx skillsauth add oaustegard/claude-skills making-wafflesInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Generate preemptive clarifications listing what a post explicitly does NOT say, helping low-context readers avoid misinterpretation.
"WAFFLES" originated from Bluesky's October 2025 controversy. A meme satirized how users read hostile implications into innocuous posts: "(bluesky user bursts into Waffle House) OH SO YOU HATE PANCAKES??" CEO Jay Graber's reply of "WAFFLES!" to an off-topic comment sparked platform-wide debate. The term evolved into a declaration format pioneered by @gracekind.net — a preemptive list of things a post does NOT claim.
Generate a WAFFLES Declaration when user:
Given post text, produce 12-20 declarations across these dimensions:
| Category | What to identify | |----------|------------------| | Emotional scope | Extremes, permanence, or intensity not claimed | | Universality | Generalizations the author isn't making | | Policy/advocacy | Positions not being endorsed | | Judgments | Evaluations not being rendered | | Temporal claims | Timelines or permanence not asserted | | Adjacent hot-takes | Related controversial positions not implied | | Inverses | Opposite claims also not being made | | Meta-claims | Authority or expertise not asserted |
🧇 WAFFLES DECLARATION 🦋
aka things this post doesn't say:
— [declaration 1]
— [declaration 2]
...
Use varied phrasing:
Declarations should be:
Prioritize likely misinterpretations over implausible ones. A good declaration makes the reader think "oh, I might have assumed that."
testing
Disciplined, validation-gated revision of an EXISTING skill so each edit is a measured improvement rather than a guess. Use when editing, revising, or tuning a skill that already exists and there is evidence it underperforms (observed failures, drift, complaints) — invoke by name, or have versioning-skills / creating-skill defer to it before applying edits. Not for authoring a brand-new skill from scratch (use creating-skill) or one-off prose.
development
Skill-aware orchestration with context routing. Decomposes complex tasks into skill-typed subtasks, extracts targeted context subsets, executes subagents in parallel, and synthesizes results. Self-answers trivial lookups inline. No SDK dependency — uses raw HTTP via httpx. Use when tasks require multiple analytical perspectives, when context is large and subtasks only need portions, or when orchestrating-agents spawns too many redundant subagents.
tools
Orchestrates parallel API instances, delegated sub-tasks, and multi-agent workflows with streaming and tool-enabled delegation patterns. Use for parallel analysis, multi-perspective reviews, or complex task decomposition.
development
Invokes Google Gemini models for structured outputs, image generation, multi-modal tasks, and Google-specific features. Use when users request Gemini, image generation, structured JSON output, Google API integration, or cost-effective parallel processing.