In short:
ak-content-marketingbuilds pillars and topic clusters, an editorial calendar, briefs for each blog post, content audits of old posts and ways to repurpose existing ones. It reuses the material you already have before making anything new. Finished posts stop at review, and are only published when you allow that exact channel.
Disclosure: I maintain AgentKit and have an affiliate relationship with it: the AgentKit link in this post is an affiliate link; buying through it gets you 30% off.
Summary
Use it when you need to know what to write, for whom, when to publish it and which old posts to keep.
flowchart LR
A["Content goals, briefs, inventory file"] --> B["ak-content-marketing"]
B --> C["Pillars, clusters, editorial calendar"]
B --> D["Reviewed blog brief and draft"]
B --> E["Content audit report"]
D --> F{"Allowed to publish on this channel?"}
F -->|"Not yet"| G["Stop at the reviewed version"]
F -->|"Yes"| H["Publish"]Four concepts to know:
| Concept | Question | Example |
|---|---|---|
| Content pillars | Which topics will the brand talk about again and again? | A budgeting app picks 3 pillars: monthly saving, paying off debt, investing small amounts |
| Topic clusters | Which posts should be split out, and which merged? | The "paying off debt" pillar has one main post of 3000+ words, surrounded by cluster posts of about 1500 words; two posts with the same search intent are not split |
| Editorial calendar | Which post goes out on which day, who owns it, and what stage is it at? | Each row has a publish date, content type, working title, keyword, owner, status, channel; a post with no owner is clearly marked as unassigned |
| Content audit | For each old post: keep, update, merge, redirect or delete? | A high-traffic post with outdated figures gets updated; five thin posts on the same topic get merged |
The skill also handles repurposing: one blog post becomes social posts, an email sequence, a video script. It prefers repurposing before writing new.
Sample prompt for a content strategy:
/ak-content-marketing Next quarter's content strategy for <product name>.
Audience: <target customer description>.
Goal: more trial sign-ups from the blog.
Already have: a brief at <brief path>, a list of old posts at <inventory file path>.
Constraint: a team of 2, about 2 posts a week.
Done when: there are 3-5 pillars, a post cluster for each pillar and a way to measure.This skill has no flags.
Below is the detailed version: the run flow, 5 situations with prompts, the change history by ak release, and common pitfalls. The detailed version and the interactive page are for subscribers. Your agent can also search them through the portal's MCP.
Opens when your account has subscriber access
This guide is for subscribers
Once your account has access, the full piece, the interactive visual and the agent call all open.
- Sign in or create a modernEngineer accountReading access belongs to your account email.
- Choose a plan on the pricing page1, 3 or 12 months, paid by VietQR bank transfer. Access opens about a minute after the money arrives.
- Or redeem a Facebook subscriber codePeople supporting the page on Facebook get an activation code by message each month.
Already a subscriber? Sign in to read.
Use this piece in your agent
Get an API keyCopy the text below and paste it into Claude Code, Codex or whichever agent you use. The agent reads the piece and checks it against the repo you have open.
Read "ak-content-marketing: pillars, editorial calendar and content audits" on modernEngineer and apply it to this repo.
1. Call the content_get tool of the modernengineer MCP server with locale "en", slug "ak-content-marketing". If the modernengineer MCP server is not connected, stop and walk me through connecting it from https://modernengineer.dev/en/mcp.
2. Summarize the main steps of the piece and point out which apply to this repo.
3. Propose concrete changes and ask me before editing any file.Connect MCP in Claude Code (once)
claude mcp add --transport http modernengineer \
https://api.modernengineer.dev/mcp \
--header "Authorization: Bearer <API key>"Reading the full piece over MCP needs an API key from a subscriber account or one that bought this guide. Without access, the agent only gets the opening.
- Version
- v1.0.0
- Updated
- 22/10/2026
- Licence
- All rights reserved
- Slug
- ak-content-marketing
