Turning Repeated Work into Hermes Skills

Skills are procedural memory. They help Hermes repeat proven workflows without rediscovering every step in a future session.

When a workflow should become a skill

Create or update a skill when:

• The task took several tool calls and will happen again
• A tricky error was solved
• The user corrected the process
• A workflow has exact commands or paths
• A safety rule must be remembered
• The task has a reliable verification pattern

Good skill structure

A useful skill includes:

• Trigger conditions: when to load it
• Prerequisites: tools, commands, paths, accounts
• Numbered procedure
• Pitfalls and known failures
• Verification steps
• Links to reference files or scripts when needed

Bad skill structure

Avoid vague notes such as “be careful with deployment.” Instead, write the actual check:

After deployment, fetch the public URL and confirm HTTP 200 plus expected page text.

Maintenance

Skills should be patched when they become outdated. A stale skill is worse than no skill because it creates false confidence.

Rocky usage

For HeyRocky workflows, skills are best for recurring site publishing, media production, gateway debugging, security checks, and client-specific operating procedures.