Restore acknowledgment step before research execution

Add back the brief topic acknowledgment ("Researching X — searching
Reddit for upvotes...") and descriptive intro that the v1 skill had.
The v2 version was jumping straight into script execution with no
user-facing feedback about what was being researched.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

SKILL.md

@@ -8,13 +8,11 @@ allowed-tools: Bash, Read, Write, AskUserQuestion, WebSearch
 
 # last30days: Research Any Topic from the Last 30 Days
 
-**YOUR FIRST ACTION: Run this command. Do NOT describe this skill. Do NOT summarize workflows. EXECUTE.**
+Research ANY topic across Reddit, X, and the web. Surface what people are actually discussing, recommending, and debating right now.
 
-```bash
+## STEP 1: Parse User Intent & Acknowledge
-python3 ~/.claude/skills/last30days/scripts/last30days.py "$ARGUMENTS" --emit=compact 2>&1
-```
 
-While that runs, parse the user's input for:
+**Before running anything**, parse the user's input for:
 
 1. **TOPIC**: What they want to learn about (e.g., "web app mockups", "Claude Code skills", "image generation")
 2. **TARGET TOOL** (if specified): Where they'll use the prompts (e.g., "Nano Banana Pro", "ChatGPT", "Midjourney")
@@ -40,6 +38,16 @@ Common patterns:
 - `TARGET_TOOL = [extracted tool, or "unknown" if not specified]`
 - `QUERY_TYPE = [RECOMMENDATIONS | NEWS | HOW-TO | GENERAL]`
 
+**Then output a brief acknowledgment before starting:**
+
+> Researching **{TOPIC}** — searching Reddit for upvotes and comments, X for likes and reposts, and the web for recent coverage. Hang tight...
+
+**Then immediately run the research script:**
+
+```bash
+python3 ~/.claude/skills/last30days/scripts/last30days.py "$ARGUMENTS" --emit=compact 2>&1
+```
+
 ---
 
 ## STEP 2: DO WEBSEARCH WHILE SCRIPT RUNS