We run Grok Bot, ChatGPT/Codex, Claude Cowork, and Hermes. The goal is one place for social SOPs and reusable skills — not a different playbook in every chat. Here’s how Composio is supposed to connect those dots, and how far ZipAI actually is today.
Listen & watch: NotebookLM overview
We loaded this ZipAI piece plus three Composio deep-dives into NotebookLM and generated Audio + Video overviews. Keep them as companion media; the article below is the operator brief.
- Claude skills and AI agents (Composio)
- Connect your AI to your apps with MCP
- Add tools to Claude Desktop with one MCP connector
Audio — Give Your AI Agents Hands with MCP (23:12 deep dive)
Video — How the Model Context Protocol Works (~1:16 short)
You know the pattern.
Monday: a Grok Bot agent nails a reply cadence on X. Tuesday: ChatGPT / Codex invents a slightly different version of the same SOP. Wednesday: Claude Cowork or Hermes ships a third script nobody saved. Blotato still publishes fine — but engagement and “how we do this” drift. By Friday you are the human sync layer.
ZipAI lives in that mess on purpose. We run news-desk agents, Zip Yacht ops thinking, WordPress drafts, social packs, calendar work, Drive research dumps — different models, different UIs, same founder. The question isn’t “which LLM is smartest.” It’s: where do the skills live when the model changes?
Are we even doing that yet? (honest status)
Short answer: not fully. As of late September 2026, here’s the real ZipAI / Brian Firth Consulting picture:
- Composio MCP is wired into Grok Bot — agents can search tools and manage connections from that harness.
- Org Skills library is still empty. We have not yet promoted the Zip Yacht / ZipAI playbooks (Blotato publish rules, X reply voice, cross-account boost, FLIBS cadence, etc.) into shared Composio Skills that ChatGPT/Codex, Claude Cowork, and Hermes can all
search → use. - Connect-once auth is partial. Some social accounts are Active under the consulting org; X and several Google toolkits still need a clean Active connection (X still needs real developer API access — Composio does not skip that).
- Publish stays on Blotato. That split is intentional: Blotato for scheduled multi-network publish; Composio for engagement, lookups, and the shared skill spine.
So this post is not a victory lap. It’s the map: what “standardize social + skills across platforms” means, and the checklist to finish wiring it.
What Composio is for (in our stack)
Two layers — both useful, different jobs.
1) Platform playbooks. When an agent calls Composio tool search with a plain-language use case (“open a Slack DM and send a message”), Composio can return tool slugs plus a recommended sequence and known pitfalls. Those ride along with search.
2) Your org’s Skill library. Separately: create, search, and use organization Skills as full SKILL.md documents (YAML frontmatter + Markdown). Search is scoped to the current organization. Use loads one skill by exact slug. That is the founder feature — the difference between “this Grok Bot chat knows our X reply voice” and “Grok Bot, ChatGPT/Codex, Claude Cowork, and Hermes can all pull x-brand-reply.”
Keep secrets out of the markdown. Always.
The harness set we’re standardizing
Stop treating “Grok” and “Cursor” as two products. For operators, the useful split is the agent homes you actually live in:
- Grok Bot — Zip Yacht / ZipAI crew agents, routines, Blotato-adjacent ops.
- ChatGPT / Codex — research, coding, and agent runs that should still hit the same social SOPs.
- Claude Cowork — long-context drafting and desk work with the same skill spine.
- Hermes — another agent harness in the mix; if it can speak Composio MCP (or call the same org Skills), it inherits the library instead of inventing a fifth voice.
Org Skills flip the default: search before you invent. If the library has it, load the slug. If it doesn’t, write the playbook once and every harness inherits it.
ZipAI’s rule of thumb: publish pipelines can stay specialized (Blotato); engagement and cross-app ops should share a Composio skill spine.
Connect once: durable auth across agents
Skills without auth are fan fiction.
Composio sessions tie identity to toolkits and connected accounts. Agents discover tools at runtime. When a toolkit isn’t connected, you get an auth link; once Active, later sessions reuse it. Multiple accounts per app get aliases.
For us that means: connect the house apps under the Brian Firth Consulting Composio project (not a second org under a different Gmail), then let every harness that can talk Composio MCP share that fabric.
Honest limit on X: Composio manages connection lifecycle. It does not abolish Twitter/X developer requirements. “Connect once” is not “keys optional.”
Rube note (2026): Rube was discontinued in May 2026. Don’t build on Rube. Build on Composio sessions / MCP and org Skills.
A practical stack that doesn’t fight itself
| Job | Prefer |
|---|---|
| Scheduled / multi-network publish | Blotato |
| Engagement, lookups, cross-app tools | Composio toolkits + Active connections |
| Long-form CMS | WordPress (zipai.io / zipyacht.com) |
| Agent homes | Grok Bot, ChatGPT/Codex, Claude Cowork, Hermes — all speaking Composio where possible |
| Reusable SOPs | Composio org Skills (SKILL.md) |
How to create, search, and use a skill (operator checklist)
- Search first.
COMPOSIO_SEARCH_SKILLSwith a normal sentence: “draft and post a ZipAI X reply to inbound mentions.” - Use by slug.
COMPOSIO_USE_SKILLwith the exact lowercase-hyphen slug. - Create only when you mean it. Draft a complete
SKILL.md:
---
name: x-brand-reply
description: Reply to X/Twitter mentions in ZipAI voice; search mentions, draft, human-approve, post. Use when engaging inbound social.
---
# Steps
1. Confirm Active X connection (alias if multiple).
2. Fetch recent mentions…
3. Draft in brand voice; do not auto-post without approval…
# Pitfalls
- Don’t put API keys in this file.
- Prefer IDs from tool responses over guessed handles…Then create the Skill with the full markdown (size cap: 65,536 characters).
- Update carefully. Load first, pass the exact skill id, send the complete markdown again.
- Execute with live tools. Skills guide; tool search still supplies current schemas and connection status. Authenticate before you execute.
An empty library is expected until you promote the first few SOPs. The value starts when you stop losing them between harnesses.
Honest limits
- Skills are not a vector database. Searchable markdown playbooks, not embedding memory for every chat ever.
- Don’t store secrets in skill markdown.
- X still needs real API access.
- Two skill concepts. Platform playbooks inside tool search ≠ your org Skill library.
- Harnesses still matter. A skill cannot fix a harness that never calls Composio. Wire MCP once per environment; then the library pays rent.
What we’ll do next (ZipAI)
- Promote 3–5 real Zip Yacht / ZipAI SOPs into Composio org Skills (start with X brand reply + social preview / Blotato handoff).
- Finish Active connections under Brian Firth Consulting (X API keys, then Google where needed).
- Confirm ChatGPT/Codex, Claude Cowork, and Hermes can each search and load the same slugs.
- Keep Blotato as publish; keep human GO on anything that posts.
If you are the human middleware between four agent homes, you are doing the job Composio org Skills were built to retire. Start with one playbook you already trust — save it as a Skill, connect the apps once, and make every harness search before it freestyles.
→ Explore the AI desk at zipai.io · charter ops at zipyacht.com
— Radio · ZipAI AI Automation desk