Skip to main content
Use this guide when you want to discuss one Paperzilla project in Telegram and receive a weekday research brief there. OpenClaw runs the agent and the schedule. Paperzilla provides the research feed, and Telegram carries the conversation and the brief.

Before you start

Connect Paperzilla in OpenClaw first. Install the Paperzilla MCP plugin and connect your account. Then return here to add Telegram.
  • If your agent already uses the Paperzilla CLI with OpenClaw, you can keep that setup. Check that pz project list works where OpenClaw runs.
  • Set up Telegram in OpenClaw. In a Telegram chat with your agent, ask it to list your Paperzilla projects to check both connections.
  • Pick one Paperzilla project for this workflow.
  • Prepare one short sentence for “our work” if the agent does not already know it. Example: Our work is evaluation infrastructure for coding agents.

How this stack works

  • You ask for papers in Telegram.
  • OpenClaw reads your Paperzilla data through MCP or the CLI, depending on your setup.
  • OpenClaw can either browse the latest feed items or search the full feed for a topic.
  • For the weekday brief, OpenClaw runs a cron job and sends the result back to Telegram.
  • Paperzilla still owns the project, feed, and relevance ranking. OpenClaw is the chat and delivery layer on top.

Use case 1: on-demand paper discussion

Start in a Telegram DM or group where your OpenClaw agent is already active. First ask for the latest papers from one project:
Then ask for metadata for one paper:
Then fetch markdown and connect it back to your team context:
Then keep the discussion going in the same Telegram chat:
You can also ask for full-feed search instead of latest-first browsing:
Good replies for this flow should:
  • keep the project name and “our work” context in view
  • separate metadata from interpretation
  • explain relevance in terms of your actual work, not generic importance
  • keep the paper discussion going instead of stopping at one summary
If markdown is still being prepared, ask again after a short wait.

Use case 2: weekday research brief in Telegram

This pattern sends one brief to Telegram every weekday. Use an OpenClaw cron job for the schedule and Telegram for delivery. OpenClaw’s cron docs use standard cron syntax, so 1-5 in the day-of-week field means weekdays.
Replace these placeholders before you run it:
  • <agent-id> with the ID of the agent that successfully read Paperzilla in the Telegram test. Use openclaw agents list to find the ID.
  • <project-name> with the Paperzilla project name you want to follow
  • <one-sentence team context> with your short “our work” description
  • Europe/Athens with your own timezone
  • <telegram target> with the Telegram target format you use in OpenClaw
The expected brief format is:
  • project name and date
  • time window and how many new papers were checked
  • for each selected paper, a source link and why it is relevant to your work
  • a clear “no new papers today” line when nothing new qualifies
See OpenClaw cron jobs and OpenClaw message delivery for channel and target details.

Limits and troubleshooting

  • If your agent cannot read Paperzilla data, check the plugin’s account connection and tool access in OpenClaw. If you use pz, check the CLI setup.
  • If the agent returns no papers, confirm the project is active and already has feed items.
  • If Markdown is queued, try again later. If it is unavailable, use the abstract and other available information and say so in the brief.
  • If the cron job does not fire, check that the OpenClaw Gateway is running continuously and that your timezone is correct.

Optional shortcut

If you want this workflow packaged as a reusable skill, see the paperzilla-monitor skill repo. Current install and distribution details live in that repo’s README.