# Weekly Content Anchor

> Create a single weekly narrative anchor that ties one proof asset to a 7-day content loop, so a brand can publish with coherence instead of posting random fragments.

- **Type:** Skill
- **Install:** `agentstack add skill-cobibean-weekly-content-anchor-system-weekly-content-anchor-system`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [cobibean](https://agentstack.voostack.com/s/cobibean)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [cobibean](https://github.com/cobibean)
- **Source:** https://github.com/cobibean/weekly-content-anchor-system

## Install

```sh
agentstack add skill-cobibean-weekly-content-anchor-system-weekly-content-anchor-system
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# Weekly Content Anchor

Use this skill when:
- you run a weekly content program
- you publish multiple assets across the week
- you have one main release, demo, launch, livestream, essay, or proof asset to build toward
- your current content feels reactive, fragmented, or disconnected

## Core idea

Most teams do not have a content-volume problem.
They have a narrative-coherence problem.

The weekly content anchor solves that by forcing the week to answer one question clearly:

What is the single story this week is trying to make legible?

Everything else hangs off that answer.

## What a weekly anchor is

A weekly anchor is the narrative spine for one week of publishing.

It connects:
- one proof asset
- one main narrative
- one audience hierarchy
- one CTA hierarchy
- one 7-day publishing loop
- one owner map
- one asset checklist

If the anchor is weak, the week becomes unrelated posts.
If the anchor is clear, the week feels like a system.

## The 7 questions every weekly anchor must answer

1. What is the proof asset?
2. What is the one-sentence narrative?
3. Why does this matter now?
4. Who is the primary audience?
5. What should they do next?
6. What assets must ship each day?
7. Who owns each part of execution?

If you cannot answer those cleanly, the anchor is not finished.

## The structure

Save the weekly anchor as `weekly-anchor.md` (or the equivalent weekly planning file your team treats as the single source of truth).

Write the weekly anchor in this format:

```md
## Week dates

## Proof asset
- What is shipping, publishing, releasing, or going live?
- What is the strongest visible proof?

## One-sentence narrative
- The single idea the whole week should reinforce

## Why now
- Why this matters this week, not in theory

## Audience order
1. Primary
2. Secondary
3. Tertiary

## CTA order
1. Primary action
2. Secondary action
3. Tertiary action

## Day-by-day asset map
- Monday:
- Tuesday:
- Wednesday:
- Thursday:
- Friday:
- Saturday:
- Sunday:

## Owner map
- Strategy:
- Writing:
- Design:
- Distribution:
- Analytics:

## Guardrails
- What to emphasize
- What to avoid
```

## The 7-day loop

### Monday — Set narrative
Job:
- choose the proof asset
- define the narrative
- lock audience order and CTA order
- draft the first framing post or brief

Output:
- weekly anchor brief
- kickoff post angle
- owner map for the week

### Tuesday — Build anticipation
Job:
- create curiosity without saying everything at once
- put one visible signal into the market
- identify where distribution or conversation should begin

Output:
- teaser post
- one supporting asset, visual, screenshot, quote, or preview
- early reply or outreach targets

### Wednesday — Show progress
Job:
- prove the week is real before the main event arrives
- show motion, not just promises
- connect visible progress back to the main narrative

Output:
- proof post
- supporting context explaining why that progress matters

### Thursday — Pre-convert
Job:
- make the main event feel worth showing up for
- move the audience from awareness into intent
- package the core reason to care in one sharp line

Output:
- pre-live, pre-release, or pre-launch post
- supporting asset
- locked distribution plan for the main event

### Friday — Main event
Job:
- ship the proof asset
- capture the best moments, claims, screenshots, quotes, or reactions
- gather the raw material that will power the weekend distribution window

Output:
- live updates or release post
- timestamps, notes, quotes, screenshots, or highlights

### Saturday — Distribute hard
Job:
- turn the proof asset into multiple formats
- summarize the strongest takeaway
- extend the shelf life of the work

Output:
- summary thread or recap post
- clips, carousels, quote cards, or cut-downs
- second-wave distribution assets

### Sunday — Retain and deepen
Job:
- turn the week's attention into retained belief
- summarize the lesson
- point people toward the next action
- prepare next week's reset cleanly

Output:
- recap
- newsletter or resource
- scorecard
- next-week notes

## Rules

1. One week should have one spine.
2. Lead with proof, not ambition.
3. One audience comes first. Do not write for everyone equally.
4. CTA order matters. Do not ask for five actions at once.
5. If the proof asset changes midweek, rewrite the anchor immediately.
6. The main event is not the end. Distribution after the event is mandatory.
7. If a claim needs receipts, include receipts.
8. Every asset should reinforce the same narrative, not compete with it.

## Anti-patterns

Anti-patterns are the inverse of the rules above. Fail the weekly anchor if any of these are true:
- the week contains multiple unrelated narratives
- the proof asset is vague or missing
- the CTA is unclear
- the team is posting hype instead of evidence
- the main event arrives without a Wednesday proof post or Thursday pre-convert setup
- the week ends without a recap or retention asset

## Quick operating checklist

Use this at the start of each week:
- [ ] proof asset chosen
- [ ] one-sentence narrative written
- [ ] audience order locked
- [ ] CTA order locked
- [ ] day-by-day asset map written
- [ ] owners assigned
- [ ] guardrails written
- [ ] kickoff post drafted

## Success test

The weekly content anchor is working when:
- a new reader can understand the week quickly
- every post feels related to the same story
- the main event feels earned by the time it happens
- the team can explain what this week is about in one sentence
- the weekend distribution package is obvious, not improvised

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [cobibean](https://github.com/cobibean)
- **Source:** [cobibean/weekly-content-anchor-system](https://github.com/cobibean/weekly-content-anchor-system)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-cobibean-weekly-content-anchor-system-weekly-content-anchor-system
- Seller: https://agentstack.voostack.com/s/cobibean
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.