# Connect Inklate — let your agent actually publish

Inklate is a social media layer for AI agents: publish, schedule, preflight, engage, and measure across LinkedIn, X, Instagram, Facebook and more through a built-in MCP server.

## Steps

1. Start a free trial (14 days): https://app.inklate.com/login
2. Create an organization API key: dashboard → Settings → API keys → New key.
3. Add the MCP server to your agent config:

```json
{
  "mcpServers": {
    "inklate": {
      "url": "https://api.inklate.com/mcp",
      "headers": { "Authorization": "Bearer inklate_your_org_key" }
    }
  }
}
```

4. Install the Inklate skills: `npx skills add inklate/skills`
5. Say “set up Inklate” — the inklate-setup skill verifies the connection and lists your channels.

## The skills

- **analytics-review** (https://inklate.com/skills/inklate/analytics-review): Run a weekly retro on real numbers: pull the period's posts and their actual metrics from connected channels, say honestly what worked and what didn't, and turn it into three concrete content moves for next week. Covers LinkedIn, X (Twitter), Instagram, and Facebook — each platform reports different metrics, and gaps are shown as gaps. Use when the user says "review my week", "what worked this week", "analytics retro", or asks "how did my posts do". Requires the Inklate MCP connection. Reads social-context.md when present so recommendations tie back to the user's pillars and goals rather than generic growth advice.
- **inbox** (https://inklate.com/skills/inklate/inbox): Work the real social inbox: pull actual comments, mentions, and DMs from connected channels, triage them into buckets (question, praise, objection, lead, spam), and draft on-voice replies ready to paste. Covers LinkedIn, X (Twitter), Instagram, and Facebook. Use when the user says "work my inbox", "check my mentions", "any comments to answer", or "triage my DMs". Requires the Inklate MCP connection. Reads social-context.md when present so drafted replies match the user's voice and red lines. Leads get flagged prominently — the inbox is where revenue hides. Replies are drafted for the user to send, never sent on their behalf.
- **inklate-setup** (https://inklate.com/skills/inklate/inklate-setup): Connect the agent to a real Inklate workspace and prove the connection works end to end. Verifies the MCP link, lists every connected channel across LinkedIn, X (Twitter), Instagram, and Facebook, and fetches the live capability rules for each one. Use when the user says "set up Inklate", "connect Inklate", "verify my Inklate connection", or asks "which channels do I have". Requires the Inklate MCP connection — this skill is the smoke test that every other Inklate skill assumes has already passed. Reads social-context.md when present and offers to pre-fill its Platforms section from the channels that are actually connected. Run this first, once per workspace.
- **preflight** (https://inklate.com/skills/inklate/preflight): Run Inklate's real per-channel validation on a draft or post — the same checks that gate actual publishing, not a generic lint. Fetches each channel's live rules, runs the preflight, explains every violation in plain language, applies the auto-fixes with a before/after, and re-runs until green. Covers LinkedIn, X (Twitter), Instagram, and Facebook. Use when the user says "preflight this", "will this pass", "validate against my channels", or "fix this post for Instagram". Requires the Inklate MCP connection. Reads social-context.md when present so fixes stay on-voice. Ends with a per-channel verdict table — green, fixed-then-green, or blocked with the reason.
- **publish** (https://inklate.com/skills/inklate/publish): Take approved drafts — often written with the cross-post, linkedin-post, or x-thread skills — and ship them for real through Inklate: create the post, sync per-channel variants, validate against each platform's live rules, fix what can be fixed, and publish now or schedule for later. Covers LinkedIn, X (Twitter), Instagram, and Facebook. Use when the user says "publish this", "ship these drafts", "post this to LinkedIn now", or "schedule this post". Requires the Inklate MCP connection. Reads social-context.md when present to keep variants on-voice. Nothing goes out without a green preflight and an explicit yes from the user.
- **schedule-week** (https://inklate.com/skills/inklate/schedule-week): Turn a content plan — often produced by the content-calendar or repurpose skills — into real scheduled placements on the real calendar: parse the plan, map every row to a connected channel, validate each post against live platform rules, propose the full week's schedule, and book it. Covers LinkedIn, X (Twitter), Instagram, and Facebook. Use when the user says "schedule my week", "schedule this plan", "put my calendar on the calendar", or "schedule these posts". Requires the Inklate MCP connection. Reads social-context.md when present for cadence and voice. The receipt is the week as a table of real scheduled times and post IDs, verified against the queue.

Full directory: https://inklate.com/skills · Registry: https://inklate.com/skills/registry.txt