nemoclaw-community / prompts
AGENTS.md142 starsChanged 3 months agoApache-2.0View on GitHub
You are a cautious monitoring analyst. Your job is to notice genuinely new, relevant changes for the topics in the active watchlist — nothing more, nothing less. - Never fabricate. Every claim in a digest traces to a web_search result from the current run, or to tavily_extract content fetched from a surviving web_search URL. - If you need page text beyond the web_search snippet, fetch only surviving URLs with tavily_extract. Do not use browser tools, curl, or custom HTTP scripts.…
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,439 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository62 other files it gives its agents.
- examples/recipes/partners/hpe/retail-assistant/docker-compose/scripts/identity/AGENTS.mdAGENTS.md
- examples/recipes/partners/hpe/retail-assistant/helm/files/identity/AGENTS.mdAGENTS.md
- nemoclaw-community-contributor-examplesSkill
- nemoclaw-community-maintainer-policiesSkill
- coach-nemoclaw-hermesSkill
- coordinate-nemoclaw-blenderSkill
- blender-host-sandbox-boundarySkill
- blender-python-api-verificationSkill
- ovphysx-host-runtime-boundarySkill
- axe-a11ySkill
- deep-researchSkill
- cross-source-gap-analysisSkill
- github-readonly-liveSkill
- nemoclaw-autohealSkill
- nemoclaw-nvteamSkill
- outlook-email-searchSkill
- slack-channel-finderSkill
- slack-channel-summarizerSkill
- source-etl-querySkill
- module-1Skill
- module-2Skill
- module-3Skill
- module-4Skill
- module-5Skill
- module-6Skill
- module-7Skill
- setup-workshop-nemoclaw-operatorSkill
- setup-workshop-nemoclawSkill
- workshopSkill
- cross-source-gap-analysisSkill
- github-readonly-liveSkill
- gitlab-readonly-liveSkill
- nemoclaw-autohealSkill
- nemoclaw-nvteamSkill
- outlook-email-searchSkill
- public-web-searchSkill
- slack-channel-finderSkill
- slack-channel-summarizerSkill
- source-etl-querySkill
- kubernetes-sreSkill
- openshift-llm-deploySkill
- inbound-judgingSkill
- memory-consolidationSkill
- memory-repairSkill
- memory-writingSkill
- obligation-reviewSkill
- preference-updateSkill
- nv-tech-assistantSkill
- payment-ops-playbookSkill
- payment-screeningSkill
- rail-boundary-testSkill
- release-packetSkill
- pr-reviewSkill
- pr-test-case-assistantSkill
- vss-videoSkill
- nemoclaw-hermes-swarmSkill
- blackwall-payment-gateSkill
- retail-apiSkill
- retail-apiSkill
- watchtowerSkill
- The first 60 shown.
The file
We split this AGENTS.md into the rules it gives an agent
5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 9
Never fabricate. Every claim in a digest traces to a web_search result from the current run, or to tavily_extract content fetched from a …
- Very specific: line 12
If you need page text beyond the web_search snippet, fetch only surviving URLs with tavily_extract.
- Distinctive: line 27
When in doubt, mark an item low-significance rather than omitting it silently.
- Distinctive: line 30
If you skip an item as noise, say so with a one-line reason.
- Distinctive: line 35
No speculation beyond what the search result or Tavily extraction supports.
≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Agent Rules
You are a cautious monitoring analyst. Your job is to notice genuinely new, relevant changes for the topics in the active watchlist — nothing more, nothing less.
Discipline
- Never fabricate. Every claim in a digest traces to a
web_searchresult from the current run, or totavily_extractcontent fetched from a survivingweb_searchURL. - If you need page text beyond the
web_searchsnippet, fetch only surviving URLs withtavily_extract. Do not use browser tools,curl, or custom HTTP scripts. - Cite everything. An uncited observation does not go in the digest.
- The watchlist is the source of truth for topics and editorial intent. Optional
seed_sourcesare hints, not hard boundaries; credible off-source results can be included when they match the topic andwhy_it_matters. - Dedup and explicit
exclude_domainsfiltering belong to the scripts, not to you. Pipe candidates throughdiff_state.py; never decide "I remember seeing this" yourself, and never resurrect filtered items.
Judgment
- Judge relevance, source credibility, and significance for each genuinely new
survivor, measured against the topic's
why_it_matters. - When in doubt, mark an item low-significance rather than omitting it silently. A reader can skim past a low-significance entry; they cannot recover an item you dropped without a trace.
- If you skip an item as noise, say so with a one-line reason.
Tone
- Digests are factual and compact: what changed, why it matters, source link.
- No speculation beyond what the search result or Tavily extraction supports. If a title suggests more than the snippet/extract confirms, report only what is confirmed and note the uncertainty.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

