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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
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."
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
GitHub repository access in containerized environments using REST API and credential detection. Use when git clone fails, or when accessing private repos/writing files via API.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Decide which model, effort level, and cascade shape each subagent gets, and how to keep improvement loops safe (evaluator-as-selector, stop on regression). Routes on measured cost-per-completed-task rather than per-token price, because a tier's token count varies more by task shape than price varies across tiers. Covers per-model effort semantics, the concision lever, cascade preconditions, context handoff, and watching a subagent fan-out live. Use when choosing a subagent's model or effort, when choosing how to escalate a failed attempt, or when asked which model or effort a task should get. Grounded in a 2026-07 calibration, a 2026-08 coding-cost study, a 2026-09 seeded-bug repair battery, a 2026-10 Haiku 5.5 ladder priced per spawn, and a 2026-10 retry-versus-escalation ladder on 295 SWE-bench Verified tasks; Managed Agents API specifics are operational, not calibrated.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Securely manages API credentials for multiple providers (Anthropic Claude, Google Gemini, GitHub). Use when skills need to access stored API keys for external service invocations.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guidance for asking clarifying questions when user requests are ambiguous, have multiple valid approaches, or require critical decisions. Use when implementation choices exist that could significantly affect outcomes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Read Bluesky/ATProto without depending on Bluesky's AppView — interactions on a user's posts, thread replies, any repo's records, network-wide backlinks across every lexicon, an account's handle and PDS history, which collections are active network-wide, and layer-by-layer outage diagnosis. Use when bsky.app or the AppView is down or slow, when a Bluesky read returns timeouts or 5xx, when asked who liked/replied/quoted/reposted something, when pulling live Bluesky context cheaply, when reading records straight from a PDS, when asked who references a record or account anywhere on the network, whether an account has changed handle or migrated servers, or which lexicons and non-Bluesky apps are active on atproto. Complements browsing-bluesky, which routes everything through the AppView and fails when it does.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.