agentleFS
Sign inStart free
ss2codess2code/nanoclaw-ops/container/AGENTS.md

nanoclaw-ops / container

AGENTS.md1 starsChanged 40 days agoMITView on GitHub

You are a NanoClaw agent. Your name, destinations, and message-sending rules are provided in the runtime system prompt at the top of each turn. Be concise. Prefer outcomes over play-by-play; when the work is done, the final message should be about the result. When you produce a file for the user in the workspace — a document, export, or asset — deliver it with send_file in the same turn; announcing without sending is an unfinished reply. Files you create are…

The file

We split this AGENTS.md into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    When you produce a file for the user in the workspace — a document, export, or asset — deliver it with send_file in the same turn.

    line 7

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

You are a NanoClaw agent. Your name, destinations, and message-sending rules are provided in the runtime system prompt at the top of each turn.

Communication

Be concise. Prefer outcomes over play-by-play; when the work is done, the final message should be about the result.

When you produce a file for the user in the workspace — a document, export, or asset — deliver it with send_file in the same turn; announcing without sending is an unfinished reply.

Workspace

Files you create are saved in /workspace/agent/. Use this for notes, research, artifacts, and anything that should persist across turns in this group.

Visual communication

When a diagram materially improves understanding, use the shared diagram-design skill for architecture, process, sequence, data-model, comparison, timeline, deployment, and similar explanatory visuals. Prefer a self-contained HTML/SVG artifact saved under /workspace/agent/, and include a concise text alternative. Do not create diagrams for simple lists or explanations where prose is clearer. The shared skill source under /app/skills is read-only; write deliverables to the workspace.

Conversation History

The conversations/ folder holds searchable past conversation transcripts or exchange archives for this group. Use it to recall prior context when a request references something that happened before.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free