mcpField
C
content-writer

content-writer

github.com/ariadossMarketing & growth1261 installsUpdated 1d ago
Repository

About content-writer

content-writer is a skill for researching configured knowledge bases and using the findings to draft content. It supports formats ranging from technical documentation to marketing copy and investor updates.

Key features

  1. 01Search configured knowledge bases
  2. 02Outline content before drafting
  3. 03Adapt tone to content type
  4. 04Review accuracy and completeness

Use cases

  1. 01Draft technical documentation from reference material
  2. 02Prepare product announcements or marketing copy
  3. 03Write investor updates using researched context

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/ariadoss/superskills --skill content-writer

After installing, type/content-writerin Claude Code to confirm it loaded.

Details

From the project README

Content Writer

Create content by researching your knowledge bases before writing.

Knowledge Bases

Reads from knowledge bases configured in ~/.superskills/knowledge.conf. Each line: name|path|description.

cat ~/.superskills/knowledge.conf

Content Types

TypeAudienceTone
Blog postDevelopers, usersTechnical but accessible
DocumentationDevelopersPrecise, example-driven
Marketing copyProspectsBenefit-focused, concise
Investor updateInvestors, boardData-driven, strategic
Product announcementUsersExciting but honest
Internal memoTeamDirect, context-rich

Workflow

Phase 1: Research

Search knowledge bases for relevant context:

# Search across all configured knowledge bases
for kb_path in $(awk -F'|' '{print $2}' ~/.superskills/knowledge.conf); do
  kb_path="${kb_path/#\~/$HOME}"
  [ -d "$kb_path" ] && grep -rli "topic" "$kb_path" --include="*.md" --include="*.txt" --include="*.html"
done

Read the top 3-5 most relevant files. Note key quotes, data points, and frameworks.

Phase 2: Outline

Before writing, create a structured outline:

  1. Hook — why should the reader care?
  2. Context — what's the situation?
  3. Core argument — what's the insight?
  4. Evidence — data, examples, quotes from knowledge base
  5. Call to action — what should the reader do next?
Phase 3: Draft

Write the full draft:

  • Match the tone to the content type and audience
  • Cite knowledge base sources where relevant (for internal docs)
  • Include concrete examples from the project's domain
  • Avoid jargon unless writing for a technical audience
Phase 4: Review

Check the draft against:

  • Accuracy: Cross-reference claims with knowledge base docs
  • Consistency: Align with project positioning and strategy docs
  • Completeness: Cover all key points from the outline
  • Voice: Match the target audience and content type

Tips

  • Research before writing — always check the knowledge base first
  • End with actionable takeaways
  • For technical content, include code examples
  • For marketing content, lead with benefits not features

Comments

Markdown supported