Open-source skills for PostKing — the AI content platform for social posts, blogs, SEO / GEO, and landing pages.
Drop these into any agent that speaks the SKILL.md standard — Hermes Agent, Claude Code / Claude.ai, OpenAI Codex, Cursor — and your agent gains the full PostKing surface: generate posts, plan content weeks, run SEO / GEO research, ship blog articles, build landing pages, and more.
hermes skills install bitsandtea/postking-skills/postking
hermes chat
> Draft 5 LinkedIn posts about our new pricing.Install any other skill in this repo the same way, swapping the slug: hermes skills install bitsandtea/postking-skills/<slug> (e.g. postking-seo, postking-reddit).
claude plugin marketplace add bitsandtea/postking-skills
claude plugin install postkingThe repo ships a .claude-plugin/marketplace.json so Claude Code can discover and install any of the 10 skills by slug directly from the marketplace.
mkdir -p ~/.claude/skills
cp -r skills/postking ~/.claude/skills/Then in Claude: "Use the postking skill to draft 3 posts about ..."
cp -r skills/postking ~/.agentskills/All skills here are pure SKILL.md + Markdown references — they install with whatever cp or skill-installer your client provides. Swap postking for any other slug from the table below.
Agents that support skill discovery via the agentskills.io well-known convention can list and fetch every skill in this repo from https://try.postking.app/.well-known/skills/index.json (backed by catalog.json), without cloning the repo.
Recommended first install: postking — it's the thin router that picks/confirms the active brand and hands off to whichever specialist skill below owns the task, so most agents only need to install it plus whichever specialist skills the user's workflows touch.
Ten skills, MCP-first. The recommended entry point is postking; the other nine are specialist skills it routes to for first-run setup, social, blog, landing pages, SEO / GEO, campaigns, competitor intelligence, Reddit growth, and brand voice / quality.
| Skill | What it does | Backend |
|---|---|---|
postking |
Thin router — picks/confirms the active brand, then hands off to the right specialist skill below. Install this first. | CLI + MCP |
postking-getting-started |
First-run flow — connect, authenticate, check credits/top-up/subscribe, onboard a first brand, connect socials, ship a first post. | MCP (+ optional CLI) |
postking-social |
Generate, approve, and schedule social posts (LinkedIn, X/Twitter, Instagram, Threads, Facebook); Smart Week cadence; repurposing; visuals; trends. | MCP (+ optional CLI) |
postking-blog |
Blog publications, AI article generation/iteration, publish to PostKing-hosted or external platforms (WordPress, Medium, Substack). | MCP (+ optional CLI) |
postking-landing-pages |
Landing-page generation, editing/vibe-editing, side pages (comparison/text/landing sub-pages), custom domains, publishing. | MCP (+ optional CLI) |
postking-seo |
Full seed-to-publish SEO / GEO pipeline: keyword research, clustering, roadmap, drafting, gap analysis, publish. | MCP (+ optional CLI) |
postking-campaign-launch |
Launch a full marketing campaign (Storylines) end-to-end. | MCP (+ optional CLI) |
postking-competitor-intel |
Discover, register, and analyze a brand's competitors (probe → classify → add → analyze → compare). | MCP |
postking-reddit |
Build a fit-scored subreddit pool, match content to communities with posting angles, and natively rewrite posts for Reddit. | MCP |
postking-brand-voice |
List and apply saved voice profiles, and run the de-slop / AI-detection pass on content. | MCP (+ optional CLI) |
postking drives both the pking CLI and MCP tool calls directly. The other nine are MCP-driven, with an optional pking CLI fast path where one exists — connect postking-mcp (local stdio or hosted at mcp.postking.app) to use them.
The postking skill uses the postking-cli under the hood. First-time setup runs once per machine; the agent handles it for you when you install the skill.
npm install -g postking-cli
pking login # device-code OAuth — paste the code from your browser
pking brand list # confirm everything is wired upThen in your agent:
"Use the
postkingskill to repurpose this URL into LinkedIn and X posts."
The nine specialist skills (postking-getting-started, postking-social, postking-blog, postking-landing-pages, postking-seo, postking-campaign-launch, postking-competitor-intel, postking-reddit, postking-brand-voice) talk to PostKing through the postking-mcp server.
Local stdio:
npm install -g postking-mcp
# Configure your client to launch postking-mcp as an MCP server.Hosted remote MCP:
Point your client at https://mcp.postking.app. See postking-mcp on npm for client-specific configs (Claude Desktop, Cursor, etc.).
postking-skills/
├── .claude-plugin/
│ └── marketplace.json # Claude Code plugin marketplace manifest
├── skills/
│ ├── postking/ # Router skill (recommended entry point)
│ │ ├── SKILL.md
│ │ └── references/commands.md, install.md
│ ├── postking-getting-started/ # First-run: auth, billing, brand onboarding, socials, first post
│ ├── postking-social/ # Social posts, Smart Week, repurposing, visuals, trends
│ ├── postking-blog/ # Blog publications, article generation, publishing
│ ├── postking-landing-pages/ # Landing pages, side pages, custom domains
│ ├── postking-seo/ # SEO / GEO: seeds → clusters → briefs → published articles
│ ├── postking-campaign-launch/ # Storylines-driven campaign launch
│ ├── postking-competitor-intel/ # Competitor discovery, registration & analysis
│ ├── postking-reddit/ # Subreddit pool, content matching, native rewrites
│ └── postking-brand-voice/ # Voice profile listing/application, de-slop / AI-detection
├── assets/icons/ # Per-skill catalog icons (SVG)
├── catalog.json # Machine-readable index for marketplaces
└── README.md
Each SKILL.md follows the agentskills.io specification: YAML frontmatter with name, description, license, compatibility, and metadata (icon + category) — plus a Markdown body with When to Use, Procedure, Pitfalls, and Verification sections. Note: version is NOT a frontmatter field — per-skill versions live in catalog.json.
A skill is plain text instructions for an LLM — no binaries, no servers. When your agent loads a skill, it reads the SKILL.md, follows the procedure, and calls the underlying tool (the pking CLI or the PostKing MCP server) on your behalf.
Progressive disclosure keeps token usage low:
- The agent sees only
name+descriptionat session start (~50 tokens). - When triggered, it reads the
SKILL.mdbody (~150 lines). - For deep details, it loads
references/commands.mdon demand.
Read more about the format at agentskills.io and Hermes Skills docs.
| Client | Format support | How to install |
|---|---|---|
| Hermes Agent | Native | hermes skills install bitsandtea/postking-skills/<slug> |
| Claude Code | Native (plugin marketplace + agentskills.io) | claude plugin marketplace add bitsandtea/postking-skills, or copy to ~/.claude/skills/ |
| Claude.ai | Native | Upload via the /skills UI |
| OpenAI Codex | agentskills.io | cp -r skills/<slug> ~/.claude/skills/ (or your client's skills dir) |
| Cursor | Via MCP | Connect mcp.postking.app |
| Any agentskills.io client | Native | cp -r skills/<slug> ~/.claude/skills/, or fetch via the well-known endpoint |
Pull requests welcome. To add a new skill:
- Create
skills/<your-skill-slug>/SKILL.mdfollowing the agentskills.io spec. - Add an entry to
catalog.json. - Update the table in this README.
- Test it locally with at least one supported client before opening the PR.
Bug reports and feature requests: open an issue.
- postking-cli — the
pkingCLI that backs thepostkingskill. - postking-mcp — the MCP server that backs the workflow skills.
- mcp.postking.app — hosted remote MCP endpoint.
- try.postking.app — sign up for PostKing.
- PostKing API docs — REST surface for direct integrations.
MIT © PostKing.