Turns one approved Notion source into channel-specific drafts, checks claims and voice, pauses before publication, and returns a ready-to-schedule content package.
Designed for
Small marketing and founder teams that want consistent multi-channel output without paying for a separate content automation stack
Operating goal
Create a reviewed content package from one trusted source while preventing unsupported claims and accidental publishing.
4 steps from trigger to verified handoff, with success and failure paths.
1 MCP layer and 1 connected tools with explicit auth and risk levels.
3 guardrails, 3 evals, and 1 harnesses before production use.
Builds a claim-safe source brief from the connected page.
Long-context editing model
Adapts the source into distinct channel drafts.
High-quality writing model
Checks each draft against the source before handoff.
Critical review model
Loads the workflow goal, allowed actions, escalation policy, and output contract before the agent plans work.
A workflow skill that captures the operating contract, tool boundaries, and escalation rules for ContentRelay: Content Repurposing Team.
Centralizes high-risk action checks for writes, secrets, customer data, billing, deploys, and public communications.
Exposes task resources, prompt templates, connector tools, and audit records behind a permission-aware boundary.
Read the selected Notion source and extract only supported claims, voice, audience, and CTA.
Create distinct drafts for the channels named in the trigger payload.
Map material claims back to the connected source and prepare publication notes.
Approve the reviewed package for downstream scheduling or publishing.
Open it in Codelit, refine it with the agent chat, then generate the architecture or product plan from the same workflow spec.
Open in Agent WorkflowQualifies an inbound lead against the team's real ICP, explains the score, pauses on ambiguous routing, and returns a signed handoff to the CRM or automation that sent it.
Screens a candidate against a role rubric, records evidence for every criterion, pauses before a shortlist decision, and returns a structured recruiter handoff.
A Slack-native engineering agent that receives operational requests, gathers context from tickets and repos, routes work to specialist agents, and drafts auditable responses before anything risky happens.