/ Hilda / Overview Team only
Hilda

Overview

What Hilda is, how the pipeline works, and the architecture behind her.
1

What is Hilda?

Hilda is Hedgehog's AI agent team — a system of 20 specialist agents orchestrated by a CEO agent. She handles the end-to-end production of client deliverables: strategy docs, planning reports, content, ad copy, and more. Everything she produces goes through a QA pipeline and sits in a review queue before anything reaches a client.

Hilda is not a single chatbot. She's a coordinated team with defined roles, handoffs, and quality gates.

NHH (Nearly Headless Hilda) is the infrastructure that powers the scheduled/autonomous layer — cron-based tasks, proactive scanning, and pipeline runs. Built and maintained by Teddi.

2

Architecture

Runtime
Node.js on Fly.io (hilda-scheduler)
Entry points
Claude.ai (Cowork), NHH scheduler (automated), Slack bot (@Hilda)
Skills library
60+ .skill files loaded on demand from Google Drive
Task management
ClickUp — all task reads/writes and Doc creation
File output
Google Drive (HH Claude Shared Drive)
Approval flow
All write operations require human approval via Slack card
Proactive scanner
Reads ClickUp tasks only — NOT Slack message history
Slack reads
Only failure-analysis.js reads Slack history (separate scheduled task)
3

The CEO pipeline

  1. CEO Agent receives brief and reads client Source of Truth
  2. Marketing Strategist produces Strategy Brief
  3. Execution agents run (Content, SEO, Paid Media, Email, Graphic Designer — whichever are needed)
  4. Copywriter QA reviews all written output
  5. Brand QA checks against Hedgehog brand guidelines
  6. Data QA cross-references all metrics against source data
  7. Client-Ready Agent packages the final deliverable
  8. Output posted to #hilda-review in Slack for human approval
  9. On approval: saved to Google Drive and linked in ClickUp
4

Entry points

Claude.ai (Cowork)
The primary interface. Type a brief directly. Hilda picks up the skill context and runs.
NHH scheduler (automated)
Scheduled tasks fire on cron — meeting prep, mid-month check-ins, proactive scanning. No human input needed.
Slack @Hilda
Mention @Hilda in a Slack thread to trigger context-aware responses from the NHH bot.
5

Hard rules

  • NHH was built by Teddi — not Josh. This distinction matters for internal comms.
  • The proactive scanner reads ClickUp tasks, not Slack messages. All Slack calls in proactive-scan.js are outbound chat.postMessage only.
  • SIMULATION_MODE must be false for live execution. Check before any Autopilot run.
  • Varnish Cache and HTTPS Redirection must be OFF on Cloudways for static HTML pages.