arch://guidance/v1/manifest is the current tool catalog.
Tool catalog
For every tool, grouped by Build, Evaluate, Optimize, Debug, and Analyze, see Build with Arch using MCP. This page covers the guidance skills, guarded edits, and how each Studio task maps to a tool.Guidance skills
A skill is a set of reusable instructions that helps the assistant choose a safe, consistent procedure for a type of task. Skills don’t add MCP tools or grant permissions. Install them with the guidance installer described in Work with a coding assistant.
Never edit the installed
arch-* skill folders, because the installer manages them. To add your team’s procedures, build a customer skill on top of them.
How guarded edits work
platform_agents:edit_dsl uses the expectedSourceHash returned by the latest read of that agent. This compare-and-save guard refuses the edit if the definition changed after it was read, which protects a newer Studio or assistant edit from being overwritten. For a new draft, the tool accepts an explicit null hash.
After a stale-edit refusal, read the current definition, compare it with the intended change, reapply only the edits that are still needed, validate, and read the result back. The guard detects concurrent changes; it doesn’t validate the agent’s behavior. Use a whole-project import only for a whole-project package, not for a single agent edit.