strategist-voice

Apply analyst house style rules to long-form strategy and forecast reports.

Updated Sep 9, 2026
One-click install
npx skills add https://github.com/lyndonkl/hermesworld --skill strategist-voice-lyndonkl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: strategist-voice
Source: https://github.com/lyndonkl/hermesworld/tree/main/packages/superforecaster/skills/writing/strategist-voice
Command: npx skills add https://github.com/lyndonkl/hermesworld --skill strategist-voice-lyndonkl

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Draft reports produced by AI assistants often read as machine-generated: em dashes everywhere, negation cascades, inline source parentheticals, hedged opinions, and undefined strategy jargon. This Skill enforces a consistent analyst house style so a consolidated report reads as written by a senior human analyst. ## Core Features & Use Cases - Hard style rules: Bans em dashes, "not X, not Y, not Z" cascades, Strategist inference: prefixes, inline citations, hollow openings, and tl;dr closers, with a final-pass checklist to verify each rule. - Opinion signalling and structure: Provides a graded conviction scale (tentative to provocative), three permitted opening-paragraph patterns, and sentence-variation guidance modelled on Damodaran's Musings on Markets and Thompson's Stratechery. - Footnoted citations and jargon control: Enforces numbered footnote citations with a bibliography grouped by source type, and requires strategy terms like wedge, flywheel, TAM, and moat to be defined on first use or rewritten away. - Use Case: After assembling working notes for a Figma strategy report, run the final consolidation pass to rewrite openings, convert inline sources to footnotes, and tick the checklist before handing the document to slop-detector and readability-check. ## Quick Start Apply the strategist-voice house style to my draft report and run the final-pass checklist before returning the finished markdown.

Frequently Asked Questions about strategist-voice

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I make an AI-written report read like a human analyst wrote it?

Apply a fixed house style during the final consolidation pass: ban em dashes and negation cascades, signal opinion through graded phrasing instead of prefixes, use footnoted citations, and vary sentence length. This Skill encodes those rules with a checklist.

How do I replace inline source citations with footnotes in a report?

Convert each inline [Source: ...] or (Source: ...) into a numbered footnote marker after the sentence punctuation, then list sources in a bibliography grouped by type such as primary company material, founder voices, and secondary analysis.

When should I apply the strategist-voice style in my writing workflow?

Apply it only in the final consolidation step, when working notes become a publishable document. It is not a drafting aid and does not check readability or slop; those are handled by the readability-check and slop-detector skills afterward.

What writing patterns does this style guide ban?

It bans em dashes, "not X, not Y, not Z" negation cascades, Strategist inference prefixes, inline citations, "It's worth noting" openings, "In conclusion" closers, undefined strategy jargon, and abstract X-shaped labels doing analytical work.

How do I handle strategy jargon like wedge, flywheel, or TAM for general readers?

Define each term inline on first use with a brief parenthetical or appositive phrase, or rewrite the sentence to avoid the term entirely. A term used twice without definition signals the writer copied a register rather than reasoned through the argument.