Traceway with write access

This skill drives the traceway-write CLI (or the write MCP server) to make the routine changes an on-call engineer makes: archive issues, acknowledge and resolve pages, snooze or toggle alert rules, run monitors, write post-mortems and mark slow endpoints.

To explain how a part of Traceway works before or after a change (what acknowledging a page does to escalation, how a snooze differs from disabling a rule, how a monitor opens an incident), use the traceway-learn skill. It is the full product guide. Over MCP the same guide is the traceway://knowledge/learn resources.

For pure investigation (debugging an issue, latency analysis), the read-only traceway skill has the deeper playbooks. Its commands work the same way here: every read command of traceway also exists in traceway-write.

If a traceway-write MCP server is connected (stdio traceway-write mcp, or https://<instance>/mcp/write), prefer its tools over shelling out. Its resources carry this skill's knowledge, and its tool names are listed in the table below.

Setup

1. Install the write CLI

traceway-write is a separate binary with its own login, so a read-only traceway install can never be upgraded to write in place.