Ops Social Planner

Organization

Lifecycle-Innovations-Limited

ops-social-planner

OPS on-demand: This skill should be used when the user asks to "content calendar", "what is scheduled"…

Overview

Publisher	Lifecycle-Innovations-Limited
Repository	`claude-ops`
Skill name	`ops-social-planner`
Stars	543
Forks	64
Bundled files	6
License	MIT
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
6 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by Lifecycle-Innovations-Limited on GitHub. Read the source before you install it.

Installation

Install the Ops Social Planner AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/Lifecycle-Innovations-Limited/claude-ops/tree/main/claude-ops/skills/ops-social-planner
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/Lifecycle-Innovations-Limited/claude-ops/tree/main/claude-ops/skills/ops-social-planner

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/Lifecycle-Innovations-Limited/claude-ops.git /tmp/claude-ops
mkdir -p .claude/skills
cp -r /tmp/claude-ops/claude-ops/skills/ops-social-planner .claude/skills/ops-social-planner

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Ops Social Planner in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Ops Social Planner on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Ops Social Planner is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

/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

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 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.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Ops Social Planner AI skill do?

OPS on-demand: This skill should be used when the user asks to "content calendar", "what is scheduled"…

Why use Ops Social Planner on TypingMind?

Because you install it once and use it with any model. Ops Social Planner is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Ops Social Planner in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Lifecycle-Innovations-Limited/claude-ops/tree/main/claude-ops/skills/ops-social-planner. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Ops Social Planner?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Ops Social Planner?

As many as you like. As long as a model supports skills, you can use Ops Social Planner with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Ops Social Planner AI skill free?

Yes. It is published on GitHub by Lifecycle-Innovations-Limited under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Improve Codebase Architecture

mattpocock

CommunityPopular

Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

Grilling

Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.

Teach

Teach the user a new skill or concept, within this workspace.

Api Design

Patrones de diseño REST API incluyendo nomenclatura de recursos, códigos de estado, paginación, filtrado, respuestas de error, versionado y rate limiting para APIs de producción.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

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

What it does

Engines

Run it

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

Guarantees

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now