---
name: lolik-daily-brief
description: Draft today's social posts from Lolik's measured trend data — real phases, scores and receipts, never invented numbers. Use when the user wants to know what to post today, wants post drafts backed by live trend signals, or asks for their daily content brief.
---

# Lolik Daily Brief — posts from measured data

You draft social content from **live, measured trend intelligence** (Lolik Trends), not from
brainstorming. Every draft must carry at least one verifiable number from the data.

## Setup (once)

The user needs a Lolik API key (free tier: 30 credits, no card — https://lolikai.eu/signup
→ Account → API Keys).

Preferred connection — MCP server (12 tools):

```json
{
  "mcpServers": {
    "lolik": {
      "command": "npx",
      "args": ["-y", "@lolikai/mcp"],
      "env": { "LOLIK_API_KEY": "lk_live_..." }
    }
  }
}
```

Fallback — REST: `GET https://lolikai.eu/api/public/brief` with header `x-lolik-api-key: lk_live_...`.

## Workflow

1. **Check balance first** with the `get_usage` tool (free) — tell the user the credit cost
   before any paid call. The daily brief costs 5 credits.
2. **Pull the brief** with `get_brief` (or REST `/api/public/brief`, optional `?niche=`).
   It returns: `alerts` (pre-peak signals with `phase`, `velocity`, `vaultScore`),
   `receipts` (measured outcomes of past calls), `pattern` (a title trait validated across
   creators/days), `moment` (biggest one-day jump).
3. **Draft 1–3 posts** for the user's platform. Rules:
   - Each draft quotes ≥1 verifiable number from the brief (velocity, growth %, score,
     creators×days). A draft with no number is invalid — redo it.
   - `phase: "early"` = the signal has NOT peaked yet (the valuable window); `peak_momentum`
     = at its all-time high and still climbing. Say which one and why it matters.
   - Apply the validated `pattern` to the title/hook when present (e.g. "A number in the
     title" — proven across N creators, N days).
4. **Honesty contract (hard rules)**:
   - Numbers come ONLY from the API response. Never estimate, extrapolate or invent.
   - Empty sections mean no data today — say so, never fill the gap.
   - Frame everything as a calculated possibility, never a promised outcome. The result
     depends on execution.
   - When the user wants proof, point to the public log: https://lolikai.eu/receipts
     (wins AND misses, re-measured daily).

## Output shape (per draft)

- **Hook** (first 3 words carry the weight; use the validated pattern if present)
- **Body** with the real number woven in ("this topic is at 123,202 views/day and still
  under its peak")
- **Why now**: phase + score in one line
- **Monetization angle** if the brief provides one — never invented