semantix-guide skillA
semantix-guide is agent-read markdown (skill) from gnosil/semantix: Troubleshoot and configure Semantix capabilities: Skills (project/custom/global/builtin priority, discovery dirs), Commands (override order, /dir:file naming), Hooks (11 events, automatic project loading, matchers, timeouts), MCP (semantix-agent.toml + .mcp.json + plugin packages, auto_start), plugin packages (native/Codex/Claude manifests), and AGENTS.md / instruction docs. Use when the user asks how to configure, debug missing skills/commands/hooks/MCP/plugins, or diagnose capability loading..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Semantix self-diagnostics guide
This skill is **inlined**. Prefer evidence over guessing.
## First action
1. Run a **static** capability report (no network, no MCP subprocesses):
```bash
semantix-agent doctor capabilities --json
```
2. Only if the user **explicitly** allows starting third-party MCP servers (may network and pass configured env/headers), run live probe:
```bash
semantix-agent doctor capabilities --live --timeout 5s --json
```
3. On desktop, open **Settings → Diagnostics** for the same report model. The desktop "include current session runtime" toggle only **reads** the active tab Host (connected/failed/deferred/disabled); it does **not** start MCP.
Do not invent auto-fixes. Surface stable issue codes, sources, and remediations from the report.
---
## Skills
### Config sources and priority
Winner per skill name (highest first):
1. **project** — `<workspace>/{.semantix,.agents,.agent,.claude}/skills/`
2. **custom** — `[skills].paths` (and plugin package skill roots)
3. **global** — `<Semantix home>/skills` and home convention dirs
4. **builtin** — shipped skills (including this guide)
…Read the whole file at its exact version.
How to install
mdr add gnosil/semantix/semantix-guide@git:20260821.2e010b8mdr add gnosil/semantix/semantix-guide@sha256:4abdc9ca42f51450Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_szo3hqi2sjl3qixt)
0 badge views in 30 days
Versions
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 (8669 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
gnosil/semantix · 719 stars · license MIT · pushed 2026-09-25 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_szo3hqi2sjl3qixt GET https://markdownregistry.com/api/v1/resolve?ref=gnosil/semantix/semantix-guide GET https://markdownregistry.com/api/v1/blob/4abdc9ca42f51450ddabc569dafeae072ded0b159912a3e5295c042690440ce6
Your agent 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.