Diagnose

Community

xiaolai

diagnose

Diagnose the cc-suite setup in the current project. Runs the full health check, explains every issue, and fixes what can be fixed automatically. Skill counterpart to /cc-suite:diagnose.

Overview

Publisher	xiaolai
Repository	`cc-suite`
Skill name	`diagnose`
Stars	56
Forks	21
Bundled files	1
License	ISC
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
1 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by xiaolai on GitHub. Read the source before you install it.

Installation

Install the Diagnose AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/xiaolai/cc-suite/tree/main/skills/cc-suite/diagnose
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/xiaolai/cc-suite.git /tmp/cc-suite
mkdir -p .claude/skills
cp -r /tmp/cc-suite/skills/cc-suite/diagnose .claude/skills/diagnose

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Diagnose in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Diagnose on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Diagnose is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Diagnose

Run the structured diagnostic engine and act on its report. Skill counterpart to /cc-suite:diagnose — both are thin wrappers around the same engine, scripts/diagnose.py, which owns every check, its classification, and its repair mapping. Do not re-implement checks here.

When to Use

At the start of a session when bridge artifacts may be missing or stale
After updating cc-suite to confirm the new version is wired as expected
When $audit, $audit-fix, or any $claude-* skill behaves unexpectedly

Workflow

Step 0: Resolve the plugin root

CLAUDE_PLUGIN_ROOT is set by Claude Code only — in a Codex or Antigravity session it is unset. Resolve the root from the bridged skills symlink (it points at <plugin-root>/skills/cc-suite):

bash
PLUGIN_ROOT="${CLAUDE_PLUGIN_ROOT:-$(dirname "$(dirname "$(readlink -f .claude/skills/cc-suite 2>/dev/null)")")}"
[ -d "${PLUGIN_ROOT}/scripts" ] || echo "! cannot resolve the cc-suite plugin root — ask the user to type /cc-suite:bridge-skills in Claude Code first, or export CLAUDE_PLUGIN_ROOT"

Stop if it could not be resolved.

Step 1: Run the engine

bash
python3 "${PLUGIN_ROOT}/scripts/diagnose.py" --json

The JSON: enabled_tools, checks[] (id, label, status, detail, fix{auto[], manual, restart_required}), summary. Statuses: healthy / issue (fixable) / info / expected_absent / manual / skipped. The engine honors the Enabled Tools selection — a deselected tool's absent artifacts are expected_absent, never issues. Add --boot-test for the network-dependent claude-octopus handshake (tests the version actually registered in .codex/config.toml) when delegation misbehaves.

Step 2: Report

Render the buckets in order — Issues, Manual action needed, Information, Healthy, Expected absent/Skipped — emitting Information even on the no-issues path. If there are no issues and nothing manual: report healthy and stop.

Step 3: Fix

Ask: "Fix all auto-fixable issues now? (yes / show commands only / cancel)". If yes, for each issue check run its fix.auto commands in order; a non-zero exit is reported verbatim and that check is NOT counted as fixed. The model_pin fix is an edit, not a command: rewrite the - **Default model**: line in .cc-suite.md to latest and touch nothing else. fix.manual and manual-status items go to the user's to-do list untouched.

Step 4: Verify by re-running the engine

Run the same engine invocation again and diff per check id: fixed (issue → healthy/expected_absent), pending restart (fix applied with restart_required: true, still flagged — expected until the host restarts), remaining. Report the three counts. Never claim a fix worked from the fix command's exit code alone.

If issues remain, tell the user: "Next step: use the repair skill here, or type /cc-suite:repair in Claude Code, for a full non-interactive re-run of all setup scripts. If that also fails, type /cc-suite:init in a Claude Code session."

Example Invocations

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

agents/openai.yaml1 KB

Frequently asked questions

What does the Diagnose AI skill do?

Diagnose the cc-suite setup in the current project. Runs the full health check, explains every issue, and fixes what can be fixed automatically. Skill counterpart to /cc-suite:diagnose.

Why use Diagnose on TypingMind?

Because you install it once and use it with any model. Diagnose is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Diagnose in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/xiaolai/cc-suite/tree/main/skills/cc-suite/diagnose. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Diagnose?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Diagnose?

As many as you like. As long as a model supports skills, you can use Diagnose with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Diagnose AI skill free?

Yes. It is published on GitHub by xiaolai under the ISC license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Control Ui E2e

openclaw

OrganizationPopular

Use when designing, testing, fixing, or extending the OpenClaw Control UI GUI, including UI stress-test galleries with feedback inputs, Vitest + Playwright end-to-end checks, mocked Gateway flows,…

Deslop

Diff-scoped AI-slop cleanup pass: strip comment slop, defensive-check slop, type-laundering, and style drift from the current branch diff before autoreview.

Discord Clawd

Use to talk to the Discord-backed OpenClaw agent/session; not for archive search.

Discrawl

Discord archive: search, sync freshness, DMs, summaries, TUI, repo/release work.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Diagnose

When to Use

Workflow

Step 0: Resolve the plugin root

Step 1: Run the engine

Step 2: Report

Step 3: Fix

Step 4: Verify by re-running the engine

Example Invocations

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now