From majestic-marketing
Writes articles matching an author's voice using Style DNA metrics from style-dna.md. Takes topic input; enforces sentence length, punctuation, structure. For ghostwriting or style imitation.
npx claudepluginhub majesticlabs-dev/majestic-marketplace --plugin majestic-marketingThis skill is limited to using the following tools:
Write an article on: $ARGUMENTS
Captures and refines user's writing voice into AUTHOR_VOICE.md via discovery questions, drafts, sample generation, and feedback cycles for AI mimicking tone/style.
Rephrases or rewrites content to match user's preferred tone, voice, and style using WritingKit and UserProfile JSON. Preserves facts for article drafts.
Composes full personal essays from structured notes in user's voice using persistent style profile, calibrated to platform and word count.
Share bugs, ideas, or general feedback.
Write an article on: $ARGUMENTS
Audience: Content creators with a Style DNA or brand voice report who need new articles written in that exact voice.
Goal: Produce articles that match a measured voice fingerprint precisely — hitting the numbers, not approximating.
Read the style-dna.md file specified by the user. Extract and internalize:
If the DNA file has a Cross-Article Comparison with multiple modes (e.g., "workshop tour" vs. "war story"), determine which mode fits the requested topic and target word count. State which mode you're using and why.
Before writing a single sentence, build a skeleton:
State the single boldest, most specific claim about this topic in one sentence. This becomes your opening.
What prior shift, pattern, or concrete comparison grounds this piece? Identify it.
List the concrete details you'll use:
Outline 3-5 headed sections. For each, note:
Plan the first 3-4 paragraphs and last 3-4 paragraphs according to the structural blueprint from the DNA.
Present the plan to the user and wait for approval before drafting.
Write the full article following the plan. While drafting, actively manage these constraints:
After completing the draft, run a verification pass. For each metric, compare your draft against the DNA target:
Use Python or manual counting to measure your draft:
| Metric | DNA Target | Your Draft | Accuracy |
|---|---|---|---|
| Avg sentence length | |||
| Short sentence ratio (<8 words) | |||
| Comma density per 100w | |||
| Colon density per 100w | |||
| Semicolons | |||
| Em/en dashes | |||
| One-sentence paragraph % | |||
| Avg paragraph length (words) | |||
| Conjunction openers % | |||
| Rhetorical questions (count) | |||
| Parenthetical asides (count) | |||
| Contractions per 100w | |||
| You/your per 100w | |||
| I/my/me per 100w | |||
| Exclamation marks |
For each metric, calculate accuracy as:
accuracy = 100 - abs(target - actual) / target * 100
Clamp to 0-100%. Report the average across all metrics.
If any metric is below 80% accuracy:
Do NOT present the draft until the average accuracy is above 85% and no single metric is below 70%.
Show the user:
Then ask:
Article ready at [X]% overall style accuracy. Want me to save it, or revise specific sections?
Wait for the user's direction before saving.
*-style-dna.md files in the current directory and docs/. Ask which one to use.Works with the content creation pipeline:
style-forensics (create DNA) → style-writer (write in that voice) → humanizer (with same DNA, strip AI tells) → copy-editor (polish)
style-forensics to create the Style DNA report from writing sampleshumanizer to strip any remaining AI patterns, copy-editor for final polishcontent-writer for general articles without a voice target, seo-content for SEO-first articles