Agents Overview

Nucleus includes a suite of autonomous agents that work behind the scenes to keep the team informed and reduce manual busywork. Each agent runs as a Cloudflare Worker and communicates through Slack.

Meet the Agents

Agent	Slash Command	What It Does
Resourcing	/resourcing	Tracks team utilisation, capacity, and allocation across squads
Analytics	/analytics	Surfaces business metrics — billable hours, deal pipeline, budget health
Marketing	/marketing	Manages the content pipeline and captures story moments from Slack
Product	/product	Collects product feedback and keeps the team updated on releases
Release Manager	/release	Automates the PR-to-production pipeline with QA gates
Insights	/insights	GA4 web analytics — traffic, content, devices, ecommerce for all client properties
QA Agents	(automatic)	Reviews every PR for technical quality and UX conventions

How They Work

All agents share a single Slack app. When you type a slash command, Slack sends it to a central router which forwards it to the right agent. Each agent can also run on a schedule — posting weekly digests, daily alerts, or checking for issues automatically.

Slash Commands

Every agent responds to a slash command in Slack. Type the command with help to see what’s available:

/resourcing help
/analytics help
/marketing help
/product help

Scheduled Reports

Agents post reports on a schedule so you don’t have to ask:

When	What
Monday morning	Weekly resourcing report (utilisation by squad)
Monday morning	Weekly analytics digest (billable hours, pipeline, risks)
Monday morning	Weekly content review (marketing pipeline health)
Friday afternoon	Weekly release communications
Every morning	Capacity alerts (over/under-allocation warnings)
Every morning	Content pipeline check
Every 30 minutes	PR status checks and deploy monitoring

AI-Powered Insights

Several agents use Claude to go beyond raw numbers:

• /resourcing ask <question> — “Who has capacity next week for a new project?”
• /analytics ask <question> — “Which squads are trending below target?”
• /insights ask <property> <question> — “What is the % of sessions mobile vs desktop for the last 12 months?”
• Weekly reports include AI-generated analysis highlighting risks and recommendations

Permissions

Agents authenticate using internal service bindings — they don’t need your login credentials. The data they access follows the same permission model as the Nucleus app, scoped to what each agent needs.

Architecture

Each agent is an independent Cloudflare Worker in apps/agents/. They communicate with the main Nucleus app via Cloudflare Service Bindings (direct Worker-to-Worker calls) and with external services (Slack, Productive, Claude) via their respective APIs.

The Slack Router (apps/agents/slack-router/) handles all incoming Slack events and dispatches them to the correct agent based on the command or action type.