Skill Doctor

Organization

dotCMS

skill-doctor

Use when a repo skill fails, produces errors, gives wrong instructions, or references stale information. Also use when a command from a skill returns "not found" or "unknown flag", when a skill references a file path that doesn't exist, when a skill's behavior doesn't match the codebase, or to list available skills, manage local overrides, check staleness, or optimize token usage and quality.

Overview

Publisher	dotCMS
Repository	`core`
Skill name	`skill-doctor`
Stars	971
Forks	487
Bundled files	1
Links	Skill source Repository Homepage

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 dotCMS on GitHub. Read the source before you install it.

Installation

Install the Skill Doctor 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/dotCMS/core/tree/main/.claude/skills/skill-doctor
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/dotCMS/core.git /tmp/core
mkdir -p .claude/skills
cp -r /tmp/core/.claude/skills/skill-doctor .claude/skills/skill-doctor

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

Use it in TypingMind

Enable Skill Doctor 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 Skill Doctor 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 Skill Doctor 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.

Skill Doctor

Diagnose issues with repository skills, manage local overrides, and optimize skill quality.

Scope: Skills in the current repository's .claude/skills/ directory only.

Routing

Parse $ARGUMENTS:

Pattern	Mode
`list`	list (all repo skills)
`info <skill>`	list (detail for one skill)
`feedback [skill] "<message>"`	feedback (quick note)
(empty) or `<skill-name>`	diagnose
`--optimize <skill>`	optimize
`--manage [skill]`	manage (status)
`clone/diff/sync/revert <skill>`	manage (lifecycle)
`report/gist/pr <skill>`	deliver
`resolve <skill>`	resolve

Unrecognized input: show this table and ask to rephrase. Then read ./reference.md for detailed procedures.

List

Dynamically discovers repo skills by reading .claude/skills/*/SKILL.md. Shows name, description, invocation, and override status. info <skill> reads the full SKILL.md to provide detailed usage guidance. All information comes from the skill files themselves — nothing is hardcoded. See reference.md for details.

Feedback

Lightweight path for quick notes. No investigation or quality gate — just scrub, preview, confirm, post. If skill name is omitted, ask which skill (or use the most recently invoked skill if known from conversation context). See reference.md for details.

Manage

Lifecycle: clone -> edit -> diff -> sync/revert -> pr/gist. Local overrides live at ~/.claude/skills/<name>/ with .skill-origin.json tracking.

Diagnose

Identify skill, validate it exists
Classify: invalid_command | wrong_assumption | stale_info | other
Investigate -- reproduce, root cause, determine fix, check related issues. Quality gate: confirmed problem + root cause + suggested fix
Duplicate check in Discussion thread. Match found: upvote, add context, or report anyway
Route: local override -> fix inline, stop. Repo -> offer clone-and-fix or report-only
Scrub PII, review with developer, deliver to GitHub Discussion + Slack

Optimize

Checks frontmatter, token efficiency (<500 words), structure quality, and staleness (file paths, commands, flags). Scored report with fixes. Local overrides fixed directly; repo versions cloned first.

Deliver & Resolve

Deliver: GitHub Discussion (primary, one thread per skill) + Slack #log-skill-feedback (optional notification). Check prerequisites first (gh auth, repo access). See reference.md.

Resolve: After fix PR merges, mark Discussion reports resolved, post Slack summary, offer to lock thread.

Common Mistakes

See reference.md for the full table. Key rules:

Never send reports without root cause + suggested fix
Always check Discussion thread for duplicates before reporting
Always run gh auth status before any delivery action
revert always shows diff and requires name confirmation

Override Warning

When ANY skill is invoked and ~/.claude/skills/<name>/.skill-origin.json exists, output before skill content:


SKILL OVERRIDE ACTIVE: <name>
  Using: ~/.claude/skills/<name>/ (local)
  Instead of: .claude/skills/<name>/ (repo)
  Cloned from: <sha> | Repo is N commits ahead
  Run /skill-doctor --manage <name> for options

Bundled files

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

reference.md22 KB

Frequently asked questions

What does the Skill Doctor AI skill do?

Why use Skill Doctor on TypingMind?

Because you install it once and use it with any model. Skill Doctor 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 Skill Doctor in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/dotCMS/core/tree/main/.claude/skills/skill-doctor. 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 Skill Doctor?

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 Skill Doctor?

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

Is the Skill Doctor AI skill free?

It is published on GitHub by dotCMS. Check the repository for licensing terms. 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

Auto Qa

openclaw

OrganizationPopular

Run OpenClaw-wide autonomous QA and live/stress campaigns across independent subsystem lanes, with verified fixes and a resumable evidence report.

Autoreview

Structured code review when explicitly requested, preferring OpenAI/Codex before Claude.

Claw Score

Audit or refresh OpenClaw maturity scorecard docs from root taxonomy, maturity scores, and QA evidence artifacts without using maintainer discrawl data or committed inventory reports.

Clawsweeper

Use for all ClawSweeper work: OpenClaw issue/PR sweep reports, repair jobs, cloud fix PRs, @clawsweeper maintainer mention commands, trusted ClawSweeper-reviewed autofix/automerge, GitHub Actions…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Skill Doctor

Routing

List

Feedback

Manage

Diagnose

Optimize

Deliver & Resolve

Common Mistakes

Override Warning

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now