Semantix Guide logo

Semantix Guide

Community
Gnosil
semantix-guide

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.

Overview

PublisherGnosil
Repositorysemantix
Skill namesemantix-guide
Stars
820
Forks
10
Bundled files
Instructions only
LicenseMIT
Links
  • 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.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by Gnosil on GitHub. Read the source before you install it.

Installation

Install the Semantix Guide AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

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.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/Gnosil/semantix/tree/main/harness/skill/builtincontent/semantix-guide
  4. 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.
2

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/Gnosil/semantix.git /tmp/semantix
mkdir -p .claude/skills
cp -r /tmp/semantix/harness/skill/builtincontent/semantix-guide .claude/skills/semantix-guide
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Semantix Guide 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 Semantix Guide 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 Semantix Guide 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.

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
  1. 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
  1. 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)

Same name: higher scope wins; lower scopes are shadowed. [skills].disabled_skills hides a name from List/Read entirely.

Discovery conventions: .semantix, .agents, .agent, .claude (see config.ConventionDirs). Layouts: <name>/SKILL.md or flat <name>.md (Claude flat files need skill frontmatter).

Checks

EntryHow
CLIsemantix-agent doctor capabilities → Skills section
DesktopSettings → Skills; Settings → Diagnostics
Agent/skill list, /semantix-guide, run_skill

Symptom → cause → fix

SymptomLikely causeFix
Skill missing from indexDisabled, shadowed, missing description, wrong rootCheck report codes skill.shadowed, skill.missing_description, disabled list, discovery roots
Builtin overriddenProject/global same nameRename or remove user skill; disable if intentional
Flat Claude file ignoredNo skill frontmatter under .claude/skillsAdd description: / runAs: frontmatter or use SKILL.md folder
Body never loadsExpected: bodies are on-demandInvoke via /name or run_skill

Ordered triage

  1. semantix-agent doctor capabilities --json → Skills
  2. Confirm name not in disabled_skills
  3. Confirm winner Path/Scope; if shadowed, inspect lower-priority roots
  4. Missing description: skill may load but index placeholder is weak — add description:
  5. Reopen session / Refresh Skills after config changes

Commands (slash templates)

Priority

config.CommandDirsForRoot: home convention commands → Semantix home commands → project convention commands. Later directory overrides earlier on name clash (command.Load).

Name from path: git/commit.md → /git:commit (slashes → :).

Checks

CLI/Desktop Diagnostics → Commands; invoke /name in chat.

Symptom → cause → fix

SymptomCauseFix
Wrong bodyShadowed by later dirCheck command.shadowed winners
Missing commandWrong dir / extensionPlace *.md under a scanned commands/ root
Parse failUnreadable fileFix permissions / encoding (command.read_failed)

Hooks

Events (11)

PreToolUse, PostToolUse, PermissionRequest, UserPromptSubmit, Stop, PostLLMCall, SessionStart, SessionEnd, SubagentStop, Notification, PreCompact.

Blocking (exit 2 can gate the loop): PreToolUse, UserPromptSubmit. Others warn or contribute context only.

Sources

  • Project: <workspace>/.semantix/settings.json — loaded automatically
  • Plugin packages: installed enabled packages
  • Global: <Semantix home>/settings.json (always)

Match field is an anchored regex: file does not match read_file; use .*file or *. Timeout is milliseconds (defaults 5s gating / 30s other).

Checks

/hooks, Settings → Hooks, Diagnostics → Hooks.

Symptom → cause → fix

SymptomCauseFix
Project hooks silentWrong workspace / restart requiredConfirm the project path and restart Semantix after saving
Matcher never firesNon-anchored assumption / bad regexFix match (hook.invalid_matcher)
Command missingEmpty command / missing context fileFix settings entry
Malformed JSONInvalid settings.jsonRepair JSON (file yields no hooks, no crash)

MCP servers

Merge order

config.LoadForRoot merges:

  1. User/project TOML [[plugins]] (higher name wins vs later sources when already defined)
  2. Project .mcp.json servers not already in TOML
  3. Enabled plugin packages MCP (skipped if name already defined)

Transports: stdio (default), http / streamable-http, sse. auto_start=false skips startup; nil/true = automatic. Tier eager blocks boot handshake; empty/background connects without blocking chat.

Env/header values may contain secrets — diagnostics list keys only.

Checks

ModeBehavior
Static doctorConfig validity, command path / URL shape, start intent — no subprocess
CLI --liveIsolated Host via boot.PluginSpecsForRoot + plugin.Start; auto-start only; concurrency 4; always Close
Desktop runtimeRead active tab Host only

Symptom → cause → fix

SymptomCauseFix
Not connectedauto_start=false or failed startEnable / fix command/URL (mcp.command_not_found, mcp.start_failed)
No toolsConnected but empty tools/listServer config or permissions (mcp.no_tools)
Wrong sourceShadowed by TOML vs .mcp.json vs packageInspect report Source / package owner
Invalid transportBad typeUse stdio/http/sse (mcp.invalid_transport)

Plugin packages

Manifests

  • Native: semantix-plugin.json
  • Codex: .codex-plugin/plugin.json
  • Claude: .claude-plugin/plugin.json (+ limited Claude compatibility paths)

State: <Semantix home>/plugin-packages.json. Disabled packages do not contribute skills/hooks/MCP.

Unmapped Claude-only features may appear as compatibility warnings — Semantix does not invent support.

Checks

semantix-agent plugin doctor <name>, Settings → Plugins, Diagnostics → Plugins.

Symptom → cause → fix

SymptomCauseFix
Package missingBad root pathReinstall / fix root (plugin.missing_root)
Invalid manifestParse failureFix JSON/manifest (plugin.invalid_manifest)
Skills missingDisabled packageEnable package

Instructions (AGENTS.md / SEMANTIX.md)

Load order (ascending specificity)

User global docs → ancestor chain → project docs → project-local (*.local.md).

Recognized names: SEMANTIX.md, AGENTS.md, CLAUDE.md (and *.local.md variants). Multiple files in one directory can load; symlink identity is deduped.

Instructions fold into the system prompt at session boot (cache-stable prefix); Hooks remain runtime event handlers loaded from their configured locations.

Checks

Diagnostics → Instructions; memory Settings; read files on disk.

Symptom → cause → fix

SymptomCauseFix
Guidance ignoredWrong filename / empty fileUse recognized names under correct dir
Wrong scope wonLocal overrideCheck load order in report

Desktop Diagnostics page

  • Static report on open; Refresh re-runs static collect
  • Copy redacted JSON
  • Optional session runtime merge (read-only Host)
  • Jump to Settings for MCP / Skills / Plugins / Hooks when issue settings_tab is set
  • Never auto-edit config, execute hooks, or auto-reconnect from this page

Safety

  • Prefer static diagnostics
  • Live MCP may run third-party code and network
  • Do not print tokens, header values, env values, URL query strings, usernames, or machine-absolute external paths
  • Report paths as <workspace>/…, ~/…, or <external>/…

Frequently asked questions

What does the Semantix Guide AI skill do?

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.

Why use Semantix Guide on TypingMind?

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

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Gnosil/semantix/tree/main/harness/skill/builtincontent/semantix-guide. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Semantix Guide?

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 Semantix Guide?

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

Is the Semantix Guide AI skill free?

Yes. It is published on GitHub by Gnosil under the MIT license. 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

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