agentleFS
rgoerwitrgoerwit/ai-investment-agent/.agents/skills/add-agent/SKILL.md

add-agent

Skill71 starsChanged 36 days agoMITView on GitHub

Add or substantially change an analysis agent, graph node, or LLM seat in this repository. Use when introducing a new agent role or changing its prompt, tools, state, routing, persistence, attribution, and tests.

9 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use setup.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • VercelSkill

    setup

    Set up Vercel CLI and project configuration. Use when the user says "set up Vercel", "configure Vercel", "link to Vercel", or "vercel init".

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

8 rules. 0 are common, 4 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 7 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

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

    Read docs/AGENT_ROSTER.md, docs/PROMPT_CONTRACTS.md, and the relevant graph and runtime modules.

    line 14
  2. Very specific:

    Add or update the prompt through structured JSON handling under prompts/.

    line 16
  3. Distinctive:

    Do not introduce a context-name exception or construction-time flex cap.

    line 23
  4. Very specific:

    Add node logic in the owning src/agents/ module and tools in the owning src/tools/ module.

    line 24
  5. Distinctive:

    Update state, reducers, graph wiring, retry/fallback behavior, output budgets, persistence, attribution, and publication requirements only …

    line 26
  6. Distinctive:

    Add contract tests for seat registration, prompt loading, graph topology, attribution, malformed/refused output, retry behavior, and …

    line 29
  7. Very specific:

    Run make test-prompts, the relevant targeted tests, and make check-all.

    line 34
  8. Distinctive:

    Do not copy thresholds, model defaults, or enum values into this skill.

    line 36

“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “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
SKILL.md

Add an analysis agent

First determine whether the requested concept is an LLM seat, deterministic validator, tool, or orchestration node. Extend the owning abstraction instead of forcing every concept into an agent shape.

For an LLM-backed role:

  1. Read docs/AGENT_ROSTER.md, docs/PROMPT_CONTRACTS.md, and the relevant graph and runtime modules.
  2. Add or update the prompt through structured JSON handling under prompts/.
  3. Register the canonical seat and capabilities in src/llm_runtime/seats.py; construct it through src/llm_runtime/construction.py. Choose its timeout class from src/llm_runtime/timeouts.py. The runtime owns total application attempts; transports configure one SDK attempt per dispatch, with no per-seat retry setting. This does not prove one physical send: Google's aiohttp connection recovery can resend internally. Verify application retry and rate-limit branch counts. Do not introduce a context-name exception or construction-time flex cap.
  4. Add node logic in the owning src/agents/ module and tools in the owning src/tools/ module. Tool execution must stay inside the inspection and audit chain.
  5. Update state, reducers, graph wiring, retry/fallback behavior, output budgets, persistence, attribution, and publication requirements only where the role needs them. Parallel branches require isolated fields or an intentional reducer.
  6. Add contract tests for seat registration, prompt loading, graph topology, attribution, malformed/refused output, retry behavior, and saved-artifact semantics. Exercise the actual adapter's dispatch options under an exhausted or nearly spent deadline, including corrections, degraded-tier dispatch and failover. A model's configuration fields alone do not prove its request deadline or retry options.
  7. Run make test-prompts, the relevant targeted tests, and make check-all.

Do not copy thresholds, model defaults, or enum values into this skill. Read them from the owning code and update that source plus its tests when behavior changes.

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.