Theme Factory
anthropics/skills
Applies one of ten preset color and font themes to slide decks, documents or HTML pages, or creates a new theme on the fly after you choose from a showcase.
Produce the Part 8 yearly planner: quarterly themes and monthly initiatives.
MITAuto-check: notes
Install Yearly Planner
$ npx skills add indranilbanerjee/digital-marketing-pro --skill yearly-planner -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install indranilbanerjee/digital-marketing-pro yearly-planner --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/indranilbanerjee/digital-marketing-pro.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/yearly-planner .claude/skills/yearly-planner && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "yearly-planner" agent skill from https://github.com/indranilbanerjee/digital-marketing-pro/tree/main/skills/yearly-planner into .claude/skills/yearly-planner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "yearly-planner", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/indranilbanerjee/digital-marketing-pro/tree/main/skills/yearly-plannerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add indranilbanerjee/digital-marketing-pro --skill yearly-planner -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install indranilbanerjee/digital-marketing-pro yearly-planner --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/indranilbanerjee/digital-marketing-pro.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/yearly-planner .agents/skills/yearly-planner && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "yearly-planner" agent skill from https://github.com/indranilbanerjee/digital-marketing-pro/tree/main/skills/yearly-planner into .agents/skills/yearly-planner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "yearly-planner", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add indranilbanerjee/digital-marketing-pro --skill yearly-planner -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install indranilbanerjee/digital-marketing-pro yearly-planner --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/indranilbanerjee/digital-marketing-pro.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/yearly-planner .cursor/skills/yearly-planner && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "yearly-planner" agent skill from https://github.com/indranilbanerjee/digital-marketing-pro/tree/main/skills/yearly-planner into .cursor/skills/yearly-planner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "yearly-planner", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/indranilbanerjee/digital-marketing-pro.git --path skills/yearly-planner--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add indranilbanerjee/digital-marketing-pro --skill yearly-planner -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install indranilbanerjee/digital-marketing-pro yearly-planner --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/indranilbanerjee/digital-marketing-pro.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/yearly-planner .gemini/skills/yearly-planner && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "yearly-planner" agent skill from https://github.com/indranilbanerjee/digital-marketing-pro/tree/main/skills/yearly-planner into .gemini/skills/yearly-planner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "yearly-planner", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install indranilbanerjee/digital-marketing-pro yearly-plannerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add indranilbanerjee/digital-marketing-pro --skill yearly-planner -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/indranilbanerjee/digital-marketing-pro.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/yearly-planner .github/skills/yearly-planner && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "yearly-planner" agent skill from https://github.com/indranilbanerjee/digital-marketing-pro/tree/main/skills/yearly-planner into .github/skills/yearly-planner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "yearly-planner", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add indranilbanerjee/digital-marketing-pro --skill yearly-planner -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install indranilbanerjee/digital-marketing-pro yearly-planner --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/indranilbanerjee/digital-marketing-pro.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/yearly-planner .opencode/skills/yearly-planner && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "yearly-planner" agent skill from https://github.com/indranilbanerjee/digital-marketing-pro/tree/main/skills/yearly-planner into .opencode/skills/yearly-planner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "yearly-planner", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
yearly-planner- GitHub stars
- 862
- Used in
- 1 other repo
- Token cost
- ~2k tokens
- SKILL.md length
- 764 words
- Files
- 1
- Skills in repo
- 162
- Repo updated
- First seen
- Licence
- MIT
At a glance
Produce the Part 8 yearly planner: quarterly themes and monthly initiatives.
- Works in 8 steps: Read sources → Build the Annual Themes → Detail the Monthly Calendar → …
- SKILL.md covers Pre-conditions, Structure (8 sections), Production process and Quality discipline, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Yearly Planner is an agent skill from indranilbanerjee/digital-marketing-pro. Produce the Part 8 yearly planner: quarterly themes and monthly initiatives. "plan the whole year month by month"
Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: An open-source AI marketing operating system for strategy, SEO, AEO/GEO, paid media, content, CRM, and analytics - grounded in brand context, human approval, and verifiable… The licence is MIT.
Example prompts
- “plan the whole year month by month”
- “/yearly-planner”
Requirements
- Pre-approved tools (allowed-tools): Read, Write, Edit, Bash, Glob, Grep
Workflow steps
8 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 9e949f3. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadWriteEditBashGlobGrep
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Yearly Planner loads about 2k tokens when it runs. Until then it costs about 32 tokens; SKILL.md has 764 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
allowed-tools: Read, Write, Edit, Bash, Glob, Grep
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from indranilbanerjee/digital-marketing-pro at commit 9e949f3, republished under its MIT licence (© indranilbanerjee). 764 words, ~1,964 tokens.
Download SKILL.mdSave it as
.claude/skills/yearly-planner/SKILL.md (or your agent's skills folder).- name
- yearly-planner
- description
- Produce the Part 8 yearly planner: quarterly themes and monthly initiatives. "plan the whole year month by month"
- allowed-tools
- Read, Write, Edit, Bash, Glob, Grep
- user-invocable
- true
- engagement-part
- 8
- view-preference
- v2-primary
/digital-marketing-pro:yearly-planner — Part 8 Operational Companion
The Yearly Planner complements the Growth Plan with a 12-month operational calendar that ties strategy to date-by-date execution. If the Growth Plan answers "How will we grow this business?", the Yearly Planner answers "What will we do, week by week, month by month?"
Specification: yearly-planner-template.md — the canonical structure.
Pre-conditions
The Yearly Planner is produced after the Growth Plan. It operationalises the Growth Plan's strategic decisions.
Before producing, verify:
- Growth Plan completed at
part-08-growth-plan/growth-plan.md - Part 7 preparation documents available (campaign architecture, content pillars, KPI tree)
- Living Project Instruction File current
- Brand profile specifies geographic operations (so seasonal context can be applied)
Structure (8 sections)
| # | Section | Source |
|---|---|---|
| 1 | Annual Themes | Synthesis of Growth Plan strategy across 4 quarters |
| 2 | Monthly Calendar | 12 monthly sub-sections; Growth Plan Section 8 expanded |
| 3 | Seasonal Strategy | Industry + cultural / festival seasonality (regional context) |
| 4 | Campaign Architecture | Part 7 campaign architecture detailed by quarter |
| 5 | Content Pillars Calendar | Core Doc 3.3 messaging pillars × Part 7 content pillars |
| 6 | Channel-Specific Cadence | One sub-section per active channel family |
| 7 | Resource & Budget Pacing | Quarterly budget pacing + resource plan |
| 8 | Quarterly Review Schedule | QBR dates + decision authority per reporting-cadence.md |
Production process
Step 1: Read sources
- Growth Plan (canonical version)
- Living Project Instruction File
- Part 7 preparation documents
- Brand profile (for geography → seasonality)
- For India-operating brands: india-market-context.md
Step 2: Build the Annual Themes
Identify 4 quarterly themes that organise the year. Each theme is one sentence with strategic rationale and ladders into the overall positioning. Themes might be (this is one example pattern, customise per engagement):
- Q1: Foundation + initial demand capture
- Q2: Demand generation activation
- Q3: Account expansion + community
- Q4: Festive surge + awards / press push
Step 3: Detail the Monthly Calendar
12 sub-sections, ~1 page each. For each month:
- Theme — one sentence summary
- Major initiatives — 2-4 specific initiatives with owner and deadline
- Always-on activity — what continues from the prior month (paid ads at fixed budget, organic posting cadence, email programme, SEO content production)
- Key dates — product launches, industry events, holidays / festivals relevant to the brand, planned PR moments
- Content calendar overview — themes per week, content pillars covered, target volume per channel
- Budget — monthly fixed spend by channel, variable budget reserve
- KPI targets — primary + 2-3 secondary KPIs for the month
Step 4: Map Seasonal Strategy
For India-operating brands, reference the seasonality table from india-market-context.md:
- Dussehra → Diwali (Sept-Nov) festive peak
- Wedding season (Nov-Feb)
- End of financial year (Jan-Mar) — B2B budget spend
- Back-to-school (Apr-Jun)
- Monsoon (Jun-Sep)
- Cricket / IPL season (Mar-May)
For other markets, apply equivalent seasonality. For B2B globally, fiscal year-end and major industry events are universal seasonality drivers.
Step 5: Map Campaign Architecture
The Part 7 campaign architecture document defines the year's major campaigns. The Yearly Planner places each campaign in its calendar slot with:
- Campaign name + theme
- Target persona
- Primary channels
- Timing (start, peak, wind-down)
- KPIs
- Expected outcome
Show full SKILL.md (291 more words)Show less
Step 6: Map Content Pillars Calendar
The 3-5 content pillars from Core Doc 3.3 are scheduled across the year:
- Per-pillar production target for the year (volume per format)
- Quarterly distribution (how content mix shifts)
- Repurposing flow (long-form blog → social posts → video → email)
Step 7: Map Channel-Specific Cadence
For each active channel family:
- Posting / sending / publishing cadence (e.g., LinkedIn: 4 posts/week; Email: 1 broadcast/week + lifecycle flows; SEO: 6 articles/month)
- Volume targets for the year
- Quarterly emphasis shifts
- Resource requirements (creative production, copywriting, design, video)
Step 8: Produce companion files
The Yearly Planner is delivered as:
yearly-planner.md(canonical)yearly-planner.pdf(client distribution viapdf-generator.py)yearly-planner.xlsx(calendar in spreadsheet form for ongoing operational use)
Save all to engagements/{id}/part-08-growth-plan/.
Quality discipline
- Every initiative has an owner. "Marketing team will do X" is not actionable.
- Every quarter has measurable KPI targets. "Improve traffic" is not a target.
- Always-on activity distinguished from initiatives. Always-on is the baseline; initiatives are time-bounded efforts on top.
- Realistic capacity respected. Sequence prevents burnout.
- Living document. Reviewed and adjusted at each Quarterly Business Review.
- Aligns with Growth Plan. No contradictions between the two.
After production
- Save all formats to
part-08-growth-plan/ - Mark Part 8 fully completed via
engagement-state.py mark-part-completed --part 8 - Update LIF: Engagement phase = "Strategy approved; Channel Build (Part 9) ready to begin"
- Brief: "Yearly Planner complete. Operational calendar covers 12 months with quarterly themes, monthly initiatives, and channel-specific cadence. Recommend reviewing with the client before kicking off Part 9 channel build. /digital-marketing-pro:engagement next to advance."
Examples
Example 1: Standard Yearly Planner production
User: Produce the Yearly Planner for Acme.
Skill response:
1. Verify Growth Plan exists ✓; Part 7 preparation docs available ✓
2. Read Growth Plan, Part 7 docs, brand profile (geography: India)
3. Apply India seasonality: Q3 includes Dussehra-Diwali surge planning; Q4 includes wedding season prep
4. Build 4 quarterly themes
5. Detail 12 monthly sections with initiatives, dates, budget, KPIs
6. Schedule 6 major campaigns across the year (Q1: launch; Q2: growth-acceleration; Q3: festive; Q4: awards-PR push)
7. Map content pillars: Pillar A 40%, B 25%, C 20%, D 15% of annual production
8. Generate markdown + PDF + XLSX
9. Mark Part 8 complete
10. Brief: "Yearly Planner complete. 12 months, 6 major campaigns, 48 content pieces planned, 4 quarterly review checkpoints. Festive season Q3 has 2x normal budget pacing per Diwali surge. /digital-marketing-pro:engagement next moves to Part 9."Related skills
growth-plan— companion deliverable; produced firstengagement-workflow— orchestrates Part 8
Related references
- yearly-planner-template.md — canonical structure
- growth-plan-template.md — companion deliverable
- india-market-context.md — seasonality
- reporting-cadence.md — Section 8 QBR cadence
- fixed-vs-variable-budget.md — monthly budget structure
© indranilbanerjee, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/yearly-planner of indranilbanerjee/digital-marketing-pro.
Open the folder on GitHubat commit 9e949f3
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in indranilbanerjee/digital-marketing-pro, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Yearly Planner next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Yearly Planner this skillindranilbanerjee/digital-marketing-pro | 862 | 1 repos | ~2k | Automated safety check: Notes | MIT | |
| Theme Factoryanthropics/skills | 180k | 47 repos | ~781 | Automated safety check: Pass | Apache-2.0 | |
| Plannerpenpot/penpot | 61k | — | ~2.7k | Automated safety check: Pass | MPL-2.0 | |
| Theme Factorynexu-io/open-design | 100k | — | ~329 | Automated safety check: Pass | Apache-2.0 | |
| Pierre Theme Packagepierrecomputer/pierre | 6.3k | — | ~352 | Automated safety check: Pass | Apache-2.0 | |
| Pierre Theming Librarypierrecomputer/pierre | 6.3k | — | ~661 | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
Planner
penpot/penpot
Read-only planning and architecture analysis — produce a structured implementation plan with task breakdown, acceptance criteria, sizing, and checkpoints.
Theme Factory
nexu-io/open-design
Apply professional font and color themes to artifacts including slides, docs, reports, and HTML landing pages.
Pierre Theme Package
pierrecomputer/pierre
Shows an agent how to install and use the @pierre/theme package, which ships ten Pierre light and dark color themes for Shiki and VS Code.
Pierre Theming Library
pierrecomputer/pierre
Explains how to use the @pierre/theming package to list, resolve, select, switch and persist themes, with controller, color and React references.
Agent Planner
ruvnet/ruflo
Agent skill for planner - invoke with $agent-planner. An agent skill from ruvnet/ruflo.
More from indranilbanerjee/digital-marketing-pro
All 162 skills in this repoImport Template
indranilbanerjee/digital-marketing-pro
Import a deliverable template as a reusable placeholder template per brand.
Ab Test Plan
indranilbanerjee/digital-marketing-pro
Plan an A/B test by script: sample size per variant, days to run, stopping rules.
Aeo Audit
indranilbanerjee/digital-marketing-pro
Run a one-time AEO audit of six AI answer engines, scored per surface.
Agent Readiness Audit
indranilbanerjee/digital-marketing-pro
Audit agent readiness by script: AI-crawler rules, product schema, no-JS HTML, feeds.
Backlink Gap
indranilbanerjee/digital-marketing-pro
Find backlink gap domains linking to competitors, not you, scored by script.
C2pa Metadata
indranilbanerjee/digital-marketing-pro
Embed C2PA provenance in AI-generated images, video or PDF by script.
Questions about Yearly Planner
What does Yearly Planner do?
Produce the Part 8 yearly planner: quarterly themes and monthly initiatives. Yearly Planner is an agent skill from indranilbanerjee/digital-marketing-pro. Produce the Part 8 yearly planner: quarterly themes and monthly initiatives.
How do I install Yearly Planner in Claude Code?
Run `npx skills add indranilbanerjee/digital-marketing-pro --skill yearly-planner -a claude-code`. Or copy the skill folder (skills/yearly-planner in indranilbanerjee/digital-marketing-pro) into .claude/skills/yearly-planner in your project. Claude Code loads it when a task matches its description.
How do I install Yearly Planner in Codex?
Run `npx skills add indranilbanerjee/digital-marketing-pro --skill yearly-planner -a codex`. Or copy the skill folder (skills/yearly-planner in indranilbanerjee/digital-marketing-pro) into .agents/skills/yearly-planner in your project. Codex loads it when a task matches its description.
Can I use Yearly Planner in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add indranilbanerjee/digital-marketing-pro --skill yearly-planner -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/yearly-planner, .gemini/skills/yearly-planner, .github/skills/yearly-planner and .opencode/skills/yearly-planner in your project.
What does Yearly Planner need to run?
SKILL.md names no scripts, command-line tools or credentials: Yearly Planner is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Write, Edit, Bash, Glob, Grep.
Does Yearly Planner access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Yearly Planner safe to install?
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Yearly Planner use?
Yearly Planner is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Yearly Planner use?
About 2k tokens (SKILL.md is roughly 7.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Yearly Planner?
Skills that share tags, products or a category with Yearly Planner: Theme Factory (anthropics/skills, 180k stars), Planner (penpot/penpot, 61k stars), Theme Factory (nexu-io/open-design, 100k stars) and Pierre Theme Package (pierrecomputer/pierre, 6.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Yearly Planner?
indranilbanerjee (a GitHub user) maintains it in indranilbanerjee/digital-marketing-pro, which has 862 GitHub stars. The repository holds 162 skills in this directory. The repository was last updated on October 9, 2026.
Source: indranilbanerjee/digital-marketing-pro on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.