Formát špecifikácie agenta

Formát špecifikácie agenta

Agenti Tajo sú definovaní v markdown súboroch. Každý súbor obsahuje YAML frontmatter (identita, nástroje, obmedzenia) a markdown telo (inštrukcie, stratégia, pravidlá). Tento formát je inšpirovaný produkčnými vzormi agentov používanými v systémoch multi-agent orchestrácie.

Štruktúra súboru

---
name: agent-name
description: Čo tento agent robí (max 160 znakov)
version: 1.0.0
temperature: 0.2
max_tokens: 4096
tools:
- brevo_contacts
- brevo_email_campaign_management
- brevo_sms_campaigns
triggers:
- event: cart_abandoned
- schedule: "0 */4 * * *"
permissions:
- contacts:read
- email:send
- sms:send
---
# Názov agenta
Inštrukcie pre agenta v prirodzenom jazyku...

Polia Frontmatter

Povinné polia

PoleTypPopis
namestringJedinečný identifikátor v kebab-case (napr. cart-recovery-agent)
descriptionstringČo tento agent robí (max 160 znakov)
versionstringSémantická verzia (napr. 1.0.0)
toolsarrayModuly Brevo MCP servera, ku ktorým má tento agent prístup

Behaviorálne polia

PoleTypPredvolená hodnotaPopis
temperaturefloat0.3Teplota LLM. Nižšia = deterministickejšia. Použite 0.1-0.2 pre dátové operácie, 0.3-0.5 pre návrh kampaní
max_tokensinteger4096Maximálna dĺžka odpovede na otočku
modelstringclaude-sonnet-4-6LLM model na použitie

Polia spúšťačov

PoleTypPredvolená hodnotaPopis
triggersarray[]Udalosti, plány alebo webhooky, ktoré aktivujú tohto agenta
triggers[].eventstring-Názov udalosti (napr. cart_abandoned, customer_created)
triggers[].schedulestring-Cron výraz (napr. 0 9 * * * pre každý deň o 9:00)
triggers[].webhookstring-Cesta webhooku (napr. /agents/cart-recovery/trigger)
triggers[].conditionsarray[]Podmienky filtrovania pre spúšťač
triggers[].debouncestring-Okno debounce (napr. 5m, 1h)

Polia oprávnení

PoleTypPredvolená hodnotaPopis
permissionsarray[]Požadované rozsahy oprávnení pre auditný záznam
related_agentsarray[]ID agentov, na ktorých môže tento agent delegovať
escalationstring-Kam smerovať keď je agent neistý (human, supervisor-agent)

Nástroje: Mapovanie na Brevo MCP servery

Pole tools odkazuje na názvy modulov Brevo MCP servera. Každý modul mapuje na špecifický endpoint na mcp.brevo.com:

tools:
# Kontakty a segmentácia
- brevo_contacts # /v1/brevo_contacts/mcp
- brevo_lists # /v1/brevo_lists/mcp
- brevo_segments # /v1/brevo_segments/mcp
- brevo_attributes # /v1/brevo_attributes/mcp
# Kampane a správy
- brevo_email_campaign_management # /v1/brevo_email_campaign_management/mcp
- brevo_templates # /v1/brevo_templates/mcp
- brevo_sms_campaigns # /v1/brevo_sms_campaigns/mcp
- brevo_whatsapp_campaigns # /v1/brevo_whatsapp_campaigns/mcp
# Analytika
- brevo_campaign_analytics # /v1/brevo_campaign_analytics/mcp
# Sales CRM
- brevo_deals # /v1/brevo_deals/mcp
- brevo_companies # /v1/brevo_companies/mcp
- brevo_tasks # /v1/brevo_tasks/mcp
- brevo_pipelines # /v1/brevo_pipelines/mcp
- brevo_notes # /v1/brevo_notes/mcp

Tip

Používajte minimálnu sadu nástrojov, ktorú váš agent potrebuje. Menej nástrojov = lepšie uvažovanie AI a rýchlejšie odpovede. Pozrite Brevo MCP Server pre všetky dostupné moduly.

