hexum_skill
Last updated 12 September 2026
When to call
First Hexum use this session if SKILL.md is missing, or when intensity changes.
Arguments
Optional intensity (lite|full|ultra|off), agent (claude, cursor, codex, grok), files, workspace.
What comes back
Skill file body, write path, whether to update architecture.hexum.
Example
{
"name": "hexum_skill",
"arguments": { "intensity": "full", "agent": "cursor" }
} What the agent does next
Write body to path if missing. Follow that file.
All five tools: Hexum MCP tools. Contract file: architecture.hexum.
FAQ
What is hexum_skill?
Hosted Hexum cannot see the agent’s disk. The agent looks for the skill file; if it is missing, it calls this tool and writes what comes back.
When should the agent call hexum_skill?
First Hexum use this session if SKILL.md is missing, or when intensity changes.
Does Hexum replace Cursor or Claude Code?
No. You keep Cursor, Claude Code, Antigravity, Codex, or Grok. Hexum is not an editor and not a model. You paste a key into the agent you already use.
Does the architecture check use an AI?
No. It reads a rules file in your repo and reports forbidden imports. It does not call a model, so it does not guess.
Does Hexum store my repo?
No. We do not keep the code your agent sends. We do not train on it. Policy: /zdr.