content-calendar
$
npx mdskill add mohitagw15856/pm-claude-skills/content-calendarThis skill generates a structured content calendar from brand inputs. It produces ready-to-use calendar entries with topics, formats, channels, and opening hooks — usable for social media, blogs, newsletters, or multi-channel campaigns.
SKILL.md
.github/skills/content-calendarView on GitHub ↗
--- name: content-calendar description: "Generate a structured content calendar for any brand, product, or creator. Use when asked for a content plan, editorial calendar, social media schedule, or weekly/monthly content strategy. Produces a calendar with topics, formats, channels, and copy hooks." --- # Content Calendar Skill This skill generates a structured content calendar from brand inputs. It produces ready-to-use calendar entries with topics, formats, channels, and opening hooks — usable for social media, blogs, newsletters, or multi-channel campaigns. ## Required Inputs Ask the user for these if not provided: - **Brand or product name** - **Target audience** (who are you trying to reach?) - **Primary content goal** (awareness / lead gen / retention / thought leadership) - **Channels** (e.g. LinkedIn, Instagram, newsletter, blog, X/Twitter) - **Cadence** (daily / 3x per week / weekly / monthly) - **Timeframe** (e.g. 4 weeks, Q2) - **Brand pillars or themes** (optional — if not provided, derive 3 from the product description) ## Output Structure ### 1. Content Pillars (if not provided) Derive 3–4 content pillars from the brand/product description. Each pillar = a recurring theme that anchors multiple posts. Label each one clearly (e.g. "Pillar 1: Industry Education", "Pillar 2: Product Stories"). ### 2. Calendar Table Produce a weekly table for each week requested. Format: | Date | Pillar | Topic | Format | Channel | Opening Hook | |---|---|---|---|---|---| | Mon 7 Apr | Education | [Topic title] | Carousel / Article / Short video / Thread | LinkedIn | [First sentence or headline of the post] | Rules: - Rotate through all pillars across the week — don't stack the same pillar on consecutive days - Match format to channel norms (e.g. carousels for Instagram, long-form for LinkedIn, threads for X) - Opening hooks must be specific and scroll-stopping — no generic openers like "Did you know..." - Flag 1–2 posts per week as "High Priority" — these are the cornerstone pieces worth boosting or repurposing ### 3. Repurposing Map For each "High Priority" post, add one repurposing suggestion — e.g. "Turn this LinkedIn article into a newsletter section" or "Clip this video for an Instagram Reel." ## Quality Checks - [ ] Every week has balanced pillar distribution - [ ] No two consecutive posts have the same format on the same channel - [ ] Opening hooks are specific (no generic openers) - [ ] Formats match platform norms - [ ] Repurposing map covers all High Priority posts ## Example Trigger Phrases - "Build me a 4-week content calendar for [brand]" - "Create a social media plan for [product launch]" - "Give me a monthly editorial calendar for my newsletter" - "Plan my LinkedIn content for the next month"
More from mohitagw15856/pm-claude-skills
- 360-feedback-templateDesign a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.
- ab-test-plannerDesign statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.
- accessibility-auditGenerate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.
- account-planBuild a structured account plan for any key customer or target account. Use when asked to create an account plan, key account strategy, strategic account review, or territory plan. Produces a complete account plan with relationship map, growth opportunities, risks, and 90-day action plan.
- aeo-optimizerOptimize an article for Answer Engine Optimization (AEO) — restructuring content so AI engines like ChatGPT, Perplexity, and Claude can extract, quote, and cite it. Rewrites headings as questions, drops 50-80 word answer capsules, audits paragraph length, and flags trust signals. Use when asked to AEO-optimize, make content AI-readable, improve AI citation chances, or adapt an article for answer engines.
- ai-ethics-reviewConduct an ethical review of an AI or ML feature, model, or product. Use when asked to run an AI ethics review, assess AI risks, audit a model for bias, or produce an AI impact assessment. Produces a structured ethics review covering fairness, transparency, privacy, safety, accountability, and societal impact with prioritised mitigations.
- ai-product-canvasStructure AI and ML product decisions with the rigour of any product decision. Use when building AI-powered features, evaluating LLM integrations, designing AI products, or assessing AI readiness. Produces a complete AI product canvas covering problem definition, model approach, data requirements, evaluation framework, UX design, responsible AI checklist, and launch monitoring plan.
- ambiguity-resolverStructure vague opportunities and unclear briefs into actionable one-page problem statements. Use when asked to clarify a vague brief, frame an undefined problem, make sense of an unclear opportunity, or when the user says 'we need to figure out what to do about X' or 'I've been asked to look into Y'. Produces a structured problem brief with reframed questions, scoped boundaries, and a minimum viable research plan.
- api-docs-writerWrite clear, developer-facing API documentation. Use when asked to document an API endpoint, write API reference docs, create a developer guide, or turn a raw spec/Postman collection into documentation. Produces endpoint documentation with descriptions, parameters, request/response examples, and error codes.
- api-versioning-strategyWrite an API versioning strategy document for a service or API platform. Use when asked to define versioning policy, plan API deprecation, classify breaking changes, or document version lifecycle. Produces a complete versioning strategy with breaking-change classification table, deprecation timeline, migration guide template, and client communication template.