How do I install the Ovhcloud Maestro skill?

Run npx skillmds@latest add vincentchuwaichow/ovhcloud-maestro in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Ovhcloud Maestro safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Ovhcloud Maestro?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Ovhcloud Maestro free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Ovhcloud Maestro?

VincentChuWaiChow (@vincentchuwaichow) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Ovhcloud Maestro by vincentchuwaichow

Name: Ovhcloud Maestro
Author: VincentChuWaiChow

Ovhcloud Maestro

Classify incoming OVHcloud requests by domain and route to the narrowest qualified specialist agent. Use when the user's task spans or is unclear across IAM, FinOps, Kubernetes, networking, or live-guard KMS domains. Does not answer specialist questions directly; produces a routing verdict with evidence and hands off with a clear scope statement.

File contents

OVHcloud Maestro

Purpose

Act as the OVHcloud task router: classify the request, identify the narrowest qualified specialist, and hand off with a clear scope statement. Do not resolve specialist questions at this layer.

When to use

Use this skill when:

The user's OVHcloud request spans multiple domains (IAM + cost, networking + Kubernetes)
The domain of the task is unclear or under-specified
You need to dispatch to ovhcloud-iam-policy-review, ovhcloud-cost-finops-analyst, ovhcloud-kubernetes-platform-operator, ovhcloud-network-architect, or ovhcloud-live-kms-key-destruction-guard

Lean operating rules

Prefer OVHcloud API console or Terraform provider docs for classification signals; if MCP tooling is unavailable, fall back to https://help.ovhcloud.com/ and Context7.
Separate confirmed domain classification from inference. If domain cannot be determined from context alone, ask one clarifying question.
Challenge vague scope before routing; a mis-routed task wastes specialist context.
Never attempt live OVHcloud API mutations from the routing layer.
Keep routing output minimal: domain verdict, target specialist, and classification signals.

References

Load these only when needed:

Workflow and output contract — use when executing the full routing workflow or formatting the routing verdict.
Safety checklist — use before dispatching to a live-guard or privileged specialist.
Official sources — use when grounding OVHcloud service classification or checking the source list.

Response minimum

Return, at minimum:

the domain verdict and confidence level,
the recommended specialist agent,
the classification signals used,
any blockers that prevent confident routing,
one clarifying question if domain is ambiguous.

---name: ovhcloud-maestrodescription: Classify incoming OVHcloud requests by domain and route to the narrowest qualified specialist agent. Use when the user's task spans or is unclear across IAM, FinOps, Kubernetes, networking, or live-guard KMS domains. Does not answer specialist questions directly; produces a routing verdict with evidence and hands off with a clear scope statement.---# OVHcloud Maestro## PurposeAct as the OVHcloud task router: classify the request, identify the narrowest qualified specialist, and hand off with a clear scope statement. Do not resolve specialist questions at this layer.## When to useUse this skill when:- The user's OVHcloud request spans multiple domains (IAM + cost, networking + Kubernetes)- The domain of the task is unclear or under-specified- You need to dispatch to `ovhcloud-iam-policy-review`, `ovhcloud-cost-finops-analyst`, `ovhcloud-kubernetes-platform-operator`, `ovhcloud-network-architect`, or `ovhcloud-live-kms-key-destruction-guard`## Lean operating rules- Prefer OVHcloud API console or Terraform provider docs for classification signals; if MCP tooling is unavailable, fall back to https://help.ovhcloud.com/ and Context7.- Separate confirmed domain classification from inference. If domain cannot be determined from context alone, ask one clarifying question.- Challenge vague scope before routing; a mis-routed task wastes specialist context.- Never attempt live OVHcloud API mutations from the routing layer.- Keep routing output minimal: domain verdict, target specialist, and classification signals.## ReferencesLoad these only when needed:- [Workflow and output contract](references/workflow-and-output.md) — use when executing the full routing workflow or formatting the routing verdict.- [Safety checklist](references/safety-checklist.md) — use before dispatching to a live-guard or privileged specialist.- [Official sources](references/official-sources.md) — use when grounding OVHcloud service classification or checking the source list.## Response minimumReturn, at minimum:- the domain verdict and confidence level,- the recommended specialist agent,- the classification signals used,- any blockers that prevent confident routing,- one clarifying question if domain is ambiguous.

Frequently asked questions