agentleFS
rasulshaikhrasulshaikh/fde-desk/AGENTS.md

fde-desk

AGENTS.md0 starsChanged 48 days agoMITView on GitHub

Registry of desk agents. Each agent lives in .claude/agents/<name>.md and is invoked by name or through a command.

The file

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

3 rules. About 0 are common, 0 are distinctive, and 3 are 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.

  • 3

    Very specific

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

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

    Always run ship-reviewer before /desk-close when artifacts will be handed to a human or CRM.

    line 21
  2. Very specific:

    Run infra-ops (and deploy-surface-check) before blaming Clay or n8n when a hosted surface is red.

    line 23
  3. Very specific:

    Add .claude/agents/<kebab-name>.md with role, inputs, outputs, and stop conditions.

    line 28

≈ “Common” is an estimate: at least 1 in 5 of the 41,581 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

AGENTS.md

Registry of desk agents. Each agent lives in .claude/agents/<name>.md and is invoked by name or through a command.

Agents

AgentRoleTypical inputsTypical outputs
signal-scoutFind and normalize buying triggersICP notes, watchlist domains, Clay signal feedsSignal board markdown, ranked trigger list
clay-enricherDesign and run Clay enrichment batchesTable schema, row sample, enrichment goalsClean CSV/table plan, field map, QA notes
account-mapperMap buying committee and whitespaceAccount list, org chart hints, CRM notesAccount map, persona coverage gaps
outreach-drafterDraft outbound that cites signalsSignal + account map + offer notesReviewable email/LinkedIn drafts
call-prepPrep discovery and demo callsMeeting context, account map, open questionsCall brief, objection list, success criteria
ship-reviewerGate quality before anything leaves the deskDrafts, packs, enrichment diffsPass/fail review with fix list
infra-opsTriage Render / Railway / optional Oracle A1Symptoms, deploy notes, stack-statusTriage note, status colors, fix order

Coordination

  1. Scout and enrich before draft.
  2. Map accounts before call prep.
  3. Always run ship-reviewer before /desk-close when artifacts will be handed to a human or CRM.
  4. Agents draft; humans approve; hooks enforce the send fence.
  5. Run infra-ops (and deploy-surface-check) before blaming Clay or n8n when a hosted surface is red.
  6. Overnight or multi-hour work goes through Hermes/Herdr with a Jev brief, not an open interactive chat left unattended.

Adding an agent

  1. Add .claude/agents/<kebab-name>.md with role, inputs, outputs, and stop conditions.
  2. Register it in this file.
  3. Wire it into a command or skill if it is part of the default loop.

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.