Produce the monthly "Stablecoin Pulse" 2-page PDF for a partner team (default Polaris) from Pharos API data plus X and web research, explaining why supply, chains, and pegs moved. Use at month end or when asked for a monthly stablecoin trends/pulse report; not for the daily digest or Telegram pulse.
The English summary is being prepared. Showing the original description.
Review the instructions the agent will receive before you install.
A concise, actionable monthly read of the stablecoin market: page 1 is the pulse (KPIs, TL;DR, top movers with their causes, launches, depegs and incidents, market-wide signals, what to watch); page 2 is the evidence annex with linked sources. The value is the why: "PYUSD +25%" is noise; "PYUSD +25%, half of it from its Aave/Arc integration" is the product.
Read editorial-rules.md before writing copy, research-briefs.md before dispatching research, and layout.md before building.
circulatingPrevMonth. The fetcher has no historical-end option; run it on the last days of the month or the 1st of the next, and use data/market.json.window for the actual dates.October 2026) and partner name for the footer (default Polaris).agents/<YYYY-MM-DD>-pulse-report/ (ignored scratch). Prior months live in sibling agents/*-pulse-report/ directories; reuse the previous content.json as the structural starting point, never its facts.Prerequisites: PHAROS_API_KEY in the process environment or root .env.local (environment wins; report the name only if missing); Playwright Chromium or Google Chrome; Poppler (pdfinfo, pdftoppm) optional. X research needs live X search (see research-briefs.md).
Use the supported repository Node runtime (>=24.16 <27) with workspace dependencies installed, including tsx; the fetcher imports canonical shared TypeScript supply helpers.
node --import tsx .codex/skills/stablecoin-pulse-report/scripts/fetch-pulse-data.mjs --out agents/<YYYY-MM-DD>-pulse-report
Read data/brief.md end to end, then the data traps in editorial-rules.md. Before any research, list the candidate stories: the top gainers and losers by USD, material percentage movers, chain shifts, flagged single mints or burns (large-mints.json), unit-versus-price splits (unit-moves.json), and depegs. Resolve identity collisions (same ticker, different issuer) now.
Split the candidate stories into the five clusters in research-briefs.md. When delegation is available, dispatch one web researcher and one X scout per cluster together in a single batch (ten agents), all reading data/brief.md. Preflight X search with a control query first; if unavailable, run web-only and state "X unavailable" in the handoff. Without delegation, perform the research and skeptical review sequentially and disclose that review was not independent. Save every result verbatim to research/<Agent>.md (or named sequential-pass notes).
content.jsonThe orchestrator writes the copy; do not delegate synthesis. Follow the schema and character budgets in layout.md and the evidence ladder in editorial-rules.md. Every number must trace to data/ or a cited source; every causal claim must match its evidence strength.
Dispatch one independent read-only reviewer when available (prompt in research-briefs.md) over content.json, data/, and research/; otherwise use the disclosed sequential review. Apply every accepted fix yourself; re-verify disputed numbers against data/ rather than choosing between agents.
Run the layout build command from the repository root.
The build fails on overflow or a page count other than two. Open out/page-1.png and out/page-2.png and inspect them visually: no clipping, collisions, split −$ amounts, or orphaned heading words. Fix fit by trimming copy, never by shrinking type below the documented minimum.
Report the PDF path, the three to five headline findings, drivers that remain unexplained ("no source names…"), data caveats that shaped the copy, the fact-check verdict and fixes applied, X search spend if known, and which agents or models ran. Do not commit or publish the report unless asked; it lives in ignored scratch.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Review the retained annotation candidate queue and curate per-coin editorial history. Use weekly during active event periods, monthly otherwise, or on queue-health warnings; this does not restore the retired live chart overlay.
The English summary is being prepared. Showing the original description.
Generate a weekly changelog entry from git history, filtering operational noise and producing editorial summary, field notes, statistics, and a bounded commit manifest. Stops for review unless commit was explicitly requested.
The English summary is being prepared. Showing the original description.
Research and populate tracked stablecoin compliance sidecars for the U.S. GENIUS Act, EU MiCA, or both. Use when adding or auditing authorization, applicability, pathway, or disclosure evidence.
The English summary is being prepared. Showing the original description.
Use when adding, reviewing, squashing, deploying, or rolling back Pharos D1 migrations or schema cleanup.
The English summary is being prepared. Showing the original description.
Drain the Pharos Dependency Map coverage-audit queues into evidence-refreshed edges, reviewed target dispositions, or documented deferrals. Use monthly after weekly production dependency audits, after dependency coverage drops, or when reviewing adapter gaps, material unlinked slices, symbol leads, duplicate/split groups, or unverifiable published edges.
The English summary is being prepared. Showing the original description.
Update Pharos funding donations by reconciling inbound transfers, rejecting wallet self-activity and spam, pricing receipt-time value, and appending user-approved rows.
The English summary is being prepared. Showing the original description.