oracle-title-forge
starsforks
How to install oracle-title-forge?
soul-brews-studio/arra-oracle-skills-cli/oracle-title-forge
$npx -y skills add Soul-Brews-Studio/arra-oracle-skills-cli --skill oracle-title-forgeForge a title + subtitle (or reframe) for a book, article, talk, or any technical piece so it has LIFE and honesty — not clinical/dated. The method that produced 'Claude Code Channel ปะทะ Hermes Gateway'. Describe-before-you-name, find the real tension, prism the candidates, cali
SKILL.md
| 1 | # /oracle-title-forge — forge a title that has life, honestly |
| 2 | |
| 3 | > Born 2026-07-09 turning the dead "ผ่าไส้ Discord Channel ของ Claude Code" into |
| 4 | > **"Claude Code Channel ปะทะ Hermes Gateway — สองสถาปัตยกรรมที่ทำให้ AI คุยบน Discord ได้…"** |
| 5 | > The lesson: a great title is *grown from understanding what the thing IS*, not shuffled from words. |
| 6 | |
| 7 | ## Why the method works (read this first) |
| 8 | |
| 9 | A dead title fails one specific way: it has **clarity without intrigue**. "ผ่าไส้ X" tells you |
| 10 | the topic and nothing else — no tension, no question, no stake. Every principle below exists to |
| 11 | add intrigue *without lying*. The magic isn't wordsmithing; it's that each step forces you to |
| 12 | understand the material more deeply, and the title falls out of that understanding. |
| 13 | |
| 14 | ## The method — 7 moves |
| 15 | |
| 16 | ### 1. Describe before you name |
| 17 | Never start by brainstorming words. First write **what each thing IS** — once vividly, once in |
| 18 | plain technical terms. The title grows from this. (For the Discord book, writing "the plugin is |
| 19 | a stdio bridge tied to a session's lifecycle; Hermes is an always-on daemon" is what *revealed* |
| 20 | the contest.) |
| 21 | |
| 22 | ### 2. Find the real tension — and check it's not forged |
| 23 | If it's a comparison/VS, run a **skeptic pass**: is the contest real or clickbait? Two things at |
| 24 | different layers can't fight on features. Reframe the tension at the honest layer — *philosophy, |
| 25 | fit, tradeoff* — not a fake feature-fight. A title promising a showdown the book can't deliver is |
| 26 | a lie. (Discord book: they're transport vs runtime — so the contest is "two philosophies of |
| 27 | presence," which is true, not "which codes better," which is false.) |
| 28 | |
| 29 | ### 3. Prism the candidates — 3-5 lenses |
| 30 | Look at each candidate from angles a single view misses. Useful lenses for titles: |
| 31 | - **🏪 Bookshelf browser** — does the spine make someone pick it up? |
| 32 | - **💀 Honest skeptic** — does the title over-promise? name only one side of a two-sided story? |
| 33 | - **🧑💻 Dev-ear** — *would a developer actually say this phrase?* Kill words devs don't use |
| 34 | ("ให้ AI พูด" → "AI คุยบน Discord"; "ต่อ AI เข้ากับ Discord" → clunky; "data เข้าทางไหน" ✓ real). |
| 35 | - **✍️ Thai editor** — cadence, clean noun phrases, cut stray connectors (ด้วย/ต่อ...เข้ากับ). |
| 36 | - **🎯 Precision** — does the subtitle name the *real axes*, not vague adjectives? |
| 37 | |
| 38 | ### 4. Apply the craft principles (from title research) |
| 39 | - **Tension = clarity × intrigue.** The reader must grasp *something* instantly AND be compelled |
| 40 | to open it for the rest. |
| 41 | - **Contrast breeds curiosity.** Unexpected/opposed words hook ("The Wealthy Barber"). A "ปะทะ" / |
| 42 | "vs" between two named things is contrast built-in. |
| 43 | - **Formula: short curious head + longer explaining subtitle.** Head = hook (1-6 words / a clash / |
| 44 | a question). Subtitle = context + payoff. |
| 45 | - **Question form** raises the stakes above the mechanism ("ใครควรได้…"). |
| 46 | - **Cadence / list-of-three** makes the subtitle linger ("data ขาเข้า, การคุมสิทธิ์, วงจรชีวิต"). |
| 47 | |
| 48 | ### 5. Calibrate register with the human |
| 49 | Draft, then dial. Common arc: *clinical → too poetic → eloquent-but-technical*. The target for |
| 50 | technical work: **สละสลวยแต่ตรง, ไม่เล่นอุปมามาก** — pleasant to the ear, but every phrase points |
| 51 | at something real in the code. Show the human one sample paragraph in the proposed voice and let |
| 52 | their taste calibrate. Their "แปลกๆ" is data — chase the specific weird word. |
| 53 | |
| 54 | ### 6. Name the real technical axes in the subtitle |
| 55 | Don't sell with adjectives ("powerful, elegant"). Sell with the **concrete things the piece |
| 56 | compares/covers** — the axes a practitioner cares about (data path, access control, lifecycle), |
| 57 | ending on the payoff ("ตัวไหนเหมาะกับงานแบบใด"). |
| 58 | |
| 59 | ### 7. Honesty is a feature, not a weakness |
| 60 | Refuse the cheap winner. "Generic: it's a tie on different axes; situational: here's the matrix" |
| 61 | reads as *more* authoritative than "X wins." A title/frame that promises an honest verdict earns |
| 62 | trust the clickbait can't. |
| 63 | |
| 64 | ## Output shape |
| 65 | Offer **2-3 candidates**, each *described by the feeling it gives + the craft reason it works* |
| 66 | (not a bare list), recommend one with why, then render the full cover block (head + subtitle) so |
| 67 | the human sees it assembled. End by asking which — let tast |
People who liked this also viewed
6 picksType
- find-skillsHelps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skSkillsJul 2026
- grill-meA relentless interview to sharpen a plan or design.SkillsJul 2026
- vercel-react-best-practicesVercel's official collection of agent skillsSkillsJul 2026
- improve-codebase-architectureScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.SkillsJul 2026
- setup-matt-pocock-skillsConfigure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.SkillsJul 2026
- triageMove issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.SkillsJul 2026
