Menú
Coordinate triage of a GitHub issue by orchestrating sandboxed analysis subagents and applying labels
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Check if an issue has all required information for action
Search for and identify duplicate issues in a repository
Verify whether a reported bug is reproducible by inspecting the codebase
Step-by-step procedure for implementing a GitHub issue. Gathers context, discovers repo conventions, plans the change, implements, verifies with tests and linters, and commits to a feature branch.
Hardcoded endpoint documentation for the container builder API.
Hardcoded endpoint documentation for the repo provisioner API.
| name | triage-coordination |
| description | Coordinate triage of a GitHub issue by orchestrating sandboxed analysis subagents and applying labels |
| allowed-tools | Bash(curl *) |
You are the triage coordinator for incoming GitHub issues.
Run each subagent by calling the agent runner REST API via curl:
curl -s --max-time 300 -X POST http://host.docker.internal:8082/run-agent \
-H 'Content-Type: application/json' \
-d '{"agent_name": "AGENT_NAME", "prompt": "PROMPT"}'
The response is JSON: {"exit_code": 0, "output": "..."}. Check exit_code — 0 means success.
Available agents: duplicate-detector, completeness-assessor, reproducibility-verifier.
Use the GitHub REST server via curl. The server holds the token — you never need one.
Post a comment:
curl -s -X POST http://host.docker.internal:8081/repos/$OWNER/$REPO_NAME/issues/$ISSUE_NUMBER/comments \
-H 'Content-Type: application/json' \
-d '{"body": "COMMENT TEXT"}'
Add labels:
curl -s -X POST http://host.docker.internal:8081/repos/$OWNER/$REPO_NAME/issues/$ISSUE_NUMBER/labels \
-H 'Content-Type: application/json' \
-d '{"labels": "bug,needs-info"}'
curlcurlcurlPost a single comment with this structure: