Free for 30 days on Scale.Start free
Run10 steps3-5 days build, ongoing weekly use

Agentize your content calendar with a writer + a scheduler

A writer agent and a scheduler agent. Three to ten posts a week, on cadence.

A two-agent content workflow that ships 3-10 posts/week with you spending under 30 min/day reviewing: writer agent drafts from the topic queue

A two-agent content workflow that ships 3-10 posts/week with you spending under 30 min/day reviewing: writer agent drafts from the topic queue, scheduler agent queues drafts in Buffer / Hypefury / your CMS, you click Publish.

Spin up an agent for the heavy lifting

Writer agent: drafts posts from the topic queue in your voice, attached to Calendar rows.

10 steps, 14 official links, 7 agent prompts

Every external doc the agent needs to cite is pre-loaded into the workspace's Pointers table. No hunting for the right URL mid-draft.

What's inside

Pre-loaded so day one is execution.

5Surfaces
10Steps
7Agent prompts
14Official links
6Tools mapped
Surfaces
  • tableSteps
  • tablePointers
  • docContent calendar plan
  • tableCalendar
  • docStatus
How the loop works

Your agent works. Dock shows you what happened.

Open this template and you get a workspace seeded with an agent prompt. Connect your agent — Claude via our MCP, Cursor, your own setup — and it reads, drafts, and posts updates as it goes. You watch Dock for the latest.

  1. 01

    Connect your agent

    Claim an agent invite at trydock.ai/agent-invites — your agent gets an API key scoped to this workspace. Paste the key into Claude Desktop, Cursor, or any MCP client.

  2. 02

    Your agent reads the workspace

    The agent prompt at the top of the workspace tells your agent its role, the cadence to follow, and the surfaces to update. No extra setup — open Dock and your agent already knows what to do.

  3. 03

    Watch Dock for the latest

    Your agent posts to the Status surface after every meaningful action — newest at top. Wire the workspace's webhooks to Slack or email to get pinged in real time.

Wire it up · Claude Desktop

Add Dock as an MCP server in 30 seconds.

{
  "mcpServers": {
    "dock": {
      "command": "npx",
      "args": ["-y", "@trydock/mcp"],
      "env": {
        "DOCK_API_KEY": "<paste from /agent-invites>"
      }
    }
  }
}

Drop into ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or the equivalent on Windows / Linux. Restart Claude Desktop. Ask Claude:“Read trydock.ai/<org>/agentize-your-content-calendar and follow the agent prompt.”

FAQ

Common questions on this template.

Why two agents instead of one?
Separation of concerns. The writer's job is voice + format; the scheduler's job is timing + channel routing. Combined into one agent, the prompt grows past the model's instruction-following capacity, and the agent does both things mediocrely. Split, each agent has a tight job description, and the Calendar surface is the contract between them, status flips from topic -> drafted -> scheduled -> published as the work moves through.
Can I let the scheduler auto-publish?
No. The pattern in this template is draft-and-queue-but-don't-publish: the scheduler pushes posts into Buffer / Hypefury / Ghost as drafts ready for review, you click Publish. Auto-publish is one bad take away from costing followers; the 30 seconds it costs to click Publish is the trust gate that keeps the workflow safe.
How do the agents know my voice if I'm just starting out?
Two paths. (a) Paste 10-20 of your historical posts (Twitter exports, LinkedIn copies, blog archive) into the Brief and have your agent pattern-match the voice rules; this is the fast path. (b) Ship 4-6 weeks with the agents, mark every edit you make to drafts, the agent learns the patterns from your edits. Path (a) gets you to 70% accuracy fast; path (b) closes the remaining 30% over 4-8 weeks.
What's the right channel mix?
Depends on your audience. For B2B SaaS founders: LinkedIn + X + a newsletter usually wins. For consumer creators: X + Threads + TikTok-adjacent. For developers: Bluesky + a blog + GitHub. Start with 2-3 channels, run for 4 weeks, drop the worst-performer, add a new one. The agents handle the mechanics; you handle the strategic mix.
What does this cost in API tokens?
For a 7 posts/week workflow on Claude Sonnet: $10-30/month for the writer + $0-10/month for the scheduler (mostly free, just API calls to scheduler tools). Buffer / Hypefury subscriptions: $6-19/month. Ghost / Substack: free or $9-29/month. Total: $25-80/month on top of platform subscriptions. ROI is real engagement, the per-post cost is rounding error compared to the time saved.
Can my AI agents help build the agents?
Yes. The template ships agent prompts for the slow parts: extracting voice rules from historical posts, drafting per-channel format rules, building the agent's daily competitor + trend research routine, generating the morning Topic Queue digest, and the weekly engagement-review write-up. The Calendar + Brief surfaces are the canonical record, every topic, every draft, every scheduled post, every weekly review.

Open it. Hand it to your agent. Ship.

One click mints a fresh workspace in your org with the template body seeded. Your agents, your team, your edits from there.

About this template

Curated by the Dock team at . Every template is a real shared workspace we run with our own agents before publishing.

Reviewed regularly by the Dock team. Each playbook step links to the upstream tool's official docs so we can re-verify the rules as platforms change.