Weekly Content Anchor System

Weekly Content Anchor

A weekly narrative system for teams that ship real work but publish like every update lives on its own island.

Weekly Content Anchor helps you take one proof asset — a launch, demo, stream, build log, lesson, or release — and turn it into a full 7-day content loop with a clear narrative, audience order, CTA order, and daily asset plan.

The point is simple: stop posting random fragments. Make the week read like a system.

Created by [Web3 Matters](https://web3matters.xyz). Framework authored by Jacobi Lange — [@cobi_bean](https://x.com/cobi_bean) on X, [@cobibean](https://github.com/cobibean) on GitHub.

What this is

This is a public, generalized version of a weekly narrative-planning workflow developed inside Web3 Matters, a Web3 media brand that runs this kind of system across X, YouTube, and TikTok.

Use it when you have one main thing to ship, show, or explain this week — and you want a coherent Monday-to-Sunday content plan around it.

Open `SKILL.md` for the full framework and a ready-to-use weekly anchor template.

Who it is for

• Builders shipping in public
• Founder-led brands
• Content operators running weekly campaigns
• Small teams that need more structure, not more noise

Install in Claude Code

Drop the skill into your Claude skills directory:

# User-level (available in every project)
git clone https://github.com/cobibean/weekly-content-anchor.git ~/.claude/skills/weekly-content-anchor

# Or project-level (available only in this repo)
git clone https://github.com/cobibean/weekly-content-anchor.git .claude/skills/weekly-content-anchor

Then in Claude Code, just ask: *"use the weekly-content-anchor skill to plan this week"* — Claude will pick it up automatically via the frontmatter.

You can also use `SKILL.md` directly as a prompt, template, or reference doc in any other tool (ChatGPT, Notion, Obsidian, etc.) — it's plain Markdown.

How to use it

1. Pick one proof asset for the week.
2. Write the one