At a glance
What it does
Diagnose why Reasonix capabilities such as skills, MCP servers, hooks, commands, and plugins are unavailable or misconfigured.
Before you choose it
This built-in Reasonix guide directs you to the relevant section of `reasonix doctor capabilities --json` and to focused references for skills, commands, hooks, MCP, plugins, and instructions. It emphasizes evidence-led diagnosis before changing configuration.
Best for
Reasonix users troubleshooting capability loading, discovery, priority, or configuration issues.
Common tasks
- Check static capability diagnostics without starting MCP subprocesses or making network calls.
- Investigate why a skill, slash command, hook, MCP server, plugin, or standing instruction is missing or misconfigured.
- Use live capability probing only after explicitly authorizing server startup.
Permissions and data
Static diagnostics are designed to avoid network calls and MCP startup. Live probing has broader exposure.
Permissions- Static reporting reads Reasonix capability configuration and sources.
- Live probing can start third-party MCP servers when explicitly authorized.
- Reports should redact tokens, headers, environment values, URL query strings, usernames, and external machine paths.
- The diagnostic UI can copy redacted JSON.
- Static diagnostics do not make network calls or start MCP subprocesses.
- Live probing may contact configured third-party servers.
- No credential requirement is declared for static diagnostics.
- Configured environment values or headers may be sent during authorized live probing.
Limitations
- This skill is a diagnostic guide; it does not automatically edit configuration, execute hooks, or reconnect servers.
- The supplied evidence does not verify successful installation or runtime behavior in a particular Reasonix version or environment.
- Live probing should not be run merely because a diagnostic request was made; explicit session authorization is required.
What DSHub checked
- The skill is an inline `reasonix-guide` artifact for diagnosing Reasonix capability configuration.
- Its static report is documented as not starting MCP subprocesses or making network calls.
- The repository snapshot and skill source are pinned to a specific commit.
What DSHub did not check
- Installation into a target Reasonix environment was not performed.
- No static or live diagnostic command was executed.
- Compatibility with a specific DSHub Harness version is not declared.
Pinned install
Primary action
This standalone skill does not have a DSH Plugin install action. Use its source documentation for the delivery method.
Maintainer source
Skill instructions
name: reasonix-guide description: "Diagnose missing or misconfigured Reasonix skills, commands, hooks, MCP servers, plugins, and instructions." runAs: inline
Reasonix capability diagnostics
For a loading or configuration problem, start with the relevant section of
reasonix doctor capabilities --json. This static report starts no MCP
subprocesses and makes no network calls. Use its issue codes, sources, and
remediations; a configuration question with enough evidence needs no full report.
References
Read only the page needed for the reported capability. These files are bundled
in the binary; a (builtin:...) source is not a local filesystem path.
| Capability | Reference |
|---|---|
| Skill discovery, priority, overrides | skills |
| Slash command naming and overrides | commands |
| Hook events, matching, timeouts | hooks |
| MCP sources, transport, startup | MCP |
| Plugin manifests and loading | plugins |
| Standing instruction scope and imports | instructions |
Read a page using read_skill with name="reasonix-guide" and
reference="references/skills.md" (substitute the page path). If the tool is
not directly exposed, use:
{"action":"call","capability_id":"tool:read_skill","arguments":{"name":"reasonix-guide","reference":"references/skills.md"}}
Runtime and permissions
Desktop Settings → Diagnostics opens a static report. Refresh repeats collection; the optional session-runtime view reads the active tab Host without starting MCP. The page can copy redacted JSON and link to the relevant settings tab; it never auto-edits config, executes hooks, or reconnects servers.
Live probing runs third-party code and may send configured environment/headers.
Use reasonix doctor capabilities --live --timeout 5s --json only when starting
those servers is explicitly authorized in the session. A diagnostic request
alone does not authorize configuration changes.
Keep tokens, header/env values, URL query strings, usernames, and external
machine paths out of reports. Use <workspace>/…, ~/…, or <external>/….
Operate deliberately
Install and manage
Prerequisites and target Profile
Target： Reasonix Profile
Delivery： Skill Files — https://raw.githubusercontent.com/esengine/DeepSeek-Reasonix/d9d152b3f77c6968557bfd9a9e709d8a2e86a7d1/internal/skill/builtincontent/reasonix-guide/SKILL.md。
Compatibility and access
Built In inline Reasonix diagnostic skill： Not declared in supplied evidence。
Review compatibility evidence ↗
Risk facts
Live diagnostics can start third-party servers and may send configured environment values or headers.
Evidence ↗Released under the MIT License, provided without warranty.
Evidence ↗Evidence and editorial reviewManifest, Bundle patch, distribution and freshness
Immutable evidence
Review status and source activity
Use the static diagnostic path first. Treat live probes as an explicit opt-in because they may run third-party code and expose configured connection data.
AI reviewed Sep 16, 2026, 2:21 PM UTC。GitHub facts last checked Sep 16, 2026, 2:21 PM UTC。
No material source change has been recorded since this evidence baseline.