dedicated-cloud-diag

Route TiDB Dedicated Cloud diagnosis 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-diag
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dedicated-cloud-diag
Source: https://github.com/alex-quan-001/nutshell-skills/tree/main/skills/diagnosis/dedicated-cloud-diag
Command: npx skills add https://github.com/alex-quan-001/nutshell-skills --skill dedicated-cloud-diag

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill eliminates the manual effort of selecting the correct Dedicated Cloud diagnosis sub-skill for a given issue, ensuring users get targeted, accurate diagnostic results without needing to understand the full sub-skill catalog.

Core Features & Use Cases

  • Intent-Based Sub-Skill Routing: Automatically matches user diagnosis requests to the most relevant Dedicated Cloud sub-skill using the pre-built, auto-generated sub-skill index.
  • Strict Read-Only Safety Boundary: Enforces read-only operations only during diagnosis workflows, preventing accidental mutations to cluster state, configuration, or permissions.
  • Use Case: When a user reports a TiDB Dedicated Cloud cluster scaling issue, this skill automatically routes the request to the dedicated diag-cluster-scale sub-skill to execute the targeted scaling diagnosis workflow.

Quick Start

Ask the AI to diagnose a scaling issue with your TiDB Dedicated Cloud cluster to automatically trigger routing to the appropriate diagnosis sub-skill.

Frequently Asked Questions about dedicated-cloud-diag

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

FAQPage Schema
How do I route a TiDB Dedicated Cloud diagnosis request to the correct troubleshooting workflow?

To route a TiDB Dedicated Cloud diagnosis request, intent-based matching automatically directs your issue to the most relevant specialized diagnostic workflow without manual selection.

What is the read-only safety boundary for TiDB Dedicated Cloud diagnostic workflows?

The read-only safety boundary for TiDB Dedicated Cloud diagnostics enforces strict operations preventing accidental mutations to cluster state, configuration, or permissions during troubleshooting.

Can I use automated routing for TiDB Dedicated Cloud cluster scaling issues?

Yes, you can use automated routing for TiDB Dedicated Cloud cluster scaling issues, which triggers the dedicated diag-cluster-scale sub-skill to execute the targeted scaling diagnosis workflow.

When do I need to escalate TiDB Dedicated Cloud remediation requests?

You need to escalate TiDB Dedicated Cloud remediation requests when change actions are required, as diagnosis workflows are strictly read-only and cannot mutate cluster state or configuration.

Does TiDB Dedicated Cloud diagnosis support telemetry evidence collection for stability incidents?

Yes, TiDB Dedicated Cloud diagnosis supports telemetry evidence collection for stability incidents, automatically routing the request to specialized sub-skills for component-level troubleshooting.