content-strategy

Generated source view for the actual executable personal/content-strategy skill. The durable routing article is Writing and Content Skills. Source: skills/personal/content-strategy/SKILL.md

Runtime Source

Bundled Resources

No bundled resource files.

Description

Comprehensive self-promotion and content strategy covering positioning arcs, content calendars, weekly rhythms, and quality gates for X and LinkedIn. Use when planning content, discussing personal brand, building a content calendar, or when the user says "content strategy", "what should I post", "content plan", or "social strategy.

Skill Source

---
name: content-strategy
description: Comprehensive self-promotion and content strategy covering positioning arcs, content calendars, weekly rhythms, and quality gates for X and LinkedIn. Use when planning content, discussing personal brand, building a content calendar, or when the user says "content strategy", "what should I post", "content plan", or "social strategy."
origin: personal
source_slug: content-strategy
---

# Content Strategy

## Positioning Arc

The progression: "talented builder" (early) -> "dangerous early engineer with taste" (mid) -> "operator mode" (mature). Each phase has specific content types and proof requirements.

## Content Calendar

**Phase 1 (Builder)**: Dev diary + frontend theses (architecture posts, custom renderers, design system work)

**Phase 2 (Taste)**: Design system work (behavior vs aesthetic control, component library positioning)

**Phase 3 (Operator)**: PMF, agent revenue, conversion, growth loops

## Weekly Rhythm

- 5 X posts (3 build logs, 1 take, 1 trend reaction)
- 2 LinkedIn posts (narrative, credibility-building)
- 15-20 meaningful replies across both platforms
- 5 DMs to people whose work connects
- 1 artifact/diagram per week (screenshot, architecture sketch, code snippet)

## Four Content Pillars

**Build in Public** -- prove craft. Dev diaries, custom renderers, design systems, frontend patterns. Reaction: "this person ships ambitious technical work."

**Field Notes** -- prove applied relevance. SEO/GEO, agent demos, event learnings, growth loops. Reaction: "this person is close to real product usage."

**Product and Market Diagnosis** -- prove thinking range. PMF, crowded-market strategy, conversion. Reaction: "this person has an original point of view."

**Human Context** -- sparingly. Hackathon summaries, founder conversations, travel moments with real story. Reaction: "this person is in motion."

## Content Mix (per 10 posts)

| Bucket | Share |
|--------|-------|
| Technical build logs | 5 |
| Product and market lessons | 3 |
| Field notes and human context | 2 |

## Agentic No-Slop Workflow Gate

Before asking an agent to write campaign copy, landing-page copy, social drafts, or other marketing output:

1. Create or identify four context files: brand, product, ICP, and offer.
2. Make the agent read those files before drafting. If it did not read them, stop.
3. Refresh current research from socials, recent blogs, YouTube, and `/last30days`. If the research is not fresh this month, research first.
4. Ask the agent to propose the method before writing the final output.
5. Run independent review with two models or two reviewer passes. If both do not approve, revert and revise the method.
6. Check taste and proof against experts, the Obsidian KB, and Kevin's own past work that performed.
7. Ship only after the gate passes, then loop results back into research and the backlog.

The invariant: no context corpus, no fresh research, no review gate, no campaign output.

## Quality Gate

1. Could only you post this exact thing?
2. Is there a concrete proof element?
3. Does it teach, reveal, or frame something?
4. Is the first line strong enough without baiting?
5. Is the close inviting without begging?
6. Does it reinforce the target reputation?

If a draft fails checks 1 or 2, kill it or rewrite it.

## Capture Schema

For each candidate idea: working title, pillar, one-sentence claim, specific proof, why it matters now, best platform/format, artifact to attach, confidentiality check. If claim, proof, or "why it matters" is missing, the post is not ready.

## Channel Roles

**X**: speed, sharp takes, build fragments, event reactions, technical snapshots. Should feel alive and slightly experimental.

**LinkedIn**: credibility, narrative posts, milestone reflections, market synthesis. Should feel sharper, calmer, more legible to operators.

## Integration

This skill provides Kevin's personalized strategic layer. Use alongside:
- `social-draft` — Kevin's X/LinkedIn drafting rules and anti-patterns
- `social-content` — General social media strategy, repurposing, engagement, analytics (upstream from coreyhaines31/marketingskills)
- `copywriting` — Landing page and conversion copy (upstream from coreyhaines31/marketingskills)
- `seo-geo-optimization` — AI search optimization for content pages

---

Timeline

• 2026-07-15 | Generated a browseable source page from the actual executable skill file. Source: skills/personal/content-strategy/SKILL.md