Spúšťače

Spúšťače udalostí

Aktivujte agenta keď sa niečo stane vo vašom systéme:

triggers:
- event: cart_abandoned
conditions:
- cart_value: "> 50"
- items_count: ">= 1"
- time_since_activity: "> 30m"
debounce: 5m

Spúšťače plánov

Spúšťajte agenta na opakujúcom sa pláne:

triggers:
- schedule: "0 9 * * MON" # Každý pondelok o 9:00
timezone: "America/New_York"
- schedule: "0 */4 * * *" # Každé 4 hodiny
- schedule: "0 0 1 * *" # Prvý deň každého mesiaca

Spúšťače webhookov

Invokujte agenta cez HTTP:

triggers:
- webhook: /agents/win-back/trigger
method: POST
authentication: api_key

Telo Markdown: Inštrukcie

Telo špecifikácie agenta sú inštrukcie v prirodzenom jazyku. Píšte to ako briefovanie skúseného marketéra:

Štruktúra

# Názov agenta
Kontextový odsek, čo tento agent robí a prečo.
## Stratégia
Krok za krokom prístup, ktorý by mal agent sledovať.
## Rozhodovací rámec
Pravidlá pre rozhodovanie (napr. ktorý kanál použiť na základe hodnoty košíka).
## Pravidlá
Tvrdé obmedzenia, veci, ktoré agent musí VŽDY alebo NIKDY robiť.
## Šablóny
Referencie na ID šablón Brevo, texty SMS, šablóny WhatsApp.
## Metriky
Udalosti na sledovanie pre meranie úspechu.

Písanie efektívnych inštrukcií

Buďte konkrétni ohľadom stratégie, nie len cieľov:

## Zlé
Re-engage churned customers.
## Dobré
When a customer hasn't purchased in 90+ days:
1. Check their last 3 orders for product category preferences
2. Create a personalized discount based on AOV (10% if AOV > $100, 15% if < $100)
3. Send email with subject line referencing their preferred category
4. Wait 72 hours, if no open, send SMS with discount code
5. Wait 7 days, if no purchase, mark as deep-churn and stop sequence

Explicitne definujte zábrany:

## Pravidlá
- NEVER send more than 3 messages per sequence
- NEVER contact customers who unsubscribed
- ALWAYS check if the customer converted before sending the next step
- ALWAYS respect quiet hours (no SMS 9pm-9am local time)
- If unsure about a decision, escalate to human review

Multi-agent reťaze

Pre komplexné pracovné toky skladajte viacerých agentov do reťaze. Každý agent spracováva jednu fázu, odovzdávajúc kontext ďalšiemu:

chain.yaml
name: quarterly-retention-campaign
steps:
- agent: customer-intelligence
input: |
Analyze customer segments for Q2 retention campaign.
Goal: {task}
Identify:
1. At-risk customers (declining purchase frequency)
2. VIP customers (top 10% by LTV)
3. Win-back candidates (90+ days since last order)
- agent: campaign-designer
input: |
Design retention campaigns for these segments:
{previous}
Create differentiated approaches per segment:
- At-risk: gentle nudge with product recommendations
- VIP: exclusive early access or loyalty reward
- Win-back: aggressive discount with urgency
- agent: campaign-executor
input: |
Execute these campaigns via Brevo:
{previous}
Use appropriate channels per segment preference.
Set up A/B tests for subject lines.
Schedule sends for optimal times.
- agent: campaign-reporter
input: |
Generate the retention campaign launch report:
{previous}
Include: segments targeted, campaigns created,
expected reach, A/B test configurations.

Premenné reťaze

PremennáPopis
{task}Pôvodný cieľ/požiadavka
{previous}Výstup z predchádzajúceho kroku
{step_N}Výstup z kroku N (0-indexed)
{artifacts_dir}Adresár pre výstupy súborov

Predbudované špecifikácie agentov

