Stats
Actions
Tags
From research-pipeline
Write research-backed articles using Sorkin's Desire-Obstacle-Battle narrative framework, MoxyWolf brand voice, and voice injection interview. The final stage of the research pipeline — transforms a verified, synthesized research library into publication-ready content. Use this skill whenever the user says "write the article," "write a blog post," "turn this into content," "draft the post," "write from my research," "create the blog," or any request to produce written content from an existing research library with a defined perspective. Also trigger after the research-synthesizer skill completes and a perspective has been stored. This skill should always be used for STIGViewer blog content and any MoxyWolf publication.
How this skill is triggered — by the user, by Claude, or both
Slash command
/research-pipeline:content-writerThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The final stage of the research pipeline. Takes a verified research library, a thematic
The final stage of the research pipeline. Takes a verified research library, a thematic map, and a writing perspective — and produces a publication-ready article using Sorkin's Desire-Obstacle-Battle narrative structure, MoxyWolf voice, and the voice injection interview process.
Every article produced by this skill combines three layers:
None of these layers is optional. An article without DOB structure reads like an essay. Without MoxyWolf voice it sounds like AI. Without voice injection it sounds like anyone. All three together produce content that's structurally compelling, stylistically authentic, and personally grounded.
Pull the research library, thematic map, and perspective:
-- Get the perspective
SELECT * FROM research_perspectives WHERE library_id = {id} ORDER BY created_at DESC LIMIT 1;
-- Get the thematic map
SELECT * FROM thematic_maps WHERE library_id = {id} ORDER BY created_at DESC LIMIT 1;
-- Get all citations sorted by relevance
SELECT * FROM citations WHERE library_id = {id} ORDER BY llm_relevance DESC NULLS LAST;
Before writing a single word, conduct the 8-question voice injection interview. Ask one question at a time. Wait for the answer before moving to the next.
The Trigger: "What triggered this? What conversation, client situation, or frustration made you want to write about this right now?"
The Evidence: "Give me a real example. A specific conversation, project, or moment where this played out. Names can be changed, but the story has to be real."
The Contrarian Take: "What do most people get wrong about this? Where's the conventional wisdom broken?"
The Authority: "Why should anyone listen to you on this? What experience shapes how you see this differently?"
The Specific Reader: "Who specifically is reading this, and what are they staring at right now that makes them need it?"
The Business Connection: "How does this connect to what MoxyWolf / STIGViewer is building?"
The Call to Action: "What should someone DO after reading this?"
The Emotional Core: "What pisses you off, excites you, or worries you about this topic?"
If voice injection answers were already provided earlier in the session, skip the interview and use those answers directly.
Using the thematic map, perspective, and interview answers, identify:
What the reader wants. Not abstractly — viscerally.
The Desire comes from the interview answers — the practitioner who cried, the CISO staring at 320 controls, the contractor worried about exclusion.
What stands in the way. This is where the research data lives.
The conflict when desire meets obstacle. This is where the ecosystem is right now.
Sorkin doesn't resolve cleanly. Neither do we.
# [Stakes-Driven Headline]
[Opening hook — 2-3 paragraphs establishing desire through a real story
from the voice injection interview. The trigger, the evidence, the person.]
## [Thematic section — not "Act I"]
[Rising action — the obstacle becomes clear. Research data, cost numbers,
specific failures. The contrarian take lands here.]
## [Thematic section]
[Battle intensifies — ecosystem shifts, automation emerges, but the gap
persists. The "what's missing" argument builds.]
[Ending — unresolved tension. Competitive pressure. Timeline deadline.
The reader is left with a decision, not a conclusion.]
---
*[Author bio with authority from Question 4. Link to STIGViewer.com.]*
---
## References
[Full Chicago-style bibliography with URLs for every cited source]
Capture DOB tension in the headline:
Examples from existing blog:
Weave citations naturally into prose using (Author/Organization, Year) format. Never use bracketed numbers [1][2] in the published article.
Every article ends with a full References section in University of Chicago style:
Author/Organization. "Title." *Publication*, Year. [URL](URL).
Pull bibliography entries from the citations table. Include every source cited in the article. Alphabetize by author/organization surname.
Contractions: Use in 80%+ of opportunities. "doesn't," "can't," "it's," "they're." Reserve the remaining 20% for deliberate emphasis: "This is not optional."
Sentence architecture: Vary length aggressively. Some sentences: four words. Others unspool across forty, building through clauses before arriving at their point.
Fragments: Use deliberately. For emphasis. The way actual writers do.
Conjunctions as starters: Start sentences with And, But, Or at least once per section.
Paragraph length: Vary dramatically. Include single-sentence paragraphs alongside longer blocks.
Specificity over abstraction: Replace "significant cost reduction" with actual numbers. Replace "organizations across industries" with named examples.
Before delivering, verify every item:
After presenting the draft, invite passage-level feedback. For each passage the user flags, ask:
Iterate until the user approves.
references/dob-examples.md — Before/after transformation examples for
opening hooks, citation embedding, visceral stakes, and unresolved endingsGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.
npx claudepluginhub moxywolfllc/moxywolf-plugins --plugin research-pipeline