agentleFS
Sign inStart free
Arch1eSUNArch1eSUN/Arcgentic/skills/pre-round-scan/SKILL.md

pre-round-scan

Skill286 starsChanged 5 months agoMITView on GitHub

Mandatory prelude for every role at the start of a round. Inventories available skills, MCP servers, plugins, sub-agents, and external references. Outputs which tools will be used in this round and which were considered but rejected, with reasons. Use as the very first action of every role skill in an arcgentic-managed project.

The file

We split this skill 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:

    EVERY role skill (plan-round, execute-round, audit-round, track-refs) invokes this as its first action, before any other reasoning.

    line 10

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill 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
SKILL.md

Pre-round scan

When to use

EVERY role skill (plan-round, execute-round, audit-round, track-refs) invokes this as its first action, before any other reasoning. Output goes into the role's handoff/verdict document as a "§ Toolkit use" section.

Rationale

R1.4 Moirai mandate (post-NEEDS_FIX): "default: multi-agent dispatch is the path, serial is the exception". Without a pre-round scan, agents repeatedly forget that MCP servers / agency-agents / skills exist and default to from-scratch implementation. The scan is mechanical insurance.

Procedure

  1. Read state.yaml to know which round + which role
  2. Inventory locally available:
    • Skills under ~/.claude/skills/ (user-level)
    • Plugins under ~/.claude/plugins/ (cached + installed)
    • MCP servers configured in ~/.claude.json
    • Sub-agents under ~/.claude/agents/
  3. Inventory project-local:
    • Project's CLAUDE.md / AGENTS.md mandates
    • Project's references/INDEX.md (if exists) — categorized OSS clones
    • Project's tech-debt registry (if exists)
  4. Map to round needs:
    • For each round-relevant subsystem, identify candidates from inventory
    • State which will be used + why
    • State which were considered + rejected + why
  5. Document in audit/handoff § "Toolkit use"

See references/scan-checklist.md for the explicit checklist.

Mandatory output format

### Toolkit use (pre-round scan)

**Skills available + considered:**
- arcgentic:foo — used (reason)
- arcgentic:bar — rejected (reason)
- ...

**MCP servers available + considered:**
- context7 — used for {library} docs lookup
- ...

**Sub-agents available + considered:**
- backend-architect — used for BA design pass
- ...

**External references available + considered:**
- references/X — used (used-what-part)
- references/Y — rejected (reason)
- ...

Failures count

Tool failures are first-class. If context7 returns 500 and you fall back to web search, record both the attempt and the fallback. Silent degradation is a Rule 2 violation in arcgentic's discipline ledger.

See also

references/scan-checklist.md — explicit checklist

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