Agent skill

Hermes Skill

Create, improve, inventory, and audit Claude Code skills. An agent skill from AlexAI-MCP/hermes-CCC.

MITAuto-check passed

Install Hermes Skill

skills CLI

$ npx skills add AlexAI-MCP/hermes-CCC --skill hermes-skill -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install AlexAI-MCP/hermes-CCC hermes-skill --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/AlexAI-MCP/hermes-CCC.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/hermes-skill .claude/skills/hermes-skill && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "hermes-skill" agent skill from https://github.com/AlexAI-MCP/hermes-CCC/tree/master/skills/hermes-skill into .claude/skills/hermes-skill/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hermes-skill", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/AlexAI-MCP/hermes-CCC/tree/master/skills/hermes-skill

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add AlexAI-MCP/hermes-CCC --skill hermes-skill -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install AlexAI-MCP/hermes-CCC hermes-skill --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/AlexAI-MCP/hermes-CCC.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/hermes-skill .agents/skills/hermes-skill && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "hermes-skill" agent skill from https://github.com/AlexAI-MCP/hermes-CCC/tree/master/skills/hermes-skill into .agents/skills/hermes-skill/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hermes-skill", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add AlexAI-MCP/hermes-CCC --skill hermes-skill -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install AlexAI-MCP/hermes-CCC hermes-skill --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/AlexAI-MCP/hermes-CCC.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/hermes-skill .cursor/skills/hermes-skill && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "hermes-skill" agent skill from https://github.com/AlexAI-MCP/hermes-CCC/tree/master/skills/hermes-skill into .cursor/skills/hermes-skill/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hermes-skill", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/AlexAI-MCP/hermes-CCC.git --path skills/hermes-skill

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add AlexAI-MCP/hermes-CCC --skill hermes-skill -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install AlexAI-MCP/hermes-CCC hermes-skill --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/AlexAI-MCP/hermes-CCC.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/hermes-skill .gemini/skills/hermes-skill && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "hermes-skill" agent skill from https://github.com/AlexAI-MCP/hermes-CCC/tree/master/skills/hermes-skill into .gemini/skills/hermes-skill/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hermes-skill", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install AlexAI-MCP/hermes-CCC hermes-skill

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add AlexAI-MCP/hermes-CCC --skill hermes-skill -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/AlexAI-MCP/hermes-CCC.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/hermes-skill .github/skills/hermes-skill && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "hermes-skill" agent skill from https://github.com/AlexAI-MCP/hermes-CCC/tree/master/skills/hermes-skill into .github/skills/hermes-skill/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hermes-skill", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add AlexAI-MCP/hermes-CCC --skill hermes-skill -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install AlexAI-MCP/hermes-CCC hermes-skill --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/AlexAI-MCP/hermes-CCC.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/hermes-skill .opencode/skills/hermes-skill && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "hermes-skill" agent skill from https://github.com/AlexAI-MCP/hermes-CCC/tree/master/skills/hermes-skill into .opencode/skills/hermes-skill/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hermes-skill", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: hermes-skill
GitHub stars: 135
Token cost: ~1.7k tokens
SKILL.md length: 823 words
Files: 1
Skills in repo: 44
Repo updated: Apr 8, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Create, improve, inventory, and audit Claude Code skills. An agent skill from AlexAI-MCP/hermes-CCC.

Works in 8 steps: Identify a repeated workflow that was… → Extract the reusable steps, not the chat… → List the exact tools, commands, and… → …
Turning a solved workflow into a reusable skill
SKILL.md covers Purpose, Required Skill Anatomy, Frontmatter Schema For This… and Description Rules, plus 19 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Hermes Skill is an agent skill from AlexAI-MCP/hermes-CCC. Create, improve, inventory, and audit Claude Code skills. Use when turning a solved workflow into a reusable skill, expanding an existing skill, checking trigger quality, or standardizing a skill pack.

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: Hermes Agent ported to Claude Code Channel — 46 native skills, no OAuth, no external process. The licence is MIT.

When your agent uses it

Turning a solved workflow into a reusable skill
Expanding an existing skill
Checking trigger quality
Standardizing a skill pack

