openalmanac 0.2.37 → 0.2.39

package/dist/setup.js

@@ -580,7 +580,7 @@ function installSkill(skillName) {
 }
 /* ── Reddit-specific tool groups ───────────────────────────────── */
 const REDDIT_EXTRA_TOOLS = [
-    "Bash(node ~/.claude/skills/reddit-wiki/scripts/ingest.js *)",
+    "Bash(node */ingest.js *)",
 ];
 /* ── Reddit setup banner ───────────────────────────────────────── */
 function printRedditBanner() {
@@ -622,6 +622,8 @@ function printRedditResult(agent, loginResult, mcpChanged, toolCount) {
     w(row(`  ${BLUE}1.${RST}  Type ${WHITE_BOLD}claude${RST} to start Claude Code`));
     w(row(`  ${BLUE}2.${RST}  Run ${BLUE}/reddit-wiki r/<subreddit>${RST}`));
     w(empty);
+    w(row(`  ${DIM}Ask "how does reddit wiki work?" to learn more${RST}`));
+    w(empty);
     w(`  ${BLUE_DIM}\u2570${"─".repeat(innerW)}\u256f${RST}`);
     w("");
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "openalmanac",
-  "version": "0.2.37",
+  "version": "0.2.39",
   "description": "OpenAlmanac — pull, edit, and push articles to the open knowledge base",
   "type": "module",
   "bin": {

package/skills/reddit-wiki/SKILL.md

@@ -28,6 +28,18 @@ Two phases:
 - **API calls / community slugs**: Bare name — `subreddit=lockpicking`
 - **Accept both** as input: `r/lockpicking` or `lockpicking`
 
+## If no subreddit is given (or user asks "how does this work")
+
+If the user runs `/reddit-wiki` without arguments or asks how it works, explain briefly:
+
+- **What it does:** Takes any subreddit and builds a wiki on Almanac — real articles with citations, images, and links between them. Two phases: a foundation of 15-20 core articles, then a deep pass through the corpus finding niche topics.
+- **What Almanac is:** An open knowledge base anyone can read and write to. Think Wikipedia's depth meets Reddit's community energy.
+- **How it works:** Downloads the subreddit's history, scores posts by quality, then uses AI agents to research and write articles citing the community's own discussions.
+- **Data storage:** Everything is stored locally at `~/.openalmanac/corpus/<subreddit>/`. The user can delete it anytime after the wiki is published.
+- **Any subreddit:** They can pick any subreddit they're interested in. Some smaller or newer subreddits may not have data available — if that happens, you'll suggest alternatives or nearby subreddits that do have data.
+
+Then ask them which subreddit they want to build a wiki for.
+
 ## Step 1: Scout
 
 Extract the subreddit name from the argument (strip `r/` prefix if present). Use the bare name for all API calls and file paths. Use `r/<name>` when talking to the user.
@@ -79,30 +91,41 @@ node ${CLAUDE_SKILL_DIR}/scripts/ingest.js <subreddit> download --since <year>
 
 This saves raw JSONL to `~/.openalmanac/corpus/<subreddit>/raw/`. The raw data is kept so you can re-filter later with different quality thresholds without re-downloading.
 
+Tell the user:
+
+```
+Downloading now. Go grab a coffee ☕ — I'll have everything 
+ready when you get back.
+```
+
 While it downloads, share interesting context about the community. Use your knowledge and do a quick `search_web` if helpful. Share REAL information — facts, history, notable members, what makes this community unique. Not questions, not small talk.
 
+Also tell them where the data is being stored: `~/.openalmanac/corpus/<subreddit>/`
+
 When the download finishes, run the filter step:
 
 ```bash
 node ${CLAUDE_SKILL_DIR}/scripts/ingest.js <subreddit> filter --stats-only
 ```
 
-This shows the quality distribution — how many posts at each quality level, with sample posts. Use this to decide the right quality threshold. Then present it to the user:
+This returns quality scores and sample posts at each level. Present the results as a table:
 
 ```
 Download complete. X posts, Y comments from r/<subreddit>.
 
-Here's what the data looks like:
-
-  high quality (top 10%):  ~300 posts — best discussions, guides, educational content
-  medium (top 30%):        ~900 posts — solid community knowledge
-  low (top 60%):           ~1,800 posts — includes questions and casual posts
-  all:                     ~3,000 posts
+| Quality   | Posts | What's in it | Example |
+|-----------|-------|--------------|---------|
+| **high**  | ~300  | Best guides, deep discussions, tutorials | "I designed a mechanism to make locks unpickable" (279 upvotes) |
+| **medium** (recommended) | ~900 | Solid community knowledge, good Q&A | "Does anyone know about this lock?" (19 upvotes, 9 comments) |
+| **low**   | ~1,800 | Includes casual posts and quick questions | "Mul-T-Lock Interactive" (31 upvotes) |
+| **all**   | ~3,000 | Everything that isn't deleted | — |
 
-I'd recommend medium for the foundation — good balance of quality and coverage.
-We can dip into the rest during Phase 2.
+I'd recommend medium — good balance of quality and coverage.
+We can always dip into the rest during Phase 2.
 ```
 
+Fill in the actual numbers and sample titles from the `--stats-only` output. The samples make it real — the user can see what kind of posts are at each level.
+
 Wait for the user to pick (or confirm your recommendation), then run:
 
 ```bash
@@ -113,7 +136,15 @@ This writes markdown entries to `~/.openalmanac/corpus/<subreddit>/entries/`. Ea
 
 Report the results:
 - How many entries were created
-- Where they're stored
+- Where they're stored (`~/.openalmanac/corpus/<subreddit>/entries/`)
+
+### If the subreddit has no data on Arctic Shift
+
+If the `count` command returns 0 posts, the subreddit may not be indexed. In this case:
+- Tell the user this subreddit doesn't have historical data available
+- Suggest nearby or related subreddits by searching Arctic Shift for similar names
+- Ask if they'd like to try one of those instead
+- Do NOT just fail silently — help them find something that works
 
 ## Step 3: Phase 1 — Foundation