diagnosing-commands SKILL.md skillA
diagnosing-commands from evovexai/evoflow is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add evovexai/evoflow/diagnosing-commands@git:20261016.a5d3a8bPins git:20261016.a5d3a8b in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- evovexai/evoflow
- Path
backend/packages/harness/evoflow/plugins/builtin/plugins/evoflow-guide/skills/diagnosing-commands/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261016.a5d3a8b, committed Oct 16, 2026
- Size
- 3,524 bytes
- Repository stars
- 484
- License
- a license file GitHub does not identify
Use to diagnose and fix EvoFlow slash command problems. Applies when a /command is missing, overridden by another plugin, has frontmatter errors, does not substitute arguments, or its body is not injected. Provides discovery rules, invocation mechanism, and a step-by-step localization and repair workflow.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Diagnosing Commands Configuration
Goal: reduce any command problem to a concrete plugin file edit.
## 1. How commands work in EvoFlow
EvoFlow slash commands come from **plugins only**. There is no standalone user command configuration file.
- Each plugin's `commands/*.md` files are commands
- The filename (without `.md`) is the command name (e.g. `commands/review.md` → `/review`)
- Nested directories join with colon: `commands/review/code.md` → `/review:code`
- A command `.md` file may have YAML frontmatter (`name`, `description`) + body
## 2. Invocation mechanism
When a user message starts with `/name`:
1. The backend matches the token against enabled plugins' command lists (`plugins/runtime.py`)
2. If matched, the command's markdown body is inlined into the message (max 4000 chars, `_INVOKED_COMMAND_BODY_MAX_CHARS`)
3. If not matched, only command metadata (name + description) is injected as context
The regex for command detection: `/(?<![\w/\\-])/([a-zA-Z0-9][a-zA-Z0-9_-]{0,63})` — matches `/name` not preceded by word chars, slashes, or backslashes.
## 3. Common symptoms → causes → fixes
### Command not found
…Read the whole file at its exact version.
How to install
mdr add evovexai/evoflow/diagnosing-commands@sha256:d858f69ab201ae75The line at the top of this page pins the label git:20261016.a5d3a8b, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_bdj5mvqh7f7gjdex)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 16, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (3524 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
evovexai/evoflow · 484 stars · license a license file GitHub does not identify · pushed 2026-10-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_bdj5mvqh7f7gjdex GET https://markdownregistry.com/api/v1/resolve?ref=evovexai/evoflow/diagnosing-commands GET https://markdownregistry.com/api/v1/blob/d858f69ab201ae755897815f68b81c71e6bb2fb63454ec66d70c9641e4192db8
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.