Automated summary
Runs a full diagnostic of the Matrix plugin and attempts to automatically repair detected issues.
Strengths
- Checks six key areas: directory, database, configuration, hooks, code index, and repo detection
- Auto-fixes common problems such as a missing directory, broken database connection, or invalid config
- Produces a pre-filled GitHub issue template when automatic fixes fail
Limitations
- Fully dependent on the Matrix plugin and the matrix_doctor MCP tool; unusable without them
- Auto-fixes may reset configuration to defaults, potentially overwriting custom settings
- Only covers Matrix plugin problems, not issues in the Matrix application itself
Use it when the Matrix plugin is not working or to periodically verify its health.
Avoid it if you do not use the Matrix plugin or need to troubleshoot something unrelated to it.
Security analysis
CautionThe skill is narrowly scoped to a Matrix diagnostic MCP tool and does not invoke shell commands, network calls, or obfuscated payloads. However, its default auto-fix behavior can modify or reset local configuration/database state, so it warrants caution rather than being fully safe.
- •Auto-fix defaults to true and may create directories, reinitialize the database, reset configuration to defaults, and trigger reindexing without explicit user confirmation.
Examples
Run matrix diagnostics and fix anything that's broken.Check matrix health but don't change anything, just report what's wrong.The Matrix plugin isn't working, can you troubleshoot it and tell me what's going on?name: Matrix Doctor description: This skill should be used when the user asks to "run matrix diagnostics", "check matrix health", "fix matrix issues", "troubleshoot matrix", or mentions matrix not working. Runs comprehensive diagnostics on the Matrix plugin and automatically fixes issues. user-invocable: true agent: haiku allowed-tools:
- mcp__plugin_matrix_matrix__matrix_doctor
Matrix Doctor
Run comprehensive diagnostics on the Matrix plugin and automatically fix issues when possible.
What It Does
- Checks Matrix Directory: Verifies ~/.claude/matrix/ exists and is writable
- Checks Database: Tests connection, validates schema version
- Checks Configuration: Validates config file, checks for missing sections
- Checks Hooks: Verifies hooks are installed correctly
- Checks Code Index: Confirms repository is indexed
- Checks Repo Detection: Tests fingerprinting works
Auto-Fix Capabilities
The doctor will automatically attempt to fix:
- Missing Matrix directory (creates it)
- Database connection issues (reinitializes)
- Invalid/missing configuration (resets to defaults)
- Missing code index (triggers reindex)
Usage
Call the matrix_doctor tool with:
autoFix: true(default) - Attempt to fix issues automaticallyautoFix: false- Only run diagnostics without fixing
If Issues Cannot Be Fixed
If the doctor finds issues that cannot be automatically fixed:
- A GitHub issue template will be generated
- The user should be directed to open an issue at: https://github.com/ojowwalker77/Claude-Matrix/issues/new?template=bug_report.md
- Include the full diagnostic output in the issue
Expected Output
The tool returns a DoctorResult object containing:
healthy: boolean indicating overall healthchecks: array of diagnostic resultsenvironment: OS, Bun version, pathssuggestions: array of recommended actionsissueTemplate: pre-filled GitHub issue template (if issues found)
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/matrix-doctor-mmio70rh/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/matrix-doctor-mmio70rh' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/matrix-doctor-mmio70rh/download' --output '.skill-downloads/matrix-doctor-mmio70rh/SKILL.md.part' && mv '.skill-downloads/matrix-doctor-mmio70rh/SKILL.md.part' '.skill-downloads/matrix-doctor-mmio70rh/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.
Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/matrix-doctor-mmio70rh/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
Configure a Chat Channel with SecretRefs
DevOps
Set up chat channels using non-interactive commands, with secrets only as SecretRefs. Covers gather, mutate, repair, and prove steps for reliable delivery.
Investigate ClickHouse CI Failures
DevOps
Investigate a ClickHouse CI failure end-to-end from a PR or S3 report URL. Fetches failed tests, classifies flaky vs real regression, and checks for existing issues/fixes.
Ansible PR Review
DevOps
Reviews an Ansible PR following the project's standardized process, including changelog checks, test coverage validation, and feedback tracking.