How do I install the Ops Social Planner skill?

Run npx skillmds@latest add lifecycle-innovations-limited/ops-social-planner in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Ops Social Planner safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: executes scripts, makes network calls, reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Ops Social Planner?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Ops Social Planner free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Ops Social Planner?

Lifecycle-Innovations-Limited (@lifecycle-innovations-limited) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Ops Social Planner by lifecycle-innovations-limited

Name: Ops Social Planner
Rating: 4.2 (5 reviews)
Author: Lifecycle-Innovations-Limited

File contents

/ops-social-planner — engine-agnostic planned-content viewer

Load ops-rules before acting. Public repo (no personal data). Outbound: one draft → one approval → one send. If AskUserQuestion / Workflow are missing, follow Rule 10 in ops-rules (Hermes: numbered options / two-turn Telegram card; delegate_task).

Read-only dashboard of every scheduled post and ad, grouped identity/project → channel → time, regardless of posting engine. Personal/founder identity and project brands stay strictly separated (see /ops-socials identity rules). See SPEC.md for the full design.

What it does

bin/ops-social-planner collect reads $PREFS_PATH/preferences.json (marketing.social_identities.personal.* + marketing.projects.*.social), dispatches a per-engine fetcher keyed on social.engine.primary, normalizes to one schema, and writes $OPS_DATA_DIR/social-planner/state.json (owner data — never committed, Rule 0).
It then serves the static UI (ui/) on localhost and opens the browser.

Engines

`engine.primary`	Source	Status
`typefully`	`GET /v2/social-sets/{id}/drafts` (Bearer; key from `~/.config/typefully/config.json`)	✅ wired
`upload-post`	`GET /api/uploadposts/schedule` (Apikey; key from `engine.upload_post.api_key_ref`)	✅ wired
`meta-graph` / `meta-ads`	Graph Ads API per project BM/token	🔌 hook (UI shows "pending")
`google-ads`	GAQL per project customer id	🔌 hook
`null` / unprovisioned	—	shown fail-closed (0 items)

Adding an engine = adding one fetch<Engine>() in bin/ops-social-planner + a dispatch branch. No UI change.

Run it

"${CLAUDE_PLUGIN_ROOT}/bin/ops-social-planner"                 # collect → serve → open
"${CLAUDE_PLUGIN_ROOT}/bin/ops-social-planner" collect          # regenerate state.json only
"${CLAUDE_PLUGIN_ROOT}/bin/ops-social-planner" serve --port 7937  # serve existing state

The UI renders ui/state.sample.json (synthetic, PII-free) when no live state exists, so it works with zero credentials — useful for the PR preview.

Agent enrichment path (optional, when invoked as a skill)

The headless collector covers posts on wired engines. When richer output is wanted, the agent can:

Pull ads via MCP (mcp__meta__*, Google Ads) per project and merge kind:"ad" items into state.json.
Replace the heuristic rationale with an LLM-written one (slot + sequence + channel intent).
Re-run serve to refresh. Do not publish or edit from here — routing/mutation belongs to /ops-socials + /ops-marketing.

Guarantees

Read-only. No secrets in the client. Server binds 127.0.0.1 only.
Identity separation honored: personal vs project never merged; unprovisioned projects render fail-closed.
No owner data committed — only ui/ + bin/ + SPEC.md + the synthetic fixture.

---name: ops-social-plannerdescription: OPS on-demand: This skill should be used when the user asks to "content calendar", "what is scheduled"…---# /ops-social-planner — engine-agnostic planned-content viewerLoad `ops-rules` before acting. Public repo (no personal data). Outbound: one draft → one approval → one send. If `AskUserQuestion` / `Workflow` are missing, follow Rule 10 in `ops-rules` (Hermes: numbered options / two-turn Telegram card; `delegate_task`).Read-only dashboard of **every** scheduled post and ad, grouped **identity/project → channel → time**,**regardless of posting engine**. Personal/founder identity and project brands stay strictly separated(see `/ops-socials` identity rules). See `SPEC.md` for the full design.## What it does1. `bin/ops-social-planner collect` reads `$PREFS_PATH/preferences.json` (`marketing.social_identities.personal.*` + `marketing.projects.*.social`), dispatches a **per-engine fetcher** keyed on `social.engine.primary`, normalizes to one schema, and writes `$OPS_DATA_DIR/social-planner/state.json` (**owner data — never committed**, Rule 0).2. It then serves the static UI (`ui/`) on localhost and opens the browser.## Engines| `engine.primary` | Source | Status || ------------------------- | -------------------------------------------------------------------------------------- | ---------------------------- || `typefully` | `GET /v2/social-sets/{id}/drafts` (Bearer; key from `~/.config/typefully/config.json`) | ✅ wired || `upload-post` | `GET /api/uploadposts/schedule` (Apikey; key from `engine.upload_post.api_key_ref`) | ✅ wired || `meta-graph` / `meta-ads` | Graph Ads API per project BM/token | 🔌 hook (UI shows "pending") || `google-ads` | GAQL per project customer id | 🔌 hook || `null` / unprovisioned | — | shown fail-closed (0 items) |Adding an engine = adding one `fetch<Engine>()` in `bin/ops-social-planner` + a dispatch branch. No UI change.## Run it```bash"${CLAUDE_PLUGIN_ROOT}/bin/ops-social-planner" # collect → serve → open"${CLAUDE_PLUGIN_ROOT}/bin/ops-social-planner" collect # regenerate state.json only"${CLAUDE_PLUGIN_ROOT}/bin/ops-social-planner" serve --port 7937 # serve existing state```The UI renders `ui/state.sample.json` (synthetic, PII-free) when no live state exists, so it workswith zero credentials — useful for the PR preview.## Agent enrichment path (optional, when invoked as a skill)The headless collector covers posts on wired engines. When richer output is wanted, the agent can:- Pull **ads** via MCP (`mcp__meta__*`, Google Ads) per project and merge `kind:"ad"` items into `state.json`.- Replace the heuristic `rationale` with an LLM-written one (slot + sequence + channel intent).- Re-run `serve` to refresh. Do **not** publish or edit from here — routing/mutation belongs to `/ops-socials` + `/ops-marketing`.## Guarantees- Read-only. No secrets in the client. Server binds `127.0.0.1` only.- Identity separation honored: personal vs project never merged; unprovisioned projects render fail-closed.- No owner data committed — only `ui/` + `bin/` + `SPEC.md` + the synthetic fixture.

Frequently asked questions

Ops Social Planner