Menu
Discover the repo provisioner API via its tool-use schema.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Check if an issue has all required information for action
Search for and identify duplicate issues in a repository
Coordinate triage of a GitHub issue by orchestrating sandboxed analysis subagents and applying labels
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.
| name | tooluse-provisioner |
| description | Discover the repo provisioner API via its tool-use schema. |
The repo provisioner server exposes a tool-use schema describing each operation as a tool with name, description, HTTP endpoint, and input schema. Fetch it:
curl -s "$PROVISIONER_URL/tools.json" | python3 -m json.tool
Each tool definition tells you:
name — what the tool doesendpoint — the HTTP path to callmethod — GET or POSTinput_schema — the JSON body schema (for POST requests)Use this to construct your API calls. All authenticated endpoints require:
Authorization: Bearer $API_TOKEN