Campaign Orchestrator

---
name: campaign-orchestrator
description: Design and execute multi-channel campaigns from natural language prompts
version: 2.0.0
temperature: 0.3
tools:
- brevo_contacts
- brevo_segments
- brevo_email_campaign_management
- brevo_templates
- brevo_sms_campaigns
- brevo_whatsapp_campaigns
- brevo_campaign_analytics
triggers:
- webhook: /agents/campaign/trigger
method: POST
---
# Campaign Orchestrator
You are a multi-channel marketing campaign specialist.
Given a campaign brief, you design, build, and launch
campaigns across email, SMS, and WhatsApp via Brevo.
## Process
1. Parse the campaign brief (audience, message, goal, timeline)
2. Create or identify the target segment in Brevo
3. Select the best channel(s) based on audience preference data
4. Build campaign content using existing templates or creating new ones
5. Configure send schedule and A/B tests
6. Launch and report initial delivery metrics
## Channel Selection
- Email: default for all campaigns
- SMS: add for time-sensitive offers or cart recovery
- WhatsApp: add for conversational campaigns or high-value segments
## Rules
- ALWAYS preview campaigns before sending
- NEVER send to unsubscribed contacts
- ALWAYS set up tracking for campaign attribution
- Maximum 2 A/B test variants per campaign

Customer Intelligence Agent

---
name: customer-intelligence
description: Autonomous segmentation, RFM scoring, and churn prediction
version: 1.5.0
temperature: 0.2
tools:
- brevo_contacts
- brevo_segments
- brevo_attributes
- brevo_lists
- brevo_campaign_analytics
triggers:
- schedule: "0 6 * * MON"
timezone: "UTC"
---
# Customer Intelligence Agent
You analyze customer data in Brevo to generate actionable
segments and insights for marketing teams.
## Weekly Analysis
1. Pull contact activity data from campaign analytics
2. Calculate RFM scores (Recency, Frequency, Monetary)
3. Identify segment shifts (customers moving between tiers)
4. Flag churn risks (declining engagement over 4+ weeks)
5. Generate segment recommendations for upcoming campaigns
## Segment Definitions
- Champions: R=5, F=5, M=5, recent, frequent, high-value
- Loyal: R>=3, F>=4, M>=3, consistent buyers
- At Risk: R<=2, F>=3, M>=3, were loyal, now fading
- Hibernating: R=1, F>=2, M>=2, long gone, were once active
- New: first purchase in last 30 days
## Output
Produce a markdown report with:
- Segment sizes and week-over-week changes
- Top 10 at-risk customers by LTV
- Recommended actions per segment
- Suggested campaign themes for the week

Nasadenie

Programové spustenie agenta

import { TajoAgent } from "@tajo/agent-sdk";
const agent = new TajoAgent({
specPath: "./agents/cart-recovery-agent.md",
brevoToken: process.env.BREVO_MCP_TOKEN,
model: "claude-sonnet-4-6",
// Pripojí len MCP servery uvedené v poli tools agenta
autoConnectServers: true,
});
const result = await agent.run(
"Recover abandoned carts over $50 from the last 4 hours"
);
console.log(result.summary);
console.log(result.toolCalls); // Úplná auditná stopa
console.log(result.metrics); // Sledované udalosti

Spustenie cez Claude Code

Terminal window
# Nasmerujte na vašu špecifikáciu agenta a nechajte Claude vykonávať
claude "Run the agent defined in ./agents/cart-recovery-agent.md for today's abandoned carts"

Plánovanie s Cron

Terminal window
# Spúšťajte agenta customer intelligence každý pondelok o 6:00
0 6 * * MON claude --print "Run ./agents/customer-intelligence.md weekly analysis" >> /var/log/tajo-agents.log 2>&1

Ďalšie kroky

Subscribe to updates

developer-docs

Drop your email or phone number — we'll send you what matters next.

AI asistent

Ahoj! Opýtajte sa ma na dokumentáciu.

Začnite zadarmo s Brevo