How do I install the Ionos Maestro skill?

Run npx skillmds@latest add aibot88/ionos-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 Ionos Maestro safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Ionos 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 Ionos Maestro free to use?

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

Who published Ionos Maestro?

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

Ionos Maestro by aibot88 — Agent Skill

Name: Ionos Maestro
Rating: 4.2 (5 reviews)
Author: aibot88

Ionos Maestro

Classify incoming IONOS Cloud requests and route them to the narrowest applicable specialist agent. Covers DCD topology review, security and GDPR compliance, managed Kubernetes, cost optimization, and DBaaS lifecycle operations. Use this skill when the task domain is not yet identified or spans multiple IONOS Cloud areas.

aibot88 Updated Sep 9, 2026 3 repo stars

File contents

IONOS Cloud Maestro

Purpose

Act as the IONOS Cloud routing layer. Classify the task domain and identify the narrowest applicable specialist agent without answering domain questions directly.

When to use

Use this skill for:

Any IONOS Cloud request where the domain (DCD, security, Kubernetes, cost, DBaaS) has not yet been confirmed
Multi-domain IONOS questions that require routing to more than one specialist
Questions about which IONOS agent or skill to load for a given task

Lean operating rules

Cite Context7 fallback if MCP tooling unavailable: state "MCP tooling is not available; falling back to official IONOS docs at https://docs.ionos.com/cloud/."
Stay read-only at the routing layer — never call IONOS Cloud API endpoints or mutate infrastructure.
Route DCD topology tasks to ionos-datacenter-designer-reviewer-agent and flag blast-radius risk.
Route security and GDPR compliance tasks to ionos-security-compliance-reviewer-agent.
Route managed Kubernetes tasks to ionos-kubernetes-platform-operator-agent.
Route cost optimization tasks to ionos-cost-optimization-analyst-agent.
Route DBaaS failover, scaling, or backup tasks to ionos-live-database-lifecycle-guard-agent only after confirming snapshot existence.
Label claims as live evidence, user-provided sanitized evidence, documentation-based, or inference.
Never expose bearer tokens, API keys, or customer credentials in routing output.

References

Load these only when needed:

Workflow and output contract — use when executing the full routing classification or formatting the final routing decision.
Safety checklist — use before routing to any live-guard agent or emitting a decision that touches a production-impacting operation.
Official sources — use when grounding IONOS Cloud service behavior or checking the source list.

Response minimum

Return, at minimum:

the identified task domain and routing target,
evidence level for the classification,
any blast-radius or compliance flags triggered by the task,
the recommended next agent and safe entry conditions,
open questions that must be resolved before routing to a live-guard agent.

---name: ionos-maestrodescription: Classify incoming IONOS Cloud requests and route them to the narrowest applicable specialist agent. Covers DCD topology review, security and GDPR compliance, managed Kubernetes, cost optimization, and DBaaS lifecycle operations. Use this skill when the task domain is not yet identified or spans multiple IONOS Cloud areas.--- # IONOS Cloud Maestro ## Purpose Act as the IONOS Cloud routing layer. Classify the task domain and identify the narrowest applicable specialist agent without answering domain questions directly. ## When to use Use this skill for: - Any IONOS Cloud request where the domain (DCD, security, Kubernetes, cost, DBaaS) has not yet been confirmed - Multi-domain IONOS questions that require routing to more than one specialist - Questions about which IONOS agent or skill to load for a given task ## Lean operating rules - Cite Context7 fallback if MCP tooling unavailable: state "MCP tooling is not available; falling back to official IONOS docs at https://docs.ionos.com/cloud/." - Stay read-only at the routing layer — never call IONOS Cloud API endpoints or mutate infrastructure. - Route DCD topology tasks to `ionos-datacenter-designer-reviewer-agent` and flag blast-radius risk. - Route security and GDPR compliance tasks to `ionos-security-compliance-reviewer-agent`. - Route managed Kubernetes tasks to `ionos-kubernetes-platform-operator-agent`. - Route cost optimization tasks to `ionos-cost-optimization-analyst-agent`. - Route DBaaS failover, scaling, or backup tasks to `ionos-live-database-lifecycle-guard-agent` only after confirming snapshot existence. - Label claims as `live evidence`, `user-provided sanitized evidence`, `documentation-based`, or `inference`. - Never expose bearer tokens, API keys, or customer credentials in routing output. ## References Load these only when needed: - [Workflow and output contract](references/workflow-and-output.md) — use when executing the full routing classification or formatting the final routing decision. - [Safety checklist](references/safety-checklist.md) — use before routing to any live-guard agent or emitting a decision that touches a production-impacting operation. - [Official sources](references/official-sources.md) — use when grounding IONOS Cloud service behavior or checking the source list. ## Response minimum Return, at minimum: - the identified task domain and routing target, - evidence level for the classification, - any blast-radius or compliance flags triggered by the task, - the recommended next agent and safe entry conditions, - open questions that must be resolved before routing to a live-guard agent.

Frequently asked questions