chieflab.io

FIRST TOOL — call before anything else when you don't know what ChiefLab does or where to start.

Outcome-named alias for chiefmo_launch_product.

Connect a third-party provider (Zernio, Resend, GA4, Search Console, HubSpot, Stripe, Linear, Notion, Slack) to this workspace.

P13 — re-check a blocked publishAction's connector readiness.

USE WHEN any launch action carries a manualFallback brief — either because the channel has no automated provider at all (Product Hunt, Hacker News, Reddit, Discord, Slack, Indie Hackers, dev.to, YC Bookface, blog) OR because the channel HAS an automated provider but its connector isn't wired yet for this workspace (LinkedIn / X without a Zernio key; email without a Resend key + verified sender domain).

P88 — set the workspace's persistent company profile.

P88 — read the workspace's stored company profile.

P87 — list the specialist agents ChiefLab can delegate to (design / video / research / outreach / seo / analytics).

P87 — delegate to a specialist agent.

P93 — admin escape hatch.

P91 — verify the persistent stores.

P80 — query the persistent proof ledger.

P79 — set per-workspace publishing target defaults so chiefmo_approve_action({ autoExecute: true }) doesn't need the agent to pass platform / recipient ids on every call.

P79 — read the workspace's stored publishing target defaults.

P75 — Next Move Engine.

P75 — turn a Next Move suggestion into an approval-gated draft action.

P72 — regenerate a single visual asset (LinkedIn graphic, X graphic, landing hero, etc.) with a different style / fidelity / headline / model.

P116 — paste-what-you-see metric fallback for channels without public-API measurement (X, LinkedIn, Email, landing pages, Product Hunt).

P115 — pull a Reddit post's score + comments + upvote ratio + top replies via the public Reddit JSON API and write them to the action's metadata.proof.

P109 — pull a Hacker News post's score + comments + top replies via the public HN API and write them to the action's metadata.proof.

P104 — approve or reject a single visual asset (LinkedIn graphic / X image / landing hero / Product Hunt gallery / carousel slide).

P71 — closed-loop executor wrapper.

P71 — measurement queue inspector.

P142 — founder rejects a next-move recommendation without doing it.

P135 — mark a next-move action as completed when the founder has done the move BUT there's no URL to record (e.g.

USE WHEN the user has manually posted to a channel returned by chieflab_use_manual_fallback (Product Hunt / HN / Reddit / Discord / etc.) and wants to feed the live URL back to ChiefLab so the closed loop continues.

USE WHEN the user just completed a connector OAuth flow and you want to confirm it succeeded — 'did my connection work?', 'is my Zernio/HubSpot/Stripe connected?'.

USE WHEN the user has no ChiefLab API key yet and you've gotten a 401 / 'authentication required' error from any other tool.

Operator: chieflab-launch (primary).

USE WHEN the user says 'make this more casual' / 'shorter' / 'less salesy' / 'add a specific number' / 'redraft this' about a published draft.

Store a provider API key for THIS workspace.

USE WHEN the user asks 'what came in from my launches?' / 'show me my replies' / 'what's in my inbox?' / 'who responded to the LinkedIn post?'.

SESSION-RECOVERY · FIRST CALL when a session starts and the user mentions launch / users / growth / customers / metrics / revenue / marketing / what next / shipping.

Alias of chieflab_status.

POST-INSTALL HEALTH CHECK.

USE WHEN the user asks 'what do you remember about my brand?' / 'show me my brain' / 'what have you learned?'.

USE WHEN your operator needs a capability outside its own scope and wants to find another operator that can fulfill it — 'find me a demo-video capability', 'who can do SEO audits', 'search for design help'.

USE WHEN you have a specific operatorId + capability and want the full machine-readable profile (inputs, outputs, pricing, approval-required flag, endpoint).

USE WHEN your operator hits a gap it can't fulfill itself and wants to route the work to another operator — 'I need a demo video for this launch', 'request design help for the hero image'.

[chieflab_* alias of chiefmo_approve_action] Approve one ChiefMO publish/send action so its executor can fire.

[chieflab_* alias of chiefmo_continue_launch_loop] Resume a ChiefLab launch loop from runId.

[chieflab_* alias of chiefmo_post_launch_review] USE WHEN ≥24h has passed since chiefmo_publish_approved_post fired and the user asks 'how did the launch perform?', 'what worked?', 'metrics from my launch'.

[chieflab_* alias of chiefmo_prepare_next_move] USE WHEN the user has just published a launch (or ≥24h post-launch) and asks 'what's next?', 'follow-up post?', 'iterate on this', 'plan day 2'.

[chieflab_* alias of chiefmo_publish_approved_post] Publish an approved social post (LinkedIn / X / Threads / Instagram / Facebook / Bluesky / TikTok) through the social publishing rail (current adapter: zernio).

[chieflab_* alias of chiefmo_send_approved_email] Send an approved launch email through the email sending rail (current adapter: resend).