aionui-troubleshooting

Diagnose DCode installations by inspecting conversations, providers, cron jobs, MCP servers, and logs.

Updated Aug 19, 2026
One-click install
npx skills add https://github.com/Dhanuzh/DCode-Core --skill aionui-troubleshooting-dhanuzh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aionui-troubleshooting
Source: https://github.com/Dhanuzh/DCode-Core/tree/main/crates/dcode-app/assets/builtin-skills/aionui-troubleshooting
Command: npx skills add https://github.com/Dhanuzh/DCode-Core --skill aionui-troubleshooting-dhanuzh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When DCode misbehaves—a conversation hangs, an LLM provider call fails, a scheduled task never runs, or an MCP server shows no tools—this Skill gives you a structured, read-only diagnostic workflow instead of manual guesswork. ## Core Features & Use Cases - Cross-Domain Overview: Run a single overview command to spot unhealthy providers, failing cron jobs, MCP servers without tools, and stuck conversations. - Targeted Diagnostics: Drill into conversation runtime state, message history, provider health, scheduled task state, team member status, backend health, and log tails. - Safe Read-Only Operation: All commands are read-only with automatic redaction of secrets, tokens, and passwords. - Use Case: A user reports their scheduled task did not run. You run the cron summary command, inspect the nested state fields like last_status and last_error, and report the root cause with evidence. ## Quick Start Ask the assistant to run a DCode diagnostic overview to find out why the application is misbehaving.

Frequently Asked Questions about aionui-troubleshooting

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

FAQPage Schema
How do I diagnose a stuck conversation in DCode?

Run the diagnose conversations get command with the conversation_id set to current, then re-check it and compare runtime fields and message progress. A single running snapshot does not prove a hang; confirm only after repeated unchanged snapshots.

How do I check why a scheduled task did not run?

Run diagnose cron summary and inspect the nested state fields: state.last_status, state.last_error, state.run_count, and state.next_run_at_ms. Timestamps are millisecond epoch integers, not human-readable dates.

Why does my MCP server show no tools in DCode?

An enabled server with tool_count of zero usually means startup failed, the command is unavailable, credentials are invalid, or the server crashed before tool registration. Run diagnose mcp summary to inspect server state.

Can this troubleshooting skill change DCode configuration?

No, every diagnose command is strictly read-only. To change configuration, use the separate aionui-config skill, and use the cron skill for scheduled task creation or updates.

Does the diagnose CLI expose secrets or tokens?

The CLI redacts known secret fields such as provider keys, MCP headers, tokens, and passwords by default. You should still summarize sensitive findings carefully and never print raw secret values.