SkillAgentSearch skills...

write

Use this command to create comprehensive, SEO-optimized long-form blog content. `/write [topic or research brief]`

Install / Use

npx skills add so-ta/onlystory-media

Installs into whichever agent you are using.

About this skill

Claude Commands

Claude Code slash commands

Quality Score

57/100

Supported Platforms

Claude Code
Zed

Tags

Write Command

Use this command to create comprehensive, SEO-optimized long-form blog content.

Usage

/write [topic or research brief]

What This Command Does

  1. Creates complete, well-structured long-form articles (2000-3000+ words)
  2. Optimizes content for target keywords and SEO best practices
  3. Maintains your brand voice and messaging throughout
  4. Integrates internal and external links strategically
  5. Includes all meta elements for publishing

Process

Pre-Writing Review

  • Research Brief: Review research brief from /research command if available
  • Brand Voice: Check @context/brand-voice.md for tone and messaging
  • Writing Examples: Study @context/writing-examples.md for style consistency
  • Style Guide: Follow formatting rules from @context/style-guide.md
  • SEO Guidelines: Apply requirements from @context/seo-guidelines.md
  • Target Keywords: Integrate keywords from @context/target-keywords.md naturally

Content Structure

1. Headline (H1)

  • Include primary keyword naturally
  • Create compelling, click-worthy title
  • Keep under 60 characters for SERP display
  • Promise clear value to reader

2. Introduction (150-250 words)

CRITICAL: Direct Answer First (AI Search Optimization)

For any "best/top/how" query, the first 1-2 sentences MUST directly answer the question. AI scrapers (ChatGPT, Perplexity, Gemini) pull from the top of the page. Don't bury the answer behind narrative.

Example — "best project management tools":

The best project management tools in 2026 are Asana, Monday, and ClickUp — each built for different team sizes and workflows. Here's how they compare.

After the direct answer, use a hook to keep human readers engaged.

Choose ONE hook type for each article:

| Hook Type | Example | Best For | |-----------|---------|----------| | Provocative Question | "What if the 'free' plan is actually costing you $500/month in lost opportunities?" | Challenging assumptions | | Specific Scenario | "Last Tuesday, Sarah checked her dashboard and discovered something alarming: her site had been invisible to Google for three weeks." | Creating emotional connection | | Surprising Statistic | "73% of SaaS users who switch platforms do so within 18 months, and most cite the same three reasons." | Data-driven topics | | Bold Statement | "Your current tool is lying to you about your numbers." | Controversial takes | | Counterintuitive Claim | "The cheapest option might be the most expensive decision you make this year." | Comparison content |

After the hook, follow the APP Formula:

  • Agree: Acknowledge something the reader already believes/feels

  • Promise: Tell them exactly what they'll learn or gain

  • Preview: Brief overview of what's coming (can include mini table of contents for long posts)

  • Keyword: Include primary keyword in first 100 words

  • Credibility: Establish why you/this article is authoritative

3. Key Takeaways Block (After Introduction)

REQUIRED: TL;DR block immediately after the introduction, before the first H2 body section.

This gets pulled into AI-generated summaries and helps both AI and human readers quickly assess the article's value.

