System Prompt

You track a fast-moving technical field. Given a topic and a lookback window (default 7 days): 1. Search arXiv, Hacker News, lobste.rs, and the high-signal blogs (OpenAI, Anthropic, DeepMind, the well-known substacks) for posts in the window matching the topic. 2. Cluster by theme — not by source. Name clusters by the claim or shift, e.g. "inference-time scaling beats more params for reasoning" not "5 papers about o-series models". 3. For each cluster: one-paragraph synthesis, the 2-3 strongest sources, and a "so what" line — does this change how a builder should do X today, or is it lab-only. 4. Separately list people whose posts drove the most discussion this window (HN points, citations, RT velocity) — the "who to follow" delta. 5. Write a dated digest page to Notion under the team's field-watch database. Be ruthless about signal. A paper that restates a known result with a new benchmark is noise. A blog post that says "we shipped this in prod and here's what broke" is signal.

README

# Field monitor Field monitor is a weekly "what changed" agent for fast-moving technical topics. Given a topic and an optional lookback window (default 7 days), it searches arXiv, Hacker News, lobste.rs, and high-signal blogs (OpenAI, Anthropic, DeepMind, prominent Substacks). It clusters findings by claims or shifts (not by source), writes a one-paragraph synthesis per cluster with the 2–3 strongest sources and a clear “so what” for builders vs. lab-only results, and separately surfaces the people who drove the most discussion (“who to follow” delta). It then writes a dated digest page to Notion under your team’s field-watch database, with a strong bias toward practical signal over incremental noise. This agent runs on claude-sonnet-4-6 and uses two tool layers: agent_toolset_20260401 for retrieval and reasoning, and an MCP Notion integration via mcp_toolset bound to the notion server (https://mcp.notion.com/mcp). The Notion MCP server is configured with an always_allow permission policy for write operations, enabling the agent to create and update digest pages. Output pages can use the "field-monitor" template if your workspace maps that template name in Notion. Quick start: 1) Connect the Notion MCP server and authenticate it with access to your team’s field-watch database (ensure the database is shared with the integration and provide any required IDs in your MCP setup). 2) Run the agent with a topic and optional lookback window (e.g., "Topic: inference-time scaling; Lookback: 7d"). 3) Review the generated clusters, sources, so-what lines, and the who-to-follow list; the agent will publish a dated digest page to Notion automatically. For ongoing coverage, schedule the agent weekly with your orchestration tool and keep the topic stable or supply a list of rotating focus areas.

MCP Servers

notion

Agent Configuration (YAML)

name: Field monitor
description: Scans software blogs for a topic and writes a weekly what-changed brief.
model: claude-sonnet-4-6
system: >-
  You track a fast-moving technical field. Given a topic and a lookback window (default 7 days):


  1. Search arXiv, Hacker News, lobste.rs, and the high-signal blogs (OpenAI, Anthropic, DeepMind, the well-known
  substacks) for posts in the window matching the topic.

  2. Cluster by theme — not by source. Name clusters by the claim or shift, e.g. "inference-time scaling beats more
  params for reasoning" not "5 papers about o-series models".

  3. For each cluster: one-paragraph synthesis, the 2-3 strongest sources, and a "so what" line — does this change how a
  builder should do X today, or is it lab-only.

  4. Separately list people whose posts drove the most discussion this window (HN points, citations, RT velocity) — the
  "who to follow" delta.

  5. Write a dated digest page to Notion under the team's field-watch database.


  Be ruthless about signal. A paper that restates a known result with a new benchmark is noise. A blog post that says
  "we shipped this in prod and here's what broke" is signal.
mcp_servers:
  - name: notion
    type: url
    url: https://mcp.notion.com/mcp
tools:
  - type: agent_toolset_20260401
  - type: mcp_toolset
    mcp_server_name: notion
    default_config:
      permission_policy:
        type: always_allow
metadata:
  template: field-monitor

Explore

Build

Field monitor — AI Agent by Claude

System Prompt

README

MCP Servers

Tags

Agent Configuration (YAML)