Example prompts

“/hermes-skill”

Workflow steps

8 steps, taken from the first numbered list in SKILL.md.

Identify a repeated workflow that was just solved.
Extract the reusable steps, not the chat narrative.
List the exact tools, commands, and files involved.
Identify preconditions and failure modes.
Write the frontmatter with strong trigger language.
Write the body as an operator playbook.
Include output contracts where consistency matters.
Include examples only when they sharpen execution.

What it can do on your machine

Read from SKILL.md and the folder at commit 8107e89. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Hermes Skill loads about 1.7k tokens when it runs. Until then it costs about 54 tokens; SKILL.md has 823 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~54
When it runs · the whole SKILL.md, loaded when a task matches: ~1.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from AlexAI-MCP/hermes-CCC at commit 8107e89, republished under its MIT licence (© AlexAI-MCP). 823 words, ~1,688 tokens.

Download SKILL.mdSave it as .claude/skills/hermes-skill/SKILL.md (or your agent's skills folder).

name: hermes-skill
description: Create, improve, inventory, and audit Claude Code skills. Use when turning a solved workflow into a reusable skill, expanding an existing skill, checking trigger quality, or standardizing a skill pack.
version: 0.1.0
author: OpenAI Codex
license: MIT
metadata.category: skilling
metadata.ported_from: NousResearch Hermes Agent
metadata.tags: skills, reuse, authoring, maintenance
metadata.tools: filesystem, markdown, shell
metadata.maturity: beta

Hermes Skill

Purpose

Convert repeated workflows into reusable Claude Code skills.
Keep skills operational rather than descriptive.
Improve trigger quality so the right skill activates at the right time.
Audit skill packs for overlap, drift, and incomplete instructions.
Preserve working patterns after a successful task.

Required Skill Anatomy

one folder per skill
one SKILL.md file per folder
YAML frontmatter at the top
Markdown instructions below the frontmatter
commands, outputs, and failure handling in the body

Frontmatter Schema For This Package

name
description
version
author
license
metadata

Description Rules

State what the skill does.
State when to use it.
Mention trigger contexts directly.
Avoid vague phrasing such as "general helper".
Include important boundaries when the skill is domain-specific.

Naming Rules

use lowercase letters, digits, and hyphens only
keep names short and concrete
prefer operational nouns or verb-noun pairs
avoid project-specific private jargon unless the package is private
do not rename a stable public skill casually

Create Workflow

Identify a repeated workflow that was just solved.
Extract the reusable steps, not the chat narrative.
List the exact tools, commands, and files involved.
Identify preconditions and failure modes.
Write the frontmatter with strong trigger language.
Write the body as an operator playbook.
Include output contracts where consistency matters.
Include examples only when they sharpen execution.

Improve Workflow

Read the full skill.
Ask what failed or felt ambiguous in actual usage.
Tighten the description if triggering was weak.
Add missing commands or environment assumptions.
Add decision rules where the old version left too much ambiguity.
Add failure handling if the skill assumed a happy path.
Remove stale instructions and dead commands.

Audit Dimensions

trigger clarity
instruction quality
command accuracy
line-count sufficiency
duplication with nearby skills
presence of decision rules
presence of output contracts
presence of verification steps

What Makes A Good Skill

It reduces repeated thinking.
It includes exact actions for non-obvious steps.
It names the right tools and commands.
It narrows ambiguity without overfitting one repo.
It handles the common failure path.
It is faster to use than rediscovering the workflow.

What Makes A Bad Skill

It repeats generic advice the base model already knows.
It has weak frontmatter and never triggers.
It explains philosophy but omits execution.
It contains stale paths or commands.
It is so narrow that it only matches one past task.
It has no failure modes or verification guidance.

Skill Extraction Questions

What exact problem was solved?
What sequence of actions worked?
What tools or connectors were essential?
What surprised us during execution?
What constraints would another agent need to know up front?
What output structure made the result useful?

Standard Sections To Include

purpose
activation signals
inputs
preflight
step-by-step procedure
decision rules
output contract
failure modes
examples
checklist

Inventory Workflow

List all skill folders.
Verify that each folder contains SKILL.md.
Read frontmatter fields.
Produce a compact table of name, description, and health.
Flag missing or malformed skills.

Show full SKILL.md (324 more words)Show less

Overlap Rules

Two skills may overlap in domain but should differ in operating goal.
Merge skills if their triggers, commands, and outputs are nearly identical.
Keep separate skills if one is strategic and the other is procedural.
Prefer smaller focused skills over one giant omnibus skill.

Updating From Real Usage

Capture friction immediately after using a skill.
Update the skill while the failure mode is fresh.
Preserve examples that encode real mistakes.
Replace speculative guidance with validated instructions.

Example Improvement Targets

add missing prereq checks
tighten "when to use" language
replace obsolete CLI flags
add a markdown response template
split one overloaded skill into two

Audit Output Template

markdown

Skill audit report:
- systematic-debugging: Healthy - clear phases, explicit outputs, and verification loop
- old-review-skill: Outdated - stale GitHub CLI commands and no failure handling
- duplicate-debug-skill: Redundant - overlaps heavily with systematic-debugging

Creation Output Template

markdown

Created skill: my-new-skill
Path: ~/.claude/skills/my-new-skill/SKILL.md
Why it should trigger: handles repeated workflow for ...
Key sections: purpose, procedure, failure modes, output contract

Decision Rules

Create a new skill only when the workflow is truly repeatable.
Improve an existing skill when the use case matches its current mission.
Split a skill when one body now serves multiple unrelated triggers.
Keep package-wide conventions consistent across all skills.

Failure Modes

encoding one conversation instead of the general workflow
omitting commands because they felt obvious during the original task
bloating a skill with reference material that belongs elsewhere
letting frontmatter drift away from actual body content
failing to update package docs after adding or removing skills

Recovery Moves

If the skill reads like a postmortem, rewrite it as instructions.
If the skill is too abstract, add commands and examples.
If the skill is too long but still coherent, split by purpose not by arbitrary size.
If the trigger is too weak, rewrite the description before changing anything else.

Good Triggers

"turn this workflow into a skill"
"improve this skill"
"audit our skill pack"
"list installed skills"
"this keeps repeating, save it"

Checklist

Confirm the workflow is reusable.
Choose the right skill name.
Write strong frontmatter.
Add exact commands and decision rules.
Add failure handling and verification.
Check for overlap with existing skills.
Update package docs if necessary.
Validate structure before shipping.

Files

Just SKILL.md in skills/hermes-skill of AlexAI-MCP/hermes-CCC.

Open the folder on GitHubat commit 8107e89

Compare with similar skills

Hermes Skill next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Hermes Skill compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Hermes Skill this skillAlexAI-MCP/hermes-CCC	135	—	~1.7k	Automated safety check: Pass	MIT	6 mo ago
Hermes Importsaffaan-m/ECC	276k	—	~324	Automated safety check: Pass	MIT	yesterday
Hermes Importsaffaan-m/ECC	276k	1 repos	~752	Automated safety check: Pass	MIT	yesterday
Inspecting Hermes Desktop DomNousResearch/hermes-agent	252k	1 repos	~1.6k	Automated safety check: Pass	MIT	yesterday
Hermes Tweetwshobson/agents	40k	—	~1.4k	Automated safety check: Pass	MIT	6 days ago
Hermes Agent Skill AuthoringNousResearch/hermes-agent	252k	—	~3.6k	Automated safety check: Pass	MIT	yesterday

Similar skills

Hermes Imports
affaan-m/ECC
将本地 Hermes 操作员工作流转换为经过清理的 ECC 技能和发布包工件。在准备将 Hermes 工作流用于公共 ECC 重用而不泄露私有工作区状态、凭据或仅本地路径时使用。
276k GitHub stars~324 tokensUpdated yesterday
Auto-check passed
Hermes Imports
affaan-m/ECC
Convert local Hermes operator workflows into sanitized ECC skills and release-pack artifacts.
276k GitHub starsUsed in 1 repo~752 tokens
Auto-check passed
Inspecting Hermes Desktop Dom
NousResearch/hermes-agent
Read the live Hermes desktop DOM/CSS over CDP. An agent skill from NousResearch/hermes-agent.
252k GitHub starsUsed in 1 repo~1.6k tokens
Frontend & DesignAuto-check passed
Hermes Tweet
wshobson/agents
Install and operate Hermes Tweet, a Hermes Agent plugin for X/Twitter research, timeline reading, tweet analysis, and approval-gated private or state-changing operations.
40k GitHub stars~1.4k tokensUpdated 6 days ago
Writing & ContentAuto-check passed
Hermes Agent Skill Authoring
NousResearch/hermes-agent
Author in-repo SKILL.md files: frontmatter and structure. An agent skill from NousResearch/hermes-agent.
252k GitHub stars~3.6k tokensUpdated yesterday
Agent WorkflowsAuto-check passed
Asset Inventory
sickn33/agentic-awesome-skills
Maintain IT asset inventory and configuration management database.
47k GitHub starsUsed in 2 repos~3.4k tokens
Auto-check passed

Questions about Hermes Skill

What does Hermes Skill do?

Create, improve, inventory, and audit Claude Code skills. An agent skill from AlexAI-MCP/hermes-CCC. Hermes Skill is an agent skill from AlexAI-MCP/hermes-CCC. Create, improve, inventory, and audit Claude Code skills.

When should I use Hermes Skill?

Hermes Skill fits situations like: turning a solved workflow into a reusable skill; expanding an existing skill; checking trigger quality; standardizing a skill pack.

How do I install Hermes Skill in Claude Code?

Run `npx skills add AlexAI-MCP/hermes-CCC --skill hermes-skill -a claude-code`. Or copy the skill folder (skills/hermes-skill in AlexAI-MCP/hermes-CCC) into .claude/skills/hermes-skill in your project. Claude Code loads it when a task matches its description.

How do I install Hermes Skill in Codex?

Run `npx skills add AlexAI-MCP/hermes-CCC --skill hermes-skill -a codex`. Or copy the skill folder (skills/hermes-skill in AlexAI-MCP/hermes-CCC) into .agents/skills/hermes-skill in your project. Codex loads it when a task matches its description.

Can I use Hermes Skill in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add AlexAI-MCP/hermes-CCC --skill hermes-skill -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/hermes-skill, .gemini/skills/hermes-skill, .github/skills/hermes-skill and .opencode/skills/hermes-skill in your project.

What does Hermes Skill need to run?

SKILL.md names no scripts, command-line tools or credentials: Hermes Skill is instructions for the agent only.

Does Hermes Skill access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Hermes Skill safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Hermes Skill use?

Hermes Skill is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Hermes Skill use?

About 1.7k tokens (SKILL.md is roughly 6.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Hermes Skill?

Skills that share tags, products or a category with Hermes Skill: Hermes Imports (affaan-m/ECC, 276k stars), Hermes Imports (affaan-m/ECC, 276k stars), Inspecting Hermes Desktop Dom (NousResearch/hermes-agent, 252k stars) and Hermes Tweet (wshobson/agents, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Hermes Skill?

AlexAI-MCP (a GitHub user) maintains it in AlexAI-MCP/hermes-CCC, which has 135 GitHub stars. The repository holds 44 skills in this directory. The repository was last updated on April 8, 2026.

Source: AlexAI-MCP/hermes-CCC on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Hermes Skill

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Hermes Skill

Purpose

Required Skill Anatomy

Frontmatter Schema For This Package

Description Rules

Naming Rules

Create Workflow

Improve Workflow

Audit Dimensions

What Makes A Good Skill

What Makes A Bad Skill

Skill Extraction Questions

Standard Sections To Include

Inventory Workflow

Overlap Rules

Updating From Real Usage

Example Improvement Targets

Audit Output Template

Creation Output Template

Decision Rules

Failure Modes

Recovery Moves

Good Triggers

Checklist

Files

Compare with similar skills

Similar skills

More from AlexAI-MCP/hermes-CCC

Questions about Hermes Skill