oaustegard/making-waffles
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.
$ install --global
skillsauthnpx skillsauth add oaustegard/claude-skills making-wafflesInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 20, 2026, 6:04 AM11.1s2 files scanned
SKILL.md
- name:
- making-waffles
- description:
- 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.
- version:
- 0.1.0
WAFFLES Declaration Generator
Generate preemptive clarifications listing what a post explicitly does NOT say, helping low-context readers avoid misinterpretation.
Background
"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.
When Triggered
Generate a WAFFLES Declaration when user:
- Explicitly requests WAFFLES or "waffle declaration"
- Asks "what might people misread into this?"
- Wants to preempt bad-faith interpretations
- Has a nuanced take on contested territory
- Says "help me clarify what I'm not saying"
Generation Process
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 |
Output Format
🧇 WAFFLES DECLARATION 🦋
aka things this post doesn't say:
— [declaration 1]
— [declaration 2]
...
Use varied phrasing:
- "This post does not claim..."
- "The author is not saying..."
- "This is not an argument that..."
- "Nothing here suggests..."
Quality Criteria
Declarations should be:
- Plausible: Things a reasonable but uncharitable reader might actually misread
- Balanced: Include both "sides" when touching contested territory
- Concise: One line each, clear and direct
- Useful: Genuinely clarifying, not padding
Prioritize likely misinterpretations over implausible ones. A good declaration makes the reader think "oh, I might have assumed that."
Related Skills
oaustegard/semantic-grep
development
VerifiedTrustedCommunity
In-process semantic search over text files or in-memory strings, using Gemini embeddings via the CF AI Gateway. Use when user wants fuzzy/conceptual search where exact-keyword grep would miss — "sessions discussing regulatory constraints", "code about retry logic", "notes mentioning burnout even if the word isn't there". Complements searching-codebases (regex/AST) and extracting-keywords (YAKE). Do NOT use when an exact string/regex match is what's wanted — grep/rg wins on speed and precision there.
135SKILL.mdUpdated Jul 26, 2026
oaustegard/assessing-impact
development
VerifiedTrustedCommunity
Pre-change blast-radius report for a symbol or file. Walks tree-sitting references, augments with a plain-text scan over non-parsed files (configs, plain docs), and clusters affected sites by feature (`_FEATURES.md`) or top-level package. Use when about to refactor, rename, or delete something in a repo you don't own — "what breaks if I change `validateUser`", "who calls this", "is this safe to remove", "where is this used", "blast radius", "impact analysis". This is the CONVERGENT pre-change risk skill — for "what is this repo?" use exploring-codebases; for "where is X?" use searching-codebases.
135SKILL.mdUpdated Jul 26, 2026
oaustegard/verifying-claims
development
VerifiedTrustedCommunity
Check that a document's claims about code are actually true by reading the prose, the code, and the tests and reporting (or fixing) where they disagree. Use whenever the user wants to verify a README, guide, spec, or docstring still matches the code; whenever they mention documentation drift, doc-code sync, "is this still accurate", stale docs, or keeping docs/tests/code consistent; before publishing or merging a docs change; or as a periodic doc-accuracy sweep. The agent reads the prose's meaning directly — there is no claim-comment DSL to maintain. Pairs with TDD — the test suite is the deterministic behavioral gate, this skill is the semantic prose-vs-reality review.
135SKILL.mdUpdated Jul 26, 2026
oaustegard/parsing-video
tools
VerifiedTrustedCommunity
Interpret video content visually by sampling frames into timestamped contact sheets that can be read as images. Use when: user asks what happens in a video; asks to summarize, describe, review, or QA video content or footage; asks about scenes, actions, people, or objects in a video; needs a storyboard-style overview of a clip; asks to find where something occurs in a video. Triggers on 'watch this video', 'what's in this video', 'summarize the video', 'describe the footage', 'contact sheet', 'storyboard', 'review this clip', 'find the scene where', 'scene detection', 'shot boundaries', 'detect cuts', 'dwell points'. For converting, trimming, or transcoding video, use processing-video instead.
135SKILL.mdUpdated Jul 19, 2026