Use an authenticated Centaur MCP deployment to find and call team-approved tools. It checks identity when permissions matter, follows the deployment’s current CLI help, and summarizes consequential changes with relevant identifiers or links.
Use an authenticated Centaur MCP deployment to discover and call team-approved tools. Use when a task requires Centaur, its tool catalog, or the user's Centaur identity and permissions.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Use Centaur's MCP tools for actions and context exposed by the user's deployment.
centaur_whoami before other Centaur tools.centaur MCP tool is listed, use it to list or search the tool catalog when the correct tool is unclear.centaur is available, inspect an unfamiliar CLI progressively with {"command": ["run", "<tool>", "--help"]}. Add known command and subcommand segments before --help until the relevant options and arguments are shown. Treat that help output as the current contract.centaur is available, run the command with {"command": ["run", "<tool>", "<argv>", "..."]}. Pass every CLI argument as a separate token and do not guess command names or options.centaur is not listed or cannot complete the request, use the legacy per-service MCP tools. Each accepts a method and arguments object. Call it with method: "help" when its methods or arguments are unclear.Centaur authorizes calls using the signed-in principal's live roles and grants. Never request, paste, print, or store Centaur OAuth tokens.
If no Centaur tools are available, explain that the client still needs the deployment-specific MCP endpoint.
codex mcp add centaur --url <CENTAUR_MCP_URL>, then run codex mcp login centaur. The --url flag is required for Streamable HTTP and OAuth.mcp_url, open /mcp, and authenticate the centaur server.centaur with the deployment's /mcp URL and complete its OAuth flow.Do not substitute a guessed hostname. Ask for the deployment URL when it is not already configured or supplied.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Investigate authentication, permission, credential, OAuth, token, secret, and API proxy failures by checking live VictoriaLogs evidence first. Summarize relevant status codes and error details, and distinguish upstream denials from local proxy or secret resolution problems.
Use this skill to translate a Console administrator’s request into Centaur permission changes. It can create supported principals and secrets, grant or revoke access, adjust Slack and sandbox permissions, and manage Slack Connect allowlists while checking for unsafe personal credential sharing.
Investigate Centaur incidents using VictoriaLogs for runtime logs and VictoriaMetrics for deployment and health metrics. The skill correlates a narrow time window with relevant code and workflow status, then reports a supported cause or bounded hypotheses and the evidence still needed.
Answer internal history and project context questions by searching indexed company information and checking relevant live sources such as Slack, Linear, Google Docs, Drive, Calendar, or Granola. Reconcile the evidence and cite dates or source links when available.
Build a new external service integration as a packaged Python CLI. The skill guides the project layout, API client, command-line interface, credential declarations, health check, and tests so the tool can be installed and used by agents.
Retrieve standalone DocSend documents or files in a DocSend Space for inspection, summarization, or download. The workflow handles email verification, passcodes, resumable sessions, and folder traversal, while reporting files that could not be fetched.