AI agent skill that researches any topic across Reddit, X, YouTube, HN, Polymarket, and the web - then synthesizes a grounded summary
Python ai-promptsai-skillblueskyclaudeclaude-codeclawhubdeep-researchhackernewsinstagramopenclawpolymarketrecencyredditresearchsocial-mediatiktoktrendstwitterweb-searchyoutube
docs: use plan files consistently in skill checklists (#1196)
TTNANddbf601a7e09
diff --git a/changelog.d/1196.fixed.md b/changelog.d/1196.fixed.mdnew file mode 100644index 00000000..13537978--- /dev/null+++ b/changelog.d/1196.fixed.md@@ -0,0 +1 @@+SKILL.md now consistently documents the `--plan` tmpfile form (`--plan "$QUERY_PLAN_FILE"`) in the pre-run checklist and post-run self-check, matching LAW 7; the inline `--plan 'QUERY_PLAN_JSON'` form no longer appears in those spots.diff --git a/skills/last30days/SKILL.md b/skills/last30days/SKILL.mdindex 7fb3faa8..83f66ecc 100644--- a/skills/last30days/SKILL.md+++ b/skills/last30days/SKILL.md@@ -1538,7 +1538,7 @@ Store your plan as `QUERY_PLAN_JSON` - you'll pass it to the script in the next2. **If WebSearch IS available:** you MUST have run Step 0.55 (Pre-Research Intelligence - resolved subreddits, X handles, TikTok hashtags/creators, Instagram creators, GitHub user/repo where applicable) AND Step 0.75 (Query Planner - produced `QUERY_PLAN_JSON` with 2-4 subqueries). These are NOT optional. If either was skipped, return to that step now.3. **If WebSearch is NOT available:** you MUST add `--auto-resolve` to the command instead. Do not attempt Steps 0.55 / 0.75 without WebSearch.4. **The command you are about to run uses `--emit=compact`.** `--emit md` is a debugging/inspection mode and is DISALLOWED as the primary user-facing flow. If you find yourself about to run `--emit md`, stop and switch to `--emit=compact`.-5. **On WebSearch platforms the command MUST include `--plan 'QUERY_PLAN_JSON'`** plus every resolved handle/subreddit/hashtag/creator flag from Step 0.55. Omit only flags whose value was not resolvable.+5. **On WebSearch platforms the command MUST include `--plan "$QUERY_PLAN_FILE"`** (the tmpfile you wrote via heredoc in Step 1 - never inline `--plan 'QUERY_PLAN_JSON'`; an apostrophe in any search or ranking string breaks shell parsing) plus every resolved handle/subreddit/hashtag/creator flag from Step 0.55. Omit only flags whose value was not resolvable.**Degraded path (missing any of the above on a WebSearch platform) is a known regression shape. It produces bland 4-bullet summaries instead of rich synthesis. Do not take it.**@@ -2263,7 +2263,7 @@ Close with `I have all the links to the {N} {source list} I pulled from. Just as4. **Polymarket block present if markets were returned.** If the engine surfaced Polymarket markets, the synthesis includes specific percentages and directional movement. If no markets were surfaced, skip.5. **Coverage footer matches the actual output.** `✅ All agents reported back!` line followed by per-source `├─`/`└─` tree exactly as the engine provided.6. **Trailing citations follow the governing contract.** Preserve any links or source section required by higher-priority host/tool requirements or user instructions. Otherwise end at the invitation ("I have all the links... Just ask.") without a duplicate source list.-7. **Research protocol was followed.** On WebSearch platforms, the command you ran used `--emit=compact --plan 'QUERY_PLAN_JSON'` with resolved handles/subreddits/hashtags. If you took the degraded path (`--emit md`, no plan, no flags), the synthesis will almost certainly fail checks 1-3 - regenerate by returning to Step 0.55 and running the full protocol.+7. **Research protocol was followed.** On WebSearch platforms, the command you ran used `--emit=compact --plan "$QUERY_PLAN_FILE"` with resolved handles/subreddits/hashtags. If you took the degraded path (`--emit md`, no plan, no flags), the synthesis will almost certainly fail checks 1-3 - regenerate by returning to Step 0.55 and running the full protocol.**Max ONE regeneration.** If the regenerated output still fails the self-check, display the best version you have and note to the user which check(s) the data could not satisfy, so they can re-run or adjust their query.