Render data already supplied by the caller or validate review-command syntax. This skill does not load clusters, execute commands, mutate SQLite, send Slack messages, or file issues.
Overview
The MCP server exposes parse_review_command. It recognizes command shape and numeric cluster tokens, but it does not know the current run and cannot confirm that a cluster number exists. Formatting and confirmation text are library helpers, not separate MCP tools. Read the runtime contract for exact limits.
Prerequisites
- Start the triage MCP server when command parsing is requested.
- Supply already-redacted cluster, evidence, routing, and source-status data for display.
- Omit raw X text and secret-bearing URLs. This skill does not perform redaction.
Authentication
No external authentication is used. The local MCP parser accepts text and performs no network call.
Instructions
Format a summary
- Validate that every cluster record has an identifier, severity, report count, and state.
- Sort by the caller-provided severity ordering; do not compute or raise severity here.
- Show no more than five clusters in the compact view and state how many remain.
- Label synthetic repo evidence as synthetic. Omit an owner when routing is uncertain.
- Keep the compact result near 20 lines when the input permits it.
Parse a command
- Call parse_review_command with message_text.
- Return the parsed command, cluster number, optional lower-cased arguments, validity, and error.
- Validate the cluster number against the caller's current displayed list; the MCP parser cannot.
- Treat a valid parse as syntax only. Never claim the requested action ran.
Output
Return either terminal Markdown or a command parse receipt. Include:
- input cluster count and displayed count;
- source/degradation warnings provided by the caller;
- evidence provenance labels;
- parser validity plus separate current-run validation;
- a clear no-mutation statement for commands.
Examples
X Bug Triage - supplied preview
3 clusters
1. API timeout - low - 4 reports - owner uncertain
Evidence: synthetic Tier 3 records only
2 more clusters shown...
Input: dismiss 3 false positive
Parser: valid syntax; clusterNumber=3; args=false positive
Execution: not performed
Current-run validation: required
Error Handling
| Situation | Response |
|---|---|
| Missing cluster fields | Mark the row incomplete; do not fabricate values. |
| Parser reports invalid | Show its error and stop. |
| Parser accepts an out-of-range number | Reject it during current-run validation. |
| Command requests a mutation | Return syntax only and require a separate implementation/approval path. |
| Unredacted sensitive text is supplied | Refuse to display it. |
Guardrails
- Never emit action-confirmation prose unless an external executor supplies a successful receipt.
- Never say a cluster was dismissed, filed, merged, escalated, snoozed, split, or rerouted from parser output alone.
- Never claim Slack delivery; no Slack tool is exposed by this plugin.