How do I install the Pre Round Scan skill?

Run npx skillmds@latest add arch1esun/pre-round-scan in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Pre Round Scan safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Pre Round Scan?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Pre Round Scan free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Pre Round Scan?

Arch1eSUN (@arch1esun) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Pre Round Scan by arch1esun — Agent Skill

Name: Pre Round Scan
Author: Arch1eSUN

Pre Round Scan

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.

Arch1eSUN Updated Sep 21, 2026

File contents

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

Read state.yaml to know which round + which role
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/
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)
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
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.

---name: pre-round-scandescription: 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.---# Pre-round scan## When to useEVERY 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.## RationaleR1.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.## Procedure1. **Read state.yaml** to know which round + which role2. **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 + why5. **Document in audit/handoff § "Toolkit use"**See `references/scan-checklist.md` for the explicit checklist.## Mandatory output format```markdown### 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 countTool 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

Frequently asked questions