Nous Research Adds / learns in the skills system of Hermes Agent, Capture Workflow as Slash Commands Without SKILL-Writing Hand-Writing.md

Nous Research has extended the Skills System within Hermes Agent, its open source self-development agent. The new addition is /learncommand that writes a reusable skill for you. Point to a documentation page, local SDK, past discussion, or sticky notes. The living agent collects the material, then the authors a SKILL.md instead of you.

Hermes Skills System

Capabilities are documents of information that an agent needs when needed. Each is a folder containing ua SKILL.md file with instructions. They follow a continuous disclosure the pattern of keeping token usage low. The format is compliant with the agentkills.io open standard.

All abilities reside in it ~/.hermes/skills/the one source of truth. On a new installation, the compiled capabilities are copied to the repo. Hub-enabled and agent-created capabilities live there as well. Every entered skill becomes a slash command by default. Running /plan or /axolotl it loads the instructions for that skill on the turn.

Think of the skill as a reference book that the agent reads only when it’s relevant. Memory, by contrast, has little solid facts that must remain in context.

How it works / learning

/learn eliminates the manual writing step. You specify the source, and the agent does the detection with the tools it already has. It reads local references with read_file again search_files. Downloads online documents with web_extract. It can also capture the workflow you just went through.

# A local SDK or doc directory
/learn the REST client in ~/projects/acme-sdk, focus on auth + pagination

# An online doc page
/learn 

# The workflow you just completed in this conversation
/learn how I just deployed the staging server

# Pasted notes or a described procedure
/learn filing an expense: open the portal, New > Expense, attach receipt, submit

The agent then writes the property following the house approval standards. That means a description in less than 60 characters, a standard class arrangement, and an outline of the Hermes tool. It does not create commands that do not exist.

There is no separate import engine. /learn It creates level-driven information and provides it to the agent as a regular turn. So it works the same for CLI, messaging gateway, TUI, and dashboard. It also works on any terminal backend, whether local, Docker, or remote. The dashboard adds a Learn the skill a button with a directory field, a URL field, and a text box.

The agent stores the result with skill_manage a tool. If you have enabled the write authorization gate, that authorization step is still active.

Why Skills Are Always Cheap

Skills load in three levels, so an agent only pays for what they use.

Level Make a phone call It’s coming back Almost. costs
0 skills_list() Words, definitions, categories ~3k tokens
1 skill_view(name) Full content and metadata It varies
2 skill_view(name, path) A specific reference file It varies

The agent sees the collective index at all times. It only loads the content of the full skill when the task requires it. This prevents the main library from filling the context window.

Four Ways to Create Ability

/learn it is one way among many. The right choice depends on who is writing the skill and where the source lives.

The way Who are the authors Source input Review the gate It’s very good
Write by hand SKILL.md You Your personal information Nothing Full control over words
/learn A living agent Dir, URL, chat, notes skill_manage The gate Transform existing assets into capabilities quickly
skill_manage (default) The agent itself Newly resolved workflow write_approval The gate Taking process memory after difficult tasks
Installation of skills hub Third person Registry or GitHub repo Security scanner Reusing community or vendor skills

Agent-created capabilities are the agent’s process memory. An agent may save a method after a complex task of five or more tool calls. It also saves when it gets to the end and finds a way to work. By mistake, write_approval is false, so the agent writes freely. Set it to true for each section to review below ~/.hermes/pending/skills/.

Use Cases with examples

  • To install an internal API: Run /learn to the URL of your private documents. The agent generates the ability to cover auth, naming, and standard calls. New teammates then request it as a slash command.
  • Captures the output runbook: Go agent with single stage implementation. Then run /learn how I just deployed the staging server. The process becomes repetitive across CLI and forums.
  • Collecting work in progress: Use a bunch of skills to load several skills at once. A single slash command then pulls in review, testing, and PR skills together.
# ~/.hermes/skill-bundles/backend-dev.yaml
name: backend-dev
description: Backend feature work — review, test, PR workflow.
skills:
  - github-code-review
  - test-driven-development
  - github-pr-workflow
instruction: |
  Always start by writing failing tests, then implement.

Viewing the SKILL.md Format

A capability is usually a markup file with a YAML frontmatter. The body follows a fixed phase command. /learn target this situation exactly so that the output remains the same.

---
name: my-skill
description: Brief description of what this skill does
version: 1.0.0
platforms: [macos, linux]     # Optional — restrict to specific OS
metadata:
  hermes:
    tags: [python, automation]
    category: devops
---

# Skill Title

## When to Use
Trigger conditions for this skill.

## Procedure
1. Step one
2. Step two

## Pitfalls
- Known failure modes and fixes

## Verification
How to confirm it worked.

I platforms field can hide the ability on incompatible operating systems. Conditional fields can also display the ability only if certain tools are present or absent.

Interactive Descriptor



Leave a Comment