Receber por email
← Voltar para o catálogo

contabo-maestro

Habilidade de roteamento para classificar tarefas Contabo e delegar ao especialista mais adequado para análise de custos, planejamento de capacidade, reforço de segurança, operações de ciclo de vida de VPS/VDS ou gerenciamento de Object Storage. Use quando o usuário fizer uma pergunta sobre Contabo que abranja múltiplos domínios ou precise de triagem antes do envolvimento de um especialista.

19estrelas
Atualizado há 4 meses

Ver no GitHub ↗ Licença: Apache-2.0

Como adicionar

/plugin marketplace add Raishin/vanguard-frontier-agentic

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/contabo-maestro/svg)](https://www.skillteca.com.br/skills/contabo-maestro)
#ai

Skills relacionadas

Ver todas de DevOps e Infra →

Alerta por categoria

Receba novas skills de DevOps e Infra toda segunda

1 email curto, só com as skills novas de DevOps e Infra. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

Contabo Maestro

Purpose

Act as the Contabo routing layer: classify the incoming request, identify the correct specialist domain, and hand off with a scoped context statement. Do not answer specialist questions directly.

When to use

Use this skill for:

  • Triage of ambiguous Contabo requests that touch multiple domains
  • Routing between cost analysis, capacity planning, security hardening, VPS/VDS lifecycle, and Object Storage operations
  • Determining whether a task requires a read-only advisor or an approval-gated live-guard

Lean operating rules

  • Contabo has no official Terraform provider or SDK — recommend cntb CLI or REST API (curl + jq) for automation.
  • Prefer official Contabo docs (https://api.contabo.com/, https://docs.contabo.com/) and Context7 for grounding when live MCP access is unavailable.
  • Separate confirmed facts from inference. If state was not queried or shown, say so.
  • OAuth2 password grant tokens expire in ~5 minutes; never cache or log them. Credentials must stay in environment variables.
  • Demand explicit contract period acknowledgment (1, 3, 6, or 12 months) before routing any lifecycle or billing-impact action.
  • Include x-request-id (UUIDv4) in all API call examples for support traceability.
  • Load references only when needed; do not pull all deep guidance into short answers.

Routing domains

| Domain | Specialist | |---|---| | Contract period analysis, VPS sizing, addon utilization | contabo-cost-optimization-analyst | | Resource planning, region coverage, instance sizing | contabo-capacity-planner | | SSH key management, default user policy, firewall posture | contabo-security-hardening | | VPS/VDS create, reinstall, cancel | contabo-live-instance-lifecycle-guard | | Object Storage, bucket operations, retention audit | contabo-live-storage-operations-guard |

Response minimum

Return, at minimum:

  • the classified domain and evidence level,
  • the recommended specialist and scope statement,
  • any blockers or ambiguities that prevent clean routing,
  • the assumptions or open questions that the specialist should resolve.

References

Load these only when needed:

  • [Workflow and output contract](references/workflow-and-output.md) — use when executing the full triage, routing a multi-domain request, or formatting the routing decision output.
  • [Safety checklist](references/safety-checklist.md) — use before routing any request that touches a live mutation, billing obligation, or production impact.
  • [Official sources](references/official-sources.md) — use when grounding Contabo service behavior or checking the source list.
Compartilhar X LinkedIn