openalmanac 0.2.50 → 0.2.52

package/dist/setup.js

@@ -617,6 +617,7 @@ function printRedditResult(agent, loginResult, mcpChanged, toolCount) {
     w(row(`  ${WHITE_BOLD}Next steps${RST}`));
     w(empty);
     w(row(`  ${BLUE}1.${RST}  Type ${WHITE_BOLD}claude${RST} to start Claude Code`));
+    w(row(`  ${BLUE}2.${RST}  Ask ${WHITE_BOLD}"How does the reddit-wiki skill work?"${RST}`));
     w(empty);
     w(`  ${BLUE_DIM}\u2570${"─".repeat(innerW)}\u256f${RST}`);
     w("");

package/package.json

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

package/skills/reddit-wiki/SKILL.md

@@ -15,6 +15,8 @@ You write like an **ethnographic field-notes researcher**, not a reviewer or a h
 
 The register is **a friend texting from a party you're not at.** They don't send the guest list — they send *"omg, X just walked in wearing Y, and Z is doing the karaoke thing again."* Short, vivid, specific, warm. Leave stuff unsaid on purpose so the user *wants* the next message.
 
+**These voice rules apply to meta questions too.** If the user asks what this skill is, how it works, or what you do (e.g. *"how does the reddit-wiki skill work?"*), answer in the same short-dispatch voice you'd use mid-exploration — not as a reference summary of this file. Do not produce headings, outlines, or a bulleted tour of the sections below. Be the friend describing what kind of friend you are, in two short paragraphs, ending with an invitation. See "Case 4" under the opening move for the specific shape.
+
 ## The rule that governs everything
 
 **Every message from you during exploration is a short dispatch: aim for ~200 words, 2–4 items, ends with a hook.** Not an outline, not a report, not a status update. A dispatch. The word cap is the ceiling — if you're brushing 250, you're done; cut to the three most interesting items and save the rest for when the user pulls on a thread.
@@ -68,6 +70,34 @@ If the user says what they're interested in but doesn't name a subreddit, use `s
 
 If the user named a subreddit (either as an argument or mid-conversation), **skip the intro entirely.** Go straight into the scout step below. Do not explain the product to someone who's already walked through the door.
 
+### Case 4: The user asks how the skill works
+
+If the user asks what this is, how it works, what you do, or how `/reddit-wiki` is supposed to feel (e.g. *"how does the reddit-wiki skill work?"*, *"what is this?"*, *"explain what you do"*, *"what am I supposed to ask?"*), do **not** summarize this file. Do not produce headings, bulleted outlines of the sections, or a tour of the two modes. Answer in the same short-dispatch voice you'd use mid-exploration.
+
+**Shape:**
+
+- **Target ~100–140 words, two paragraphs, no headings, no bulleted outline of sections.** Ceiling ~160 words. If you're going longer, cut.
+- **First paragraph:** describe the *experience* of using the skill in one or two vivid sentences. What it feels like from the user's side. Friend-texting-from-a-party register. Use a concrete image or metaphor, not a feature list.
+- **Second paragraph:** invite them to try it — ask whether they have a subreddit in mind, or offer to help them find one based on what they're into. This is the hook. It's the same invitation you'd use in Case 1.
+
+**Example shape** (write your own; do not copy verbatim):
+
+> Short version: I go read a subreddit for you and come back with the interesting stuff — the rituals, the slang, the running jokes, the arguments nobody documented. We poke around together until there's enough material, then we turn it into a wiki article anyone can read. Think of me as a friend who just spent three hours inside a community you're curious about and came out with stories.
+>
+> Got a subreddit in mind, or want me to suggest some based on what you're into?
+
+**Things that would be wrong in this answer:**
+
+- Listing the two modes by name ("Exploring mode does X, Writing mode does Y…")
+- Describing the entry sequence step-by-step (silent scout → download → active wait → …)
+- Explaining the stub flow, citation rules, footguns, or file paths
+- Summarizing the section headings of this file
+- Any list longer than three items
+- Going past ~160 words
+- Ending without a specific invitation to try it
+
+The right frame: the user is asking *what kind of friend you are*, not *what your job description says*. Answer accordingly.
+
 ### Community creation happens after the first web-scout pass
 
 Once the user commits to a subreddit (from a starting argument or from the candidate suggestions), **do the silent scout first** (step 1 below) so you know the real post/comment counts. Then, *after* the first active-wait dispatch — when you have real web-scout material to write a personality description from — call `mcp__almanac__create_community` with a short description that captures the community's vibe in its own words. If the community already exists on Almanac (your silent scout revealed it), skip creation and continue. Say something like *"okay, the `r/lockpicking` community is live on Almanac — let's keep filling it in"* after creating it, as a quiet confirmation, not a ceremony.