Agent skills for working with Hex. Each skill lives in skills/ and can be
installed individually via Claude Code, Cursor, Codex, or other agents that support the Agent Skills
standard.
| Skill | Description |
|---|---|
| hex-context-best-practices | Build and roll out a context strategy for Hex's AI agents (Threads, Notebook Agent, Modeling Agent). Drafts context assets, plans phased rollouts, and diagnoses wrong answers. |
Install one skill at a time from the shared marketplace:
/plugin marketplace add hex-inc/hex-skills
/plugin install hex-context-best-practices@hex-skills
See each skill's README for usage examples.
npx skills add hex-inc/hex-skills
Works with Claude Code, Codex, Cursor, Gemini CLI, and others that support the Agent Skills spec.
Clone the repo; AGENTS.md routes Codex to the right skill:
git clone https://github.com/hex-inc/hex-skills
git clone https://github.com/hex-inc/hex-skills
cp -r hex-skills/skills/<skill-name> ~/.claude/skills/
hex-skills/
├── .claude-plugin/
│ └── marketplace.json # Claude Code marketplace — lists all skills
├── AGENTS.md # Codex / generic-agent router
├── skills/
│ └── <skill-name>/
│ ├── SKILL.md # orchestrator — start here
│ ├── README.md # install + usage for this skill
│ ├── .claude-plugin/
│ │ └── plugin.json # per-skill plugin manifest
│ ├── agents/ # optional specialist agents
│ ├── references/ # optional supporting material
│ └── hex-guides/ # optional Hex product install artifacts
└── README.md
Use skills/hex-context-best-practices/ as the reference
implementation. Each skill is a self-contained folder under skills/.
skills/<skill-name>/
├── SKILL.md # required — orchestrator with YAML frontmatter (name, description)
├── README.md # install + usage for this skill
├── .claude-plugin/
│ └── plugin.json # per-skill plugin manifest for Claude Code
├── agents/ # optional — specialist agent prompts
├── references/ # optional — supporting docs the skill reads on demand
└── hex-guides/ # optional — content to paste into Hex Context Studio
SKILL.md is the entry point agents read first. Keep it focused; put detailed material in
references/ or agents/ and link to those files from SKILL.md.
README.md should cover what the skill does, what's inside, and how to install/use it for
this skill specifically (see the context-best-practices README for an example).
Update these three files so agents and install tools can discover the new skill:
- This README — add a row to the Skills table above.
AGENTS.md— add a row mapping the task/trigger toskills/<skill-name>/SKILL.md..claude-plugin/marketplace.json— add a plugin entry:
{
"name": "<skill-name>",
"source": "./skills/<skill-name>",
"description": "One-line description for the marketplace.",
"version": "1.0.0"
}Create skills/<skill-name>/.claude-plugin/plugin.json. Copy from
skills/hex-context-best-practices/.claude-plugin/plugin.json
and update name, description, and keywords. Keep repository pointing at this repo.
- Use kebab-case for folder and skill names (e.g.
hex-notebook-patterns). - Keep each skill independently installable — users should be able to run
/plugin install <skill-name>@hex-skillswithout pulling in unrelated skills. - If the skill includes Hex product artifacts (guides, context snippets), put them in
hex-guides/inside that skill's folder, not at the repo root.
MIT