mirror of https://github.com/NousResearch/hermes-agent.git synced 2026-04-28 23:11:37 +08:00

Files

Teknium e3921e7ca4 docs(skills): compress 74 built-in skill descriptions to <=60 chars

Target: every skill's description fits in a one-line gateway menu and
leads with trigger keywords an agent would match on. Drops filler like
'Use this skill to', 'A skill for', 'This skill provides'.

Before: max description length was 791 chars (architecture-diagram),
74 of 81 built-in skills were >60 chars.

After: max 60, mean 54, all 81 built-in skills <=60.

Rewritten with double-quoted YAML scalars to preserve Chinese/arrow
glyphs (baoyu-comic, yuanbao, youtube-content).

2026-04-26 21:50:56 -07:00

1.9 KiB

Raw Blame History

name, description, version, author, license, metadata

name

description

version

author

license

metadata

plan

Plan mode: write markdown plan to .hermes/plans/, no exec.

1.0.0

Hermes Agent

MIT

hermes

Plan Mode

Use this skill when the user wants a plan instead of execution.

Core behavior

For this turn, you are planning only.

Do not implement code.
Do not edit project files except the plan markdown file.
Do not run mutating terminal commands, commit, push, or perform external actions.
You may inspect the repo or other context with read-only commands/tools when needed.
Your deliverable is a markdown plan saved inside the active workspace under .hermes/plans/.

Output requirements

Write a markdown plan that is concrete and actionable.

Include, when relevant:

Goal
Current context / assumptions
Proposed approach
Step-by-step plan
Files likely to change
Tests / validation
Risks, tradeoffs, and open questions

If the task is code-related, include exact file paths, likely test targets, and verification steps.

Save location

Save the plan with write_file under:

.hermes/plans/YYYY-MM-DD_HHMMSS-<slug>.md

Treat that as relative to the active working directory / backend workspace. Hermes file tools are backend-aware, so using this relative path keeps the plan with the workspace on local, docker, ssh, modal, and daytona backends.

If the runtime provides a specific target path, use that exact path. If not, create a sensible timestamped filename yourself under .hermes/plans/.

Interaction style

If the request is clear enough, write the plan directly.
If no explicit instruction accompanies /plan, infer the task from the current conversation context.
If it is genuinely underspecified, ask a brief clarifying question instead of guessing.
After saving the plan, reply briefly with what you planned and the saved path.

1.9 KiB Raw Blame History