Collaborative Content Writer

VerifiedSafe

Research-driven content writing assistant that helps create structured outlines, integrate credible citations, and refine drafts through iterative feedback. Useful for writing blog posts, articles, newsletters, and technical documentation with a focus on voice preservation and hook improvement.

Sby Skills Guide Bot
ContentIntermediate
6/2/2026
Claude Code
#content-writing#research#citations#outlining#iterative-refinement

Recommended for

Automated summary

This skill helps create high-quality content through a collaborative, research-driven process involving outlining, drafting, and iterative feedback with citations.

Strengths

  • Structured workflow with clear steps
  • Emphasis on research and credible sources
  • Iterative refinement with section-by-section feedback
  • Voice preservation and hook development

Limitations

  • Relies on the user providing clear vision and examples
  • May require manual selection of sources if search is limited
  • Time-consuming for very short content
When to use it

Use when writing long-form content that requires research, structure, and multiple revisions.

When not to use it

Avoid for simple, quick messages or when you need immediate output without iteration.

Security analysis

Safe
Quality score85/100

The skill uses only Read, Glob, and Grep, which are safe, non-destructive tools. There are no commands that modify the file system, exfiltrate data, or execute external payloads. No network access is involved.

No concerns found

How this analysis is made

Examples

Write a blog post with research
I need to write a blog post about the benefits of AI in healthcare. Help me outline it, research key points with citations, and then draft it section by section.
Improve article introduction
I have a draft article about remote work productivity. Can you help me improve the hook and rewrite the introduction to be more compelling?
Research and cite sources
I'm writing a whitepaper on renewable energy trends. Please research current statistics and academic sources, then incorporate them into my draft with proper citations.

name: content-writer description: Research-driven content writing with citations, iterative outlines, and real-time feedback. Transforms writing from solo effort to collaborative partnership. license: MIT compatibility:

  • runtime:any allowed-tools:
  • Read
  • Glob
  • Grep metadata: author: thoreinstein version: 1.0.0

Content Writer

A collaborative writing assistant that helps you create high-quality content through research, outlining, drafting, and iterative refinement.

When to Use This Skill

  • Writing blog posts, articles, or essays
  • Creating technical tutorials or documentation
  • Developing thought leadership content
  • Writing newsletters or email sequences
  • Creating case studies or whitepapers
  • When you need research and citations
  • When you want to improve hooks and introductions
  • When you need section-by-section feedback

Core Capabilities

  1. Collaborative Outlining - Iterate on structure before writing
  2. Research & Citations - Find and integrate credible sources
  3. Hook Improvement - Craft compelling openings
  4. Section Feedback - Real-time feedback as you write
  5. Voice Preservation - Maintain your authentic voice
  6. Citation Management - Proper formatting and attribution
  7. Iterative Refinement - Multiple passes for polish

Workflow

Step 1: Understand the Vision

Before writing, clarify:

  • What's the core message or thesis?
  • Who is the target audience?
  • What action should readers take?
  • What's the desired tone and voice?
  • Are there existing examples of your writing style?

Step 2: Collaborative Outline

Create a structured outline together:

  • Start with main sections
  • Add key points under each
  • Identify where research/citations are needed
  • Mark sections that need strong hooks
  • Iterate until structure feels right

Step 3: Research & Citations

For research-heavy content:

  • Identify claims that need supporting evidence
  • Search for credible sources (academic, industry, primary)
  • Summarize key findings with proper attribution
  • Format citations consistently

Step 4: Draft Section by Section

Work through the outline:

  • Write one section at a time
  • Get feedback before moving on
  • Maintain consistent voice throughout
  • Flag areas of uncertainty

Step 5: Hook Development

For openings and key transitions:

  • Draft multiple hook options
  • Test against audience expectations
  • Choose the most compelling approach
  • Ensure it delivers on its promise

Step 6: Feedback Integration

After each section or full draft:

  • Review for clarity and flow
  • Check argument strength
  • Verify citations are accurate
  • Suggest specific improvements

Step 7: Voice Check

Ensure authenticity:

  • Compare against existing writing samples
  • Flag anything that sounds "off"
  • Preserve unique phrases and patterns
  • Maintain consistent tone

Step 8: Final Polish

Before publishing:

  • Read through completely
  • Check all links and citations
  • Verify formatting
  • Confirm call-to-action is clear

File Organization

For longer projects, organize files as:

content/
├── outline.md           # Living outline
├── research/
│   ├── sources.md       # Citation list
│   └── notes.md         # Research notes
├── drafts/
│   ├── v1.md            # First draft
│   └── v2.md            # Revision
└── final.md             # Published version

Best Practices

Research

  • Prefer primary sources over summaries
  • Verify claims with multiple sources
  • Note publication dates for timeliness
  • Save source URLs for citation

Feedback

  • Be specific about what's not working
  • Offer concrete alternatives
  • Explain the "why" behind suggestions
  • Respect the author's voice

Voice Preservation

  • Study existing writing samples first
  • Mirror sentence structure patterns
  • Preserve favorite phrases
  • Match punctuation habits

Writing Workflows

See references/writing-workflows.md for detailed templates:

  • Blog Post Workflow
  • Newsletter Workflow
  • Technical Tutorial Workflow
  • Thought Leadership Workflow

Examples

See references/examples.md for detailed examples:

  • Teresa Torres-style collaborative workflow
  • Research-heavy article with citations
  • Hook improvement session
  • Section-by-section feedback

Begin by understanding the writer's vision and goals before suggesting structure or content.

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/collaborative-content-writer-mm5t8bby/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/collaborative-content-writer-mm5t8bby' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/collaborative-content-writer-mm5t8bby/download' --output '.skill-downloads/collaborative-content-writer-mm5t8bby/SKILL.md.part' && mv '.skill-downloads/collaborative-content-writer-mm5t8bby/SKILL.md.part' '.skill-downloads/collaborative-content-writer-mm5t8bby/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/collaborative-content-writer-mm5t8bby/SKILL.md' && test -s '.skill-downloads/collaborative-content-writer-mm5t8bby/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/content-writer' && cp -R '.skill-downloads/collaborative-content-writer-mm5t8bby' '.claude/skills/content-writer'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/collaborative-content-writer-mm5t8bby'

openskills read 'collaborative-content-writer-mm5t8bby'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/collaborative-content-writer-mm5t8bby/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills