Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Build and manage content calendars for multi-platform content marketing including editorial planning, content type allocation, and team workflow. Use this skill when the user needs to plan content across channels, coordinate a content team, maintain publishing consistency, or align content with business goals — even if they say 'we post randomly', 'plan our content for next month', 'content strategy', or 'what should we post this week'.
.claude/skills/asgard-ai-platform-mkt-content-calendar/SKILL.md| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-01 | ✗→✓ | ▲ Improved | 7% | 0% |
| case-02 | ✗→✓ | ▲ Improved | -19% | 0% |
| case-03 | ✗→✓ | ▲ Improved | -14% | 0% |
| case-05 | ✗→✓ | ▲ Improved | 43% | 0% |
| case-07 | ✗→✓ | ▲ Improved | 59% | 0% |
IRON LAW: Higher Posting Frequency Without Content-Channel Fit REDUCES Engagement Per Post
Agents default to "post more often" when building content calendars. But
publishing frequency only improves reach when content format matches
platform consumption patterns. Posting a LinkedIn thought-leadership
article to Instagram Reels, or pushing daily content when you only have
2 good ideas per week, dilutes engagement rate and trains the algorithm
to suppress your content. Test content-channel fit on 5 posts BEFORE
committing to a cadence.Define 3-5 recurring themes that align with business goals:
| Pillar | Purpose | Content Ratio | Example | |--------|---------|-------------|---------| | Educational | Establish expertise, attract search traffic | 40% | How-to guides, tutorials, tips | | Promotional | Drive sales and conversions | 20% | Product features, offers, launches | | Engagement | Build community and interaction | 20% | Polls, questions, UGC, memes | | Brand Story | Build trust and personality | 10% | Behind-scenes, team stories, values | | Curated | Add value without creating from scratch | 10% | Industry news, partner content |
Monthly Planning (first week of prior month)
Weekly Check-in
One Core Piece (e.g., blog post)
├── → Instagram carousel (key points)
├── → LinkedIn post (professional angle)
├── → X thread (bite-sized insights)
├── → YouTube short / Reel (visual summary)
├── → Email newsletter (curated highlight)
└── → LINE message (key takeaway + link)| Date | Platform | Pillar | Topic | Format | Copy Status | Visual Status | Publish Time | |------|----------|--------|-------|--------|------------|--------------|-------------| | Mon 4/7 | IG | Educational | "5 tips for..." | Carousel | Draft | In design | 12:00 | | Tue 4/8 | LinkedIn | Brand | Team spotlight | Photo + text | Approved | Ready | 09:00 |
| Month | Events/Holidays | Content Opportunities | |-------|----------------|---------------------| | Jan | New Year | Year-in-review, goals | | Feb | Lunar New Year (春節) | Holiday greetings, lucky draw | | Mar | White Day, 婦女節 | Gift guides, women's stories | | Apr | 兒童節, Tomb Sweeping | Family content, spring themes | | May | Mother's Day | Gift promotions, mother stories | | Jun | Dragon Boat, 畢業季 | Graduation offers, summer prep | | Jul-Aug | Summer sales | Summer campaigns, travel content | | Sep | Moon Festival (中秋) | Mooncake season, gifting | | Oct | 雙十節 | National pride, promotions | | Nov | 11.11, Black Friday | Major sales events | | Dec | Christmas, year-end | Gift guides, year-end review |
markdown# Content Calendar: {Brand} — {Month} ## Monthly Theme {Overarching theme or campaign} ## Content Plan | Week | Mon | Tue | Wed | Thu | Fri | |------|-----|-----|-----|-----|-----| | W1 | {IG: topic} | {LI: topic} | — | {FB: topic} | {IG: topic} | | W2 | ... | ... | ... | ... | ... | ## Content Details | # | Date | Platform | Pillar | Topic | Format | Owner | Status | |---|------|----------|--------|-------|--------|-------|--------| | 1 | {date} | {platform} | {pillar} | {topic} | {format} | {name} | Draft/Review/Ready | ## KPIs for the Month | Metric | Target | Prior Month | |--------|--------|------------| | Total posts | {N} | {N} | | Engagement rate | {%} | {%} | | Follower growth | +{N} | +{N} | | Traffic from social | {N visits} | {N} |
references/content-analytics.md| Case | Status | Duration (ms) | Turns | Tokens | Tool calls | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Without | With | Δ | Without | With | Δ | Without | With | Δ | Without | With | Δ | ||
case-01 | fail→pass | 20,397 | 15,201 | -25% | 1 | 1 | 0% | 3,617 | 3,888 | +7% | 0 | 0 | — |
case-02 | fail→pass | 31,425 | 17,993 | -43% | 1 | 1 | 0% | 5,349 | 4,349 | -19% | 0 | 0 | — |
case-03 | fail→pass | 34,338 | 19,979 | -42% | 1 | 1 | 0% | 5,388 | 4,613 | -14% | 0 | 0 | — |
case-04 | fail→fail | 19,589 | 16,396 | -16% | 1 | 1 | 0% | 2,689 | 3,492 | +30% | 0 | 0 | — |
case-05 | fail→pass | 17,062 | 16,796 | -2% | 1 | 1 | 0% | 2,728 | 3,891 | +43% | 0 | 0 | — |
case-06 | pass→pass | 17,341 | 20,288 | +17% | 1 | 1 | 0% | 2,551 | 4,366 | +71% | 0 | 0 | — |
case-07 | fail→pass | 20,145 | 22,608 | +12% | 1 | 1 | 0% | 2,861 | 4,551 | +59% | 0 | 0 | — |
case-08 | fail→pass | 16,619 | 15,949 | -4% | 1 | 1 | 0% | 2,299 | 3,920 | +71% | 0 | 0 | — |
case-09 | pass→pass | 18,202 | 16,532 | -9% | 1 | 1 | 0% | 2,423 | 3,716 | +53% | 0 | 0 | — |
case-10 | fail→pass | 12,662 | 10,827 | -14% | 1 | 1 | 0% | 1,895 | 2,796 | +48% | 0 | 0 | — |
case-11 | pass→pass | 16,385 | 13,222 | -19% | 1 | 1 | 0% | 2,265 | 3,346 | +48% | 0 | 0 | — |
case-17 | pass→pass | 10,108 | 4,137 | -59% | 1 | 1 | 0% | 1,499 | 1,943 | +30% | 0 | 0 | — |
case-12 | pass→pass | 13,686 | 12,146 | -11% | 1 | 1 | 0% | 2,153 | 3,205 | +49% | 0 | 0 | — |
case-13 | pass→pass | 15,652 | 16,109 | +3% | 1 | 1 | 0% | 2,102 | 3,582 | +70% | 0 | 0 | — |
case-14 | fail→pass | 11,857 | 7,237 | -39% | 1 | 1 | 0% | 1,897 | 2,521 | +33% | 0 | 0 | — |
case-15 | pass→pass | 17,838 | 17,304 | -3% | 1 | 1 | 0% | 2,583 | 4,423 | +71% | 0 | 0 | — |
case-16 | pass→pass | 20,868 | 19,233 | -8% | 1 | 1 | 0% | 3,121 | 4,486 | +44% | 0 | 0 | — |
case-18 | pass→pass | 18,663 | 16,011 | -14% | 1 | 1 | 0% | 2,816 | 4,050 | +44% | 0 | 0 | — |
case-19 | fail→pass | 10,721 | 11,621 | +8% | 1 | 1 | 0% | 1,819 | 3,175 | +75% | 0 | 0 | — |
case-20 | pass→pass | 10,125 | 10,493 | +4% | 1 | 1 | 0% | 1,482 | 2,644 | +78% | 0 | 0 | — |
case-21 | pass→pass | 13,361 | 14,937 | +12% | 1 | 1 | 0% | 2,548 | 4,027 | +58% | 0 | 0 | — |
case-22 | pass→pass | 14,794 | 13,817 | -7% | 1 | 1 | 0% | 2,077 | 3,432 | +65% | 0 | 0 | — |
DecimalAI ran this skill against gemini-3.6-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 22 cases were attempted. The headline lift of +41 percentage points is the difference between those two pass rates over the 22 comparable cases.
Without the skill loaded, the model failed this case. With it loaded, the same prompt on the same model passed. This is one improved case from the latest verified run; every case, including any that regressed, is in the table above.
Other measured skills in the registry, with their headline benchmark lift.