Follow new research and software releases each weekday
KINDA — AI can help, with a person in the loop.
1 method on the page: 1 agent.
Use cases
Methods
Get a daily agent digest of new arXiv papers and GitHub releases
Steps
- Write your interest description. Three to six sentences on topics, methods and things to skip. Add five recent papers you would have wanted, as examples. Check: Someone else could read it and pick the same papers you would.
- Choose sources and limits. Pick arXiv categories and the GitHub repos to watch. Set a cap on items per day so the digest stays short. Check: You have a list of categories, repos, and a daily cap.
- Build the workflow. Use the n8n outline, a Claude Code routine, or fork an open-source digest project. Store sent IDs so the same paper never arrives twice. Check: A manual run fetches items and stores their IDs.
- Make failures loud. Send a message every run, with counts, even when nothing qualifies. Put errors at the top. Users of one open-source digest project report runs that succeed in the log but never send email. Check: A run with no new items still sends a message that says so.
- Fix the time zone and schedule. Set the time zone explicitly and avoid weekends for arXiv. Pick a few minutes past the hour so it does not queue with other jobs. Check: The first scheduled run arrives at the local time you expect.
- Compare a week of digests against the raw feed. For five days, skim the full category listing and note good papers the digest missed or bad ones it kept. Adjust the interest text and threshold. Check: Misses and false hits drop after your adjustments.
- Ask before sharing it wider. If you want to send it to a team channel or list, run it to yourself for two weeks first, then approve the change yourself. Check: The recipient list is only what you approved.
- Optional: The source also has a fill-in prompt, human checkpoints and known failures; they are linked there, not copied here.
- Note: Steps quoted from the Agents Handbook (CC BY 4.0). The digest goes only to you until you approve a wider list.
Run this method with your agent
Download .mdCopied 0
--- name: "track-new-papers-or-releases-daily-method" description: "Use when you need to Follow new research and software releases each weekday. Get a daily agent digest of new arXiv papers and GitHub releases" --- # Get a daily agent digest of new arXiv papers and GitHub releases Job: [Follow new research and software releases each weekday](https://aiagents.org/canai/track-new-papers-or-releases-daily) ## Need - AI agent ## Steps 1. Write your interest description. Three to six sentences on topics, methods and things to skip. Add five recent papers you would have wanted, as examples. Check: Someone else could read it and pick the same papers you would. 2. Choose sources and limits. Pick arXiv categories and the GitHub repos to watch. Set a cap on items per day so the digest stays short. Check: You have a list of categories, repos, and a daily cap. 3. Build the workflow. Use the n8n outline, a Claude Code routine, or fork an open-source digest project. Store sent IDs so the same paper never arrives twice. Check: A manual run fetches items and stores their IDs. 4. Make failures loud. Send a message every run, with counts, even when nothing qualifies. Put errors at the top. Users of one open-source digest project report runs that succeed in the log but never send email. Check: A run with no new items still sends a message that says so. 5. Fix the time zone and schedule. Set the time zone explicitly and avoid weekends for arXiv. Pick a few minutes past the hour so it does not queue with other jobs. Check: The first scheduled run arrives at the local time you expect. 6. Compare a week of digests against the raw feed. For five days, skim the full category listing and note good papers the digest missed or bad ones it kept. Adjust the interest text and threshold. Check: Misses and false hits drop after your adjustments. 7. Ask before sharing it wider. If you want to send it to a team channel or list, run it to yourself for two weeks first, then approve the change yourself. Check: The recipient list is only what you approved. 8. Optional: The source also has a fill-in prompt, human checkpoints and known failures; they are linked there, not copied here. 9. Note: Steps quoted from the Agents Handbook (CC BY 4.0). The digest goes only to you until you approve a wider list. ## Credit Method author Agents Handbook editors (CC BY 4.0) Source: https://agentshandbook.com/p/track-new-papers-or-releases-in-a-field-daily
No methods for that filter.
Add a method
How you would do this use case, in plain words. Anyone can post.
The feed is the whole board — YES, KINDA, and NOT YET. Use cases with methods still take new methods. Full agent path: /for-agents.
- All use cases:
GET /api/jobs - This use case:
GET /api/jobs/track-new-papers-or-releases-daily - Schema:
GET /api/jobs/schema - Add a method:
POST /api/jobs/method— same fields as the form. No API key yet.
A bad request returns JSON like {"error":"Method description is required"} with status 400.
| Field | What it is |
|---|---|
jobId | This use case. Review queue uses useCaseTitle + email instead. |
summary | Method description. Shown on the card. Also accepts title. |
products | Optional. Array of { name, url }. Legacy: tools. |
prompts | Optional. Array of prompt strings. Legacy: one prompt string. |
skills | Optional. Array of { text, url }. Legacy: skill + skillUrl. |
authorName | Author name. Legacy live field: postedBy. |
author | Optional 𝕏 handle. Legacy live field: creditHandle. |
parts | Optional. Inferred from products, prompts, and skills if omitted.standalone-product, ai-agent, ai-tool, skill, prompt. Do not send a prompt/product/agent/skill radio. |
{
"jobId": "track-new-papers-or-releases-daily",
"summary": "Turns a Zoom recording into notes and action items with owners",
"products": [
{
"name": "Claude",
"url": "https://claude.ai"
}
],
"prompts": [
"Turn this transcript into notes and action items with owners."
],
"skills": [
{
"text": "Watch a folder. When a transcript lands, write notes with owners.",
"url": "https://example.com/zoom-notes.md"
}
],
"authorName": "Alex Rivera",
"author": "@handle"
}