Format specifikacije agenta

Format specifikacije agenta

Tajo agenti su definisani u markdown fajlovima. Svaki fajl sadrži YAML frontmatter (identitet, alati, ograničenja) i markdown telo (uputstva, strategija, pravila). Ovaj format je inspirisan produkcionim šablonima agenata koji se koriste u sistemima multi-agent orkestracije.

Struktura fajla

---
name: agent-name
description: Šta ovaj agent radi (maks. 160 znakova)
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
---
# Naziv agenta
Uputstva za agenta na prirodnom jeziku...

Polja Frontmatter

Obavezna polja

PoljeTipOpis
namestringJedinstveni identifikator u kebab-case (npr. cart-recovery-agent)
descriptionstringŠta ovaj agent radi (maks. 160 znakova)
versionstringSemantička verzija (npr. 1.0.0)
toolsarrayModuli Brevo MCP servera kojima ovaj agent ima pristup

Polja ponašanja

PoljeTipPodrazumevana vrednostOpis
temperaturefloat0.3Temperatura LLM-a. Niža = determinističnija. Koristite 0.1-0.2 za operacije sa podacima, 0.3-0.5 za dizajn kampanja
max_tokensinteger4096Maksimalna dužina odgovora po obrtu
modelstringclaude-sonnet-4-6LLM model za upotrebu

Polja okidača

PoljeTipPodrazumevana vrednostOpis
triggersarray[]Događaji, rasporedi ili webhookovi koji aktiviraju ovog agenta
triggers[].eventstring-Naziv događaja (npr. cart_abandoned, customer_created)
triggers[].schedulestring-Cron izraz (npr. 0 9 * * * za svaki dan u 9:00)
triggers[].webhookstring-Putanja webhooks (npr. /agents/cart-recovery/trigger)
triggers[].conditionsarray[]Uslovi filtriranja za okidač
triggers[].debouncestring-Prozor debounce-a (npr. 5m, 1h)

Polja dozvola

PoljeTipPodrazumevana vrednostOpis
permissionsarray[]Zahtevani opsezi dozvola za revizorski zapis
related_agentsarray[]ID-ovi agenata na koje ovaj agent može da delegira
escalationstring-Gde eskalirati kada agent nije siguran (human, supervisor-agent)

Alati: Mapiranje na Brevo MCP servere

Polje tools referencira nazive modula Brevo MCP servera. Svaki modul se mapira na određeni endpoint na mcp.brevo.com:

tools:
# Kontakti i segmentacija
- brevo_contacts # /v1/brevo_contacts/mcp
- brevo_lists # /v1/brevo_lists/mcp
- brevo_segments # /v1/brevo_segments/mcp
- brevo_attributes # /v1/brevo_attributes/mcp
# Kampanje i poruke
- 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
# Analitika
- 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

Koristite minimalni skup alata koji vaš agent treba. Manje alata = bolje AI zaključivanje i brži odgovori. Pogledajte Brevo MCP Server za sve dostupne module.

Okidači

Okidači događaja

Aktivirajte agenta kada se nešto dogodi u vašem sistemu:

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

Okidači rasporeda

Pokrenite agenta po ponavljajućem rasporedu:

triggers:
- schedule: "0 9 * * MON" # Svaki ponedeljak u 9:00
timezone: "America/New_York"
- schedule: "0 */4 * * *" # Svakih 4 sata
- schedule: "0 0 1 * *" # Prvog dana svakog meseca

Okidači webhookova

Pozovite agenta kroz HTTP:

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

Telo Markdown: Uputstva

Telo specifikacije agenta su uputstva na prirodnom jeziku. Pišite ga kao brifovanje iskusnom marketaru:

Struktura

# Naziv agenta
Kontekstualni pasus, šta ovaj agent radi i zašto.
## Strategija
Korak-po-korak pristup koji agent treba da prati.
## Okvir odlučivanja
Pravila za donošenje odluka (npr. koji kanal koristiti na osnovu vrednosti korpe).
## Pravila
Čvrsta ograničenja, stvari koje agent UVEK ili NIKAD ne sme da radi.
## Šabloni
Reference na ID-ove šablona Brevo, SMS tekstove, WhatsApp šablone.
## Metrike
Događaji za praćenje radi merenja uspeha.

Pisanje efikasnih uputstava

Budite konkretni u pogledu strategije, ne samo ciljeva:

## Loše
Re-engage churned customers.
## Dobro
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

Eksplicitno definišite ograničenja:

## Pravila
- 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 lanci

Za složene tokove rada sastavite više agenata u lanac. Svaki agent obrađuje jednu fazu, predajući kontekst sledećem:

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.

Promenljive lanca

PromenljivaOpis
{task}Originalni cilj/zahtev
{previous}Izlaz iz prethodnog koraka
{step_N}Izlaz iz koraka N (0-indeksirano)
{artifacts_dir}Direktorijum za izlazne fajlove

Ugrađene specifikacije agenata

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

Implementacija

Programsko pokretanje 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",
// Povezuje samo MCP servere navedene u polju 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); // Potpuna revizorska putanja
console.log(result.metrics); // Praćeni događaji

Pokretanje kroz Claude Code

Terminal window
# Uputite na vašu specifikaciju agenta i pustite Claude da izvršava
claude "Run the agent defined in ./agents/cart-recovery-agent.md for today's abandoned carts"

Zakazivanje sa Cron

Terminal window
# Pokretajte agenta customer intelligence svaki ponedeljak u 6:00
0 6 * * MON claude --print "Run ./agents/customer-intelligence.md weekly analysis" >> /var/log/tajo-agents.log 2>&1

Sledeći koraci

Subscribe to updates

developer-docs

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

AI асистент

Здраво! Питајте ме о документацији.

Započnite besplatno sa Brevo