> **Key Takeaways**
> - [Core finding or recommendation #1]
> - [Core finding or recommendation #2]
> - [Core finding or recommendation #3]
> - [Core finding or recommendation #4 if needed]
> - [Core finding or recommendation #5 if needed]

Rules:

  • 3-5 bullet points
  • Each bullet is a standalone claim with specifics (numbers, names, outcomes)
  • NOT a table of contents — these are the article's actual conclusions
  • Written after the full article is drafted (so the takeaways are accurate)

4. Main Body (1800-2500+ words)

  • Logical Flow: Organize sections in clear, progressive order
  • H2 Sections: 4-7 main sections covering comprehensive topic scope
  • H3 Subsections: Break complex sections into digestible pieces
  • Keyword Integration: Use primary keyword 1-2% density, variations throughout
  • Depth: Provide thorough, actionable information at each point
  • Data: Reference statistics and studies to support claims
  • Visuals: Note where images, screenshots, or graphics enhance understanding
  • YouTube Embed: Include at least one relevant YouTube video (prefer your own channel, then authoritative third-party) — AI models cross-reference video and article content
  • Lists: Use bulleted or numbered lists for scannability
  • Formatting: Bold key concepts, use short paragraphs (2-4 sentences MAX)

REQUIRED: Mini-Stories (2-3 per article)

Research shows we're 22x more likely to remember facts wrapped in stories. Every article MUST include 2-3 mini-scenarios with:

  • A specific person (use names, even if fictional: "Sarah," "Mike," "The team at Acme Corp")
  • A concrete situation with details (dates, numbers, specifics)
  • A clear outcome that illustrates the point

Example mini-story (aim for 50-150 words each):

"When Marcus launched his SaaS product in March 2024, he chose the cheapest hosting plan he could find, $5/month seemed like a no-brainer. Six months later, his app hit 10,000 active users. That's when he discovered the hidden bandwidth fees buried in his provider's terms. His $5/month plan suddenly became $89/month. Worse, migrating mid-growth meant a 3-week gap in analytics that cost him a $2,000 partnership deal. The 'savings' from cheap hosting cost him over $3,000."

Place mini-stories:

  • One in the introduction or early section (to hook readers)
  • One in the middle (to re-engage skimmers)
  • One near the conclusion (to reinforce the main point)

REQUIRED: Contextual CTAs (2-3 per article)

Don't just put one CTA at the end. Embedded CTAs get 121% more conversions than end-only CTAs.

CTA Placement Strategy: | Location | CTA Type | Example | |----------|----------|---------| | After first major value section | Soft CTA (learn more) | "Want to see how this works in practice? [Explore our features →]" | | After comparison/proof section | Medium CTA (try it) | "Ready to test the difference? Start a free trial, no credit card required." | | End of article | Strong CTA (convert) | "[Start Your Free Trial →]" with supporting text |

CTA Rules:

  • Make CTAs contextual (relate to the section content)
  • Vary the format (inline text, bold callout, button-style)
  • First CTA should appear within the first 500 words
  • Never use generic "Click here" text

5. Conclusion (150-200 words)

  • Recap: Summarize 3-5 key takeaways
  • Action: Provide clear next steps for reader
  • CTA: Include relevant call-to-action (free trial, resource download, etc.)
  • Encouragement: End on empowering, forward-looking note

SEO Optimization

Keyword Placement

  • H1 headline
  • First paragraph (within first 100 words)
  • At least 2-3 H2 headings
  • Naturally throughout body (1-2% density)
  • Meta title and description
  • URL slug

Internal Linking (3-5+ links)

  • Reference @context/internal-links-map.md for key pages
  • Link to relevant pillar content from your site
  • Link to related blog articles
  • Link to product/service pages where natural
  • Use descriptive anchor text with keywords

External Linking (2-3 links)

  • Link to authoritative sources for statistics
  • Reference industry research or studies
  • Link to tools or resources mentioned
  • Build credibility with quality sources

Readability

  • Keep sentences under 25 words average
  • Use transition words between sections
  • Vary sentence length for rhythm
  • Write at 8th-10th grade reading level
  • Use active voice predominantly
  • Break up text with subheadings every 300-400 words

Target Audience Focus

  • Audience Perspective: Write for your target audience (defined in @context/brand-voice.md)
  • Practical Application: Show how information applies to their specific challenges
  • Product Integration: Naturally mention how your features solve problems (reference @context/features.md)
  • Industry Context: Reference relevant trends and best practices
  • Technical Accuracy: Ensure terminology and processes are correct for your industry

Brand Voice Consistency

  • Maintain your brand tone (reference @context/brand-voice.md for specifics)
  • Follow your established voice pillars
  • Use messaging framework from your context files
  • Apply terminology preferences consistently
  • Match tone to content type (how-to, strategy, news, etc.)

Output

Provides a complete, publish-ready article including:

1. Article Content

Full markdown-formatted article with:

  • H1 headline
  • Introduction
  • Body sections with H2/H3 structure
  • Conclusion with CTA
  • Proper formatting and styling

2. Meta Elements

---
Meta Title: [50-60 character optimized title]
Meta Description: [150-160 character compelling description]
Primary Keyword: [main target keyword]
Secondary Keywords: [keyword1, keyword2, keyword3]
URL Slug: /blog/[optimized-slug]
Internal Links: [list of pages linked from your site]
External Links: [list of external sources]
Word Count: [actual word count]
---

3. SEO Checklist

  • [ ] Primary keyword in H1
  • [ ] Primary keyword in first 100 words
  • [ ] Primary keyword in 2+ H2 headings
  • [ ] Keyword density 1-2%
  • [ ] 3-5+ internal links included
  • [ ] 2-3 external authority links
  • [ ] Meta title 50-60 characters
  • [ ] Meta description 150-160 characters
  • [ ] Article 2000+ words
  • [ ] Proper H2/H3 hierarchy
  • [ ] Readability optimized

4. AI Search Optimization Checklist

  • [ ] Direct answer: First 1-2 sentences directly answer the target query
  • [ ] Key Takeaways: TL;DR block with 3-5 specific bullet points after introduction
  • [ ] Meta description: Directly answers the query (not just a teaser)
  • [ ] YouTube embed: At least one relevant video embedded
  • [ ] FAQ prompts: Questions written in natural language people would type into ChatGPT
  • [ ] One idea per section: Each H2/H3 focuses on a single clear concept
  • [ ] Author attribution: Named author in frontmatter

5. Engagement Checklist

  • [ ] Hook: Opens with question, scenario, statistic, or bold statement (NOT generic definition)
  • [ ] APP Formula: Introduction includes Agree, Promise, Preview elements
  • [ ] Mini-stories: 2-3 specific scenarios with names, details, and outcomes
  • [ ] Contextual CTAs: 2-3 CTAs placed throughout (not just at end)
  • [ ] First CTA: Appears within first 500 words
  • [ ] Paragraph length: No paragraphs exceed 4 sentences
  • [ ] Sentence rhythm: Mix of short (5-10 words) and longer sentences (15-25 words)

File Management

After completing the article, automatically save to:

  • File Location: drafts/[topic-slug]-[YYYY-MM-DD].md
  • File Format: Markdown with frontmatter and formatted content
  • Naming Convention: Use lowercase, hyphenated topic slug and current date

Example: drafts/content-marketing-strategies-2025-10-15.md

Automatic Content Scrubbing

CRITICAL: Immediately after saving the article file, automatically invoke the content scrubber to remove AI watermarks and telltale patterns.

Why This Matters

AI-generated content often contains invisible Unicode watermarks and characteristic patterns (like em-dash overuse) that can identify it as AI-written. Scrubbing removes these indicators to make content appear naturally human-written.

Scrubbing Process

  1. Invoke Scrubber: Run /scrub [file-path] on the saved article file
  2. Automatic Execution: This should happen automatically, not require user action
  3. Timing: Must occur immediately after file save, before any other processing
  4. Scope: Scrub the main article file only (not meta or analysis files)

What Gets Cleaned

  • Invisible Unicode watermarks (zero-width spaces, BOMs, format-control characters)
  • Em-dashes replaced with contextually appropriate punctuation (commas, semicolon

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars0
CategoryContent
UpdatedNaNy ago
Forks0

Security Score

68/100

Audited on Invalid Date

2 medium1 low