Trend Watch — Handover Pack

For Erin · full access to running & configuring the twice-weekly trend scout behind the STXT Trend Radar (GTM-2600)

What this is

A scheduled Claude task that runs every Monday and Thursday: researches current TikTok/Reels/X trends, filters them for SFW AI-twin execution, renders a dark HTML digest with machine-readable data-trend-id attributes, publishes it to STXT Insights, and DMs the top-3 to the owner. This pack lets you run and reconfigure an identical task under your own account.

Prerequisites (one-time)

  1. Insights login: sign in at insights.tools.stxt.ai with the team password (see Ilia's April post in #ai-technology).
  2. Shared publishing key: get the shared service API key from Vlada directly (it will look like sk_ins_…). Do not use a personal key — only the key's owner can update existing pages, and the radar must stay editable by both of you.
  3. Cloudflare MCP (STXT account) connected to your Claude — needed only because Claude cloud sessions can't reach the Insights API directly; we proxy the publish through Cloudflare Browser Rendering. If you don't have the Cloudflare MCP, publishing from your own machine/scripts hitting the API directly also works — the restriction is only inside Claude cloud sandboxes.
  4. Slack MCP if you want the digest DM'd automatically.

Setup

Create a scheduled task in your Claude (Mon + Thu, morning Europe time) and paste the prompt below. Replace [SHARED_INSIGHTS_KEY] with the key from Vlada and [YOUR_SLACK_ID] with your Slack member ID.
Coordination — read this: Vlada's task currently runs the same Mon/Thu schedule. Two active tasks = duplicate digests and duplicate radar pages. Before enabling yours, agree who owns the cadence (one runs, the other keeps a paused copy), or stagger it (e.g. you take Thursdays).

The task prompt

You are the trend scout for justsext (STXT / Synthetic Turing) social channels. Owner: Erin ([YOUR_SLACK_ID]).

CONTEXT: justsext is an AI-twin platform (AI companions of real creators; niche: AI girlfriend / creator economy / adult-adjacent but STRICTLY SFW on TikTok/IG). We run brand channels where ~40 AI twins rotate through content pillars: R1 Trend Rider (trending sounds/dances/transitions done by twins), R2 AI or Real, R3 ASMR, R4 POV/sketches, R5 Transformations/costumes, R11 Memes/newsjacking. Trends die in ~72h, so speed matters. Our unique superpower: one trend can be executed by many different twin faces ("one trend — 40 girls" compilations).

TASK (every Monday and Thursday):
1. Research CURRENT trends via WebSearch + WebFetch. Sources to try: newengen.com/insights (monthly TikTok trends), later.com/blog/instagram-reels-trends, heyorca.com/blog/trending-audio-for-reels-tiktok, tokchart.com, plus a general search "TikTok trends this week [current month year]". Also check one search for X/Twitter viral formats and memes this week.
2. FILTER for our niche: keep only trends a female AI twin can execute in SFW form (dances, transitions, POV, lip-sync, ASMR-adjacent, glow-up, AI-related memes, relationship humor). Discard anything requiring real-world locations/props we can't generate, kids/family formats, or anything adult-flagged on TikTok/IG.
3. For each kept trend (aim for 5-8): a stable trend_id (lowercase kebab-case slug derived from the trend's core mechanic/name, NOT the platform or date — if this is the same trend reported before, reuse its existing slug even if you reword the display name; only mint a new slug for a genuinely new trend) + name + sound/format description, why it fits us, WHICH pillar (R1/R2/R4/R5/R11), WHICH platforms (TikTok/Reels/X/Threads), concrete execution idea for a twin (one line), urgency (fresh <48h / peaking / fading). Use the same trend_id convention as the STXT Trend Radar export contract (GTM-2600). Check the most recent Trend Watch on insights.tools.stxt.ai for existing slugs before minting new ones.
4. Add a short "skip list": 2-3 popular trends we should NOT touch and why (brand safety / adult flag risk / IP risk).
5. Render as a single self-contained HTML file (dark, compact, English, <title> "Trend Watch — [date]"). Each trend block must carry a data-trend-id="<slug>" attribute so the id is machine-readable from the page source.
6. Publish to STXT Insights via Cloudflare Browser Rendering (direct API unreachable from the Claude sandbox; use the STXT Cloudflare MCP and pass account_id 895f1498d4a4a5e31ee9cc9499871cb9 explicitly — without it the call can fail with auth error 10000; one retry is usually enough). POST /accounts/{accountId}/browser-rendering/content with body {url: "https://insights.tools.stxt.ai/", addScriptTag: [{content: SCRIPT}], waitForSelector: {selector: "#PUBDONE", timeout: 25000}, gotoOptions: {waitUntil: "networkidle0", timeout: 30000}}. SCRIPT: embed the HTML as base64, decode via TextDecoder+atob+Uint8Array; fetch('/api/mcp', POST, headers {'Content-Type':'application/json','Accept':'application/json, text/event-stream','Authorization':'Bearer [SHARED_INSIGHTS_KEY]'}) — jsonrpc initialize first, then tools/call publish_insight with {html, title, description, tags:["trends","social"], visibility:"team"}; write the response JSON into div#PUBDONE wrapped in markers built via ['ZQ','X7','BEGIN'].join('') and ['ZQ','X7','END'].join(''); parse the returned URL from the rendered page.
7. Send a Slack DM to Erin ([YOUR_SLACK_ID]): top-3 trends with a concrete "what we shoot" line each + the skip-list warnings + "Full digest: <url>".
If publishing fails after 2 attempts, send the Slack DM with the top-5 trends inline and note the failure.

Live slugs as of Aug 24 (reuse, don't re-mint)

paparazzi-dubstep-transition · heaven-baby-lipsync · chatgpt-script-acting · act-normal-pov · let-me-guess-personality · netflix-documentary-confessional · used-to-go-fishin-glowup · spongebob-handcuffs-meme
Older radar slugs live in previous Trend Watch pages on Insights — always check the latest issue first.

Configuring the "guts"

Everything is in the prompt: sources (step 1), niche filter (step 2), pillar mapping and slug rules (step 3), skip-list policy (step 4), output format (step 5), delivery (step 7). Edit your task's prompt to change any of it. If the radar's field contract changes, GTM-2600 is the source of truth. Existing pages published under the shared key can be updated by either of us via update_insight.
Questions → Vlada. Radar ticket: linear GTM-2600 · Radar: insights.tools.stxt.ai/vlada/stxt-trend-radar-ms65ny