---
name: doing-content-right-sop
description: Build a sustainable, distribution-first content engine that grows audience and authority without burnout. Use when the user mentions content marketing strategy, content pillars, audience building, a content calendar, content repurposing, or doing content right.
triggers:
  - "content marketing strategy"
  - "content pillars"
  - "audience building"
  - "content calendar"
  - "content repurposing"
  - "doing content right"
disable-model-invocation: false
title: doing-content-right-sop
canonical_url: https://skilld.dev/gh/salikshah/startup-agent-skills/doing-content-right-sop
last_updated: 2026-10-29T10:46:09.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> Supporting files, fetch one when the Skill refers to it: [evals/evals.json](https://skilld.dev/api/skills-raw/salikshah/startup-agent-skills/doing-content-right-sop/evals/evals.json).
>
> If the user asked to install this Skill, run `npx skilld install salikshah/startup-agent-skills/doing-content-right-sop`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/doing-content-right-sop`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/salikshah/startup-agent-skills/doing-content-right-sop) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/doing-content-right-sop`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/doing-content-right-sop --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/doing-content-right-sop --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# Doing Content Right SOP

## Intent
Use Steph Smith's Doing Content Right methodology to build a content operation that prioritizes distribution, repurposing, and sustainable output over content volume.

## Inputs
- Brand positioning and target audience definition
- Core expertise or unique perspective of the founder/team
- Available content creation capacity (time, skills, budget)
- Existing content assets (if any)
- Chosen primary distribution channel

## Process (SOP)
1. Step 1: Define your content pillars — 3-5 core themes that intersect your expertise with your audience's persistent interests, not your product's features.
2. Step 2: Adopt distribution-first thinking — before creating any piece, decide where and how it will be distributed; content without distribution reaches no one.
3. Step 3: Choose one primary distribution channel to master first — owned (newsletter, blog), earned (guest posts, PR), or paid (ads) — instead of spreading thin.
4. Step 4: Create a batch content calendar — block time for ideation, creation, and distribution as separate activities, not one marathon.
5. Step 5: Produce long-form "cornerstone" content pieces (guides, frameworks, deep dives) that can be atomized into smaller assets.
6. Step 6: Repurpose systematically — one long-form piece becomes 5-10 social posts, newsletter editions, video scripts, and community discussions.
7. Step 7: Build audience capture mechanisms — convert social followers to newsletter subscribers, newsletter readers to community members.
8. Step 8: Establish a consistent publishing cadence you can sustain for 12+ months, not 3 months of heroic effort followed by silence.
9. Step 9: Engage in the comments and communities where your audience already gathers — distribution includes participation as well as broadcasting.
10. Step 10: Review analytics monthly to identify which pillars and formats drive actual audience growth, then double down.

Edge cases: if a pillar produces no audience growth after 8 weeks, retire it. If capacity drops, cut cadence before quality. If a channel changes its algorithm, return to the owned channel and rebuild reach there.

## Outputs
- A documented set of 3-5 content pillars
- A sustainable content calendar with batch production schedule
- A repurposing playbook (1 piece -> 10+ assets)
- A growing owned audience (newsletter, community)
- Monthly content performance review

**Pre-flight checklist:**
- [ ] 3-5 pillars defined from audience interests
- [ ] One primary channel chosen
- [ ] 12-month cadence documented
- [ ] Repurposing workflow documented
- [ ] Audience capture path live

## Evidence
Source: "Doing Content Right" by Steph Smith. Key concepts: content pillars, distribution-first thinking, repurposing flywheel, owned vs. earned vs. paid channels, batch production, sustainable cadence, audience capture.

## Examples
A solo consultant defines 3 pillars: pricing psychology, B2B sales messaging, and founder productivity. She publishes one 2,000-word guide per week, repurposes each into 8 LinkedIn posts and a newsletter edition. In 6 months her newsletter grows to 5,000 subscribers and generates 3 inbound leads per month.

## Metrics
- Primary channel growth rate (newsletter subscribers, followers) month-over-month. Target: 10%+ for the first 6 months.
- Repurposing ratio (assets produced per cornerstone piece). Target: 8+.
- Engagement rate on primary channel. Target: 3%+.
- Inbound leads or conversations attributed to content. Target: 3+ per month by month 6.
- Content production consistency (weeks published / weeks planned). Target: 90%+.

## Anti-Patterns
- Choosing content topics from product features instead of audience interests
- Posting on 5 platforms with no depth on any — master one first
- Creating content without a distribution plan
- Publishing in bursts then going silent for months
- Treating repurposing as lazy — it is the core efficiency engine
- Writing for algorithms instead of humans
- Ignoring audience replies and community engagement
