ccdash

Route natural language CCDash questions to CLI commands and output modes.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/miethe/signal_to_system --skill ccdash
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ccdash
Source: https://github.com/miethe/signal_to_system/tree/main/.agents/skills/ccdash
Command: npx skills add https://github.com/miethe/signal_to_system --skill ccdash

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill turns natural-language questions about CCDash project health, feature forensics, sessions, workflows, and server access into the correct CLI actions, so operators and agents can get reliable answers without memorizing the command tree.

Core Features & Use Cases

  • Intent Routing: Maps requests to the right CCDash subcommand, output mode, and recipe for multi-step investigations.
  • Project and Feature Analysis: Handles status checks, feature deep-dives, session intelligence, workflow failure analysis, and narrative reports.
  • Setup and Recovery Guidance: Helps with target onboarding, authentication, connectivity checks, and graceful fallback to doctor-style diagnostics when a call fails.
  • Example Use Case: A user asks why a feature is delayed, and the Skill routes them through feature detail, linked sessions, workflow failures, and an after-action report.

Quick Start

Ask the skill to analyze your CCDash question and route it to the best command, such as checking project health, investigating a feature, or diagnosing a broken target.

Frequently Asked Questions about ccdash

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

FAQPage Schema
How do I map natural language questions to CCDash CLI commands?

To map natural language questions to CCDash CLI commands, this skill applies intent routing to translate project health triage or feature forensics queries into the correct subcommands and output modes automatically.

What is the best way to investigate a delayed feature using session analysis?

The best way to investigate a delayed feature is through provenance-aware chaining, which routes you through feature details, linked sessions, workflow failures, and generates a narrative after-action report.

How do I troubleshoot target onboarding and authentication failures?

To troubleshoot target onboarding and authentication failures, route your query to trigger graceful fallback through doctor-style diagnostics that check server connectivity and auth states.

Can I get narrative reports for workflow failure investigation without memorizing the command tree?

Yes, you can get narrative reports for workflow failure investigation by asking natural-language questions, which routes your request to the correct recipe for multi-step diagnostics without needing the command tree.

Why does my CCDash session analysis fail when server connectivity drops?

Session analysis fails when server connectivity drops because the routing requires active connections, but it provides a graceful fallback through doctor checks to diagnose the connectivity or auth issue.