dedicated-cloud-toolkit

Route Dedicated Cloud operation requests to specialized sub-skills.

Updated Jun 3, 2026
One-click install
npx skills add https://github.com/alex-quan-001/nutshell-skills --skill dedicated-cloud-toolkit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dedicated-cloud-toolkit
Source: https://github.com/alex-quan-001/nutshell-skills/tree/main/skills/utilities/dedicated-cloud-toolkit
Command: npx skills add https://github.com/alex-quan-001/nutshell-skills --skill dedicated-cloud-toolkit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, and includes scripts (resource) components.

What problem does it solve?

Manually identifying and selecting the correct Dedicated Cloud sub-skill for a specific task is inefficient and prone to error. This skill acts as the central entry point for the Dedicated Cloud toolkit, automatically detecting your intent and routing your request to the most relevant specialized sub-skill, so you don't have to manage sub-skill discovery or execution details yourself.

Core Features & Use Cases

  • Intent-based routing: Automatically matches your request to the correct Dedicated Cloud sub-skill by analyzing your query against the curated sub-skill index.
  • Full workflow coverage: Supports both read-only query actions (such as retrieving cluster custom resources) and operational change actions for remediation tasks.
  • Built-in safety guardrails: Enforces mandatory prerequisite checks (including reading required mechanism documentation and validating DevOps API token availability) and excludes non-executable template sub-skills from runtime routing.
  • Use Case: When you need to look up the cluster CR for a specific Dedicated Cloud cluster, this skill automatically routes your request to the dedicated get-cluster-cr sub-skill, which handles authentication, API execution, and output formatting.

Quick Start

Use the dedicated-cloud-toolkit skill to retrieve the cluster custom resource (CR) for your Dedicated Cloud cluster with ID <your-cluster-id>.

Frequently Asked Questions about dedicated-cloud-toolkit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically route Dedicated Cloud cluster operations instead of manually selecting sub-skills?

Automatically route Dedicated Cloud cluster operations by using an intent detection entry point that analyzes your query against a sub-skill index. This eliminates manual sub-skill discovery and directly matches your request to the appropriate specialized workflow.

How do I retrieve the cluster custom resource for a specific Dedicated Cloud cluster?

Retrieve the cluster custom resource by submitting your cluster ID to the toolkit. The intent detection mechanism routes your request to the get-cluster-cr sub-skill, which handles DevOps API authentication, execution, and output formatting.

Do I need a DevOps API token to execute Dedicated Cloud cluster remediation tasks?

Yes, you need a DevOps API token to execute Dedicated Cloud cluster remediation tasks. The toolkit enforces built-in safety guardrails that validate DevOps API token availability before routing any operational change actions to sub-skills.

What prerequisite checks are required before running Dedicated Cloud toolkit workflows?

Prerequisite checks for Dedicated Cloud toolkit workflows include reading required mechanism documentation and validating DevOps API token availability. These enforced guardrails ensure sub-skills follow documented execution and verification procedures.

Does the dedicated-cloud-toolkit support read-only cluster resource queries?

Yes, the dedicated-cloud-toolkit supports read-only cluster resource queries. It provides full workflow coverage that includes both retrieving cluster custom resources and executing operational change actions for remediation tasks.

Why are non-executable template sub-skills excluded from runtime routing?

Non-executable template sub-skills are excluded from runtime routing to enforce safety guardrails. This prevents the intent detection mechanism from accidentally routing operational requests to incomplete workflows that lack documented execution and verification procedures.