openalmanac 0.2.38 → 0.2.40

package/package.json

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

package/skills/reddit-wiki/SKILL.md

@@ -108,22 +108,24 @@ When the download finishes, run the filter step:
 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:
+| 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 | — |
 
-  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
-
-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
@@ -154,18 +156,30 @@ Read 20-30 corpus entries (prioritize high-score posts) to understand the landsc
 list_articles(community_slug: "<subreddit>", sort: "most_referenced")
 ```
 
-Identify 15-20 core topics grouped by theme. These should be the foundational articles every reader of this wiki would expect. Present them to the user grouped by theme:
+Identify 15-20 core articles. **Favor nouns over themes** — specific things people would look up, not vague survey topics.
+
+- **~70% nouns:** Specific locks, tools, people, techniques, concepts. "American Lock 1100", "Spool Pin", "Tension Wrench", "LockPickingLawyer". These are the building blocks — what people search for, link to, and learn from.
+- **~30% structural themes:** Only the big ones that serve as entry points and tie nouns together. "Belt System", "Lock Picking Basics". Not vague surveys — each should be a real article that teaches something.
+
+Bad: "Security Pin Mechanics" (vague theme, reads like a textbook chapter)
+Good: "Spool Pin", "Serrated Pin", "Mushroom Pin" (specific nouns — then link them from a "Security Pins" overview)
+
+Present them to the user grouped by category, but make clear most articles are about specific things:
 
 ```
 Here's what I'd build for the foundation:
 
-  Lock Anatomy
-    › Cylinder, Warding, Master Keying
+  Locks
+    › American Lock 1100, Abus 55/40, Master Lock #3, Kwikset SmartKey
+
+  Components
+    › Spool Pin, Serrated Pin, Tension Wrench, Key Pin
 
   Techniques
-    › Bumping, Comb Picking, Impressioning
+    › Bumping, Raking, Single Pin Picking
 
-  [etc.]
+  Community
+    › LockPickingLawyer, BosnianBill, Belt System
 
 Want to add or change anything?
 ```
@@ -355,6 +369,11 @@ openalmanac.org/communities/<subreddit>/wiki
 - The description should have personality — capture the community's vibe, not a generic taxonomy
 - Find a good cover image with `search_images`
 
+### File access
+- Use `Glob` and `Read` tools to browse and read files in `~/.openalmanac/` — do NOT use `Bash(ls ...)` or `Bash(cat ...)`
+- Use `Write` and `Edit` tools to modify files — do NOT use `Bash(echo ...)` or `Bash(sed ...)`
+- The only Bash command you should use is the ingest script
+
 ### What NOT to do
 - Don't estimate how long things will take
 - Don't make small talk or ask personal questions