content-planner
Plan and organize your content calendar with AI-driven scheduling and topic suggestions.
git clone --depth 1 https://github.com/holaboss-ai/holaOS /tmp/content-planner && cp -r /tmp/content-planner/apps/desktop/electron/default-skills/content-planner ~/.claude/skills/content-plannerSKILL.md
# Content Planner Plan like a content strategist building a calendar the team can actually execute. A good plan balances variety, consistency, and intent — every slot has a reason to exist, and the whole thing ladders up to a goal. ## When to use this skill Use Content Planner to build weekly or monthly content calendars: what to post, when, on which platform, and why. It suggests topics, posting cadence, and content mix. If the task is generating raw ideas without scheduling, use Idea Generator; if it's writing the posts themselves, use Content Writer. ## Planning principles - **Goal first.** Anchor the calendar to an objective (growth, engagement, launch support). Every slot should serve it. - **Mix on purpose.** Balance content types — educational, entertaining, promotional, community/UGC — so the feed isn't all sell or all fluff. A common starting ratio is roughly 3 value posts to 1 promotional, tuned to the brand. - **Cadence the audience can sustain.** Consistency beats bursts. Set a realistic frequency per platform and hold it. - **Time to the audience.** Schedule around when this audience is active and around real events, campaigns, and seasonality. - **Platform-native.** Tailor format and frequency to each platform rather than cross-posting blindly. ## How to build the plan 1. Confirm goals, platforms, posting frequency, audience behavior, and any fixed dates (launches, events, holidays). 2. Set the content mix and cadence per platform. 3. Map specific topics/themes to dates, distributing categories so no week is lopsided. 4. Assign each slot a format, platform, and suggested time, and note the campaign or theme it supports. 5. Leave deliberate slack for timely/reactive content rather than packing every slot. ## Output format Deliver a calendar that's ready to act on, typically a table or dated list with columns for: date, platform, content type/theme, topic or hook, format, and suggested posting time. Open with a short note on the plan's strategy — the goal, the mix ratio, and the cadence — so the reader understands the logic before the grid. Call out where flexibility is built in.
Build a new holaOS app using @holaboss/app-builder-sdk (5 backend primitives + optional shadcn dashboard UI). The canonical path for vibe-coded apps — integration modules AND dashboard apps both live here.
Use when working in the embedded browser and you want the cheapest reliable interaction loop.
Use when validating or debugging a workflow in the embedded browser and you need a reproducible, evidence-first loop.
Build the visual layer of a holaOS dashboard app — TanStack Start + @holaboss/ui + workspace tokens. Use when an app has SDK primitives wired (via app-builder-sdk) AND needs a `src/client/` UI surface. NOT for marketing pages, NOT for snapshot HTML reports.
Provision a production-ready teammate only after its stable responsibilities, prerequisites, and reusable operating guidance are understood.
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications. Generates creative, polished code that avoids generic AI aesthetics.
This skill is for interface design — dashboards, admin panels, apps, tools, and interactive products. NOT for marketing design (landing pages, marketing sites, campaigns).
Add or update workspace MCP servers using holaOS mcp_registry syntax.