skill

Route user slash commands to predefined hex skills with auditable execution.

4|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/gaberger/hex --skill skill-gaberger
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill
Source: https://github.com/gaberger/hex/tree/main/hex-cli/assets/context-templates/tools
Command: npx skills add https://github.com/gaberger/hex --skill skill-gaberger

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables and standardizes the invocation of predefined hex skills when users reference slash commands, ensuring only authorized skills are executed and preventing misuse of built-in CLI commands.

Core Features & Use Cases

  • Skill dispatch: route user requests to the correct predefined hex skill from the user message.
  • Safety guarantees: restricts execution to skills listed in user-invocable skills and bypasses non-listed commands.
  • Auditable execution: relies on frontmatter-defined skill names and documented behavior for traceability.

Quick Start

Ask the agent to invoke a specific hex skill by its slash command, for example /hex-scaffold to scaffold a new project.

Frequently Asked Questions about skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I safely invoke hex skills using slash commands?

To safely dispatch hex skills, this tool routes user requests to the correct predefined skill from the message, enforcing frontmatter-defined names to restrict execution to authorized user-invocable skills only.

What is the best way to prevent unauthorized CLI command execution during skill dispatch?

Preventing unauthorized CLI command execution during skill dispatch requires restricting invocations to predefined hex skills listed in user-invocable skills, bypassing non-listed commands to guarantee safe operation.

Can I use arbitrary CLI commands with hex skill validation?

Hex skill validation does not support arbitrary CLI commands. It scopes execution to only skills listed in user-invocable skills, preventing misuse of built-in CLI commands.

How does frontmatter-defined skill naming ensure auditable execution?

Frontmatter-defined skill naming ensures auditable execution by relying on documented behavior and predefined names for traceability, standardizing the invocation of predefined hex skills.

When do I need to standardize hex skill invocation via slash commands?

You need to standardize hex skill invocation via slash commands when users reference predefined skills, ensuring only authorized skills are executed and preventing misuse of built-in CLI commands.