agentleFS
Sign inStart free
anomalycoanomalyco/hex/skills/hex-personal-commands/SKILL.md

hex-personal-commands

Skill5.8k starsChanged 14 days agoMITView on GitHub

Configure Hex personal deterministic transcript transformations in `~/.config/hex/hex.config.ts`. Use when the user wants to add or change custom text transformations for the Hex voice app.

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Who's talking about anomalyco/hex

The biggest 5 of 78 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 78

Talked about on GitHub, YouTube and Bluesky (78 times).

On GitHub · 50

45 more on GitHub

On YouTube · 24

19 more on YouTube
  • In this repositoryOne other file it gives its agents.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 0 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Check for ~/.config/hex/hex.config.ts (or hex.config.js).

    line 16
  2. Very specific:

    Read ~/.config/hex/AGENTS.md for the current API and limits, and hex.d.ts for exact types.

    line 19
  3. Very specific:

    Use defineHexConfig from @hex/commands and declare pure transformations entries ({ id, name, description?, transform(text, context) }).

    line 27
  4. Very specific:

    Run hex commands check (macOS) after editing.

    line 31
  5. Very specific:

    If hex reports commands check as an unrecognized subcommand, stop: the user is on an older Hex (such as 2.3.1).

    line 36

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Hex Personal Transformations

This skill targets current Hex (dev builds now, and the next stable release). Hex 2.3.1 uses an older runtime; its matching skill installs with npx skills add anomalyco/hex#app-v2.3.1 --skill hex-personal-commands.

Hex runs ~/.config/hex/hex.config.ts itself, in an embedded JavaScript engine. There is no package to install and no build step.

  1. Check for ~/.config/hex/hex.config.ts (or hex.config.js). If it is missing, ask the user to open Hex's Modes pane and choose Create Config, or run hex commands init if the hex CLI is available.
  2. Read ~/.config/hex/AGENTS.md for the current API and limits, and hex.d.ts for exact types. Hex owns both and rewrites them; do not edit them.
  3. Edit only the config and files it imports. Scripts are plain TypeScript or JavaScript: they can import @hex/commands and files in the folder, not npm packages, Effect, or Node APIs, and they have no filesystem, network, or timer access. Enums, namespaces, and constructor parameter properties are rejected.
  4. Use defineHexConfig from @hex/commands and declare pure transformations entries ({ id, name, description?, transform(text, context) }).
  5. Transformations must be selected in the mode's Transformations section. They run after mode corrections and optional AI rewriting, not for meetings.
  6. Run hex commands check (macOS) after editing. It loads the config as Hex does and prints what it registers or the error with file, line, and column. Optionally type-check with npx -y -p typescript tsc in ~/.config/hex. A running Hex reloads the config on save and shows load errors in Modes' Transformations section. If hex reports commands check as an unrecognized subcommand, stop: the user is on an older Hex (such as 2.3.1). Tell them to install the matching skill with npx skills add anomalyco/hex#app-v2.3.1 --skill hex-personal-commands, or to switch to the dev build (https://github.com/anomalyco/hex#downloads).

Completion criterion: the requested behavior is represented in the config, hex commands check succeeds (or, without the CLI, the reload succeeded in Hex), and any verification gap is reported.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free