hermes-agent-skill-authoring

Author in-repo SKILL.md files with compliant frontmatter and structure.

Updated Sep 20, 2026
One-click install
npx skills add https://github.com/GreenyZA/neo-light --skill hermes-agent-skill-authoring-greenyza
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hermes-agent-skill-authoring
Source: https://github.com/GreenyZA/neo-light/tree/main/.hermes-home/skills/software-development/hermes-agent-skill-authoring
Command: npx skills add https://github.com/GreenyZA/neo-light --skill hermes-agent-skill-authoring-greenyza

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Contributing a reusable skill to the hermes-agent repository requires meeting strict authoring standards that reviewers enforce, and this Skill walks you through every rule so your PR passes review on the first attempt. ## Core Features & Use Cases - Frontmatter Compliance: Enforces the repo hardline rules for name, description (60 characters max), author attribution, platforms, and related_skills fields. - Tier and Category Guidance: Helps you decide between bundled skills/ and optional-skills/ placement and pick the correct category. - Tests and Docs Workflow: Covers required pytest files, docs regeneration with scope discipline, and the verification checklist before committing. - Use Case: When asked to add a new skill to a hermes-agent branch, follow this Skill to draft the SKILL.md, validate it locally, add tests, regenerate docs, and open a clean PR. ## Quick Start Ask the agent to create a new in-repo skill for your workflow following the hermes-agent authoring standards.

Frequently Asked Questions about hermes-agent-skill-authoring

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a SKILL.md file in the hermes-agent repo?▼

Write the file with write_file to skills/<category>/<name>/SKILL.md or optional-skills/<category>/<name>/SKILL.md, then git add and commit. Do not use skill_manage(action='create'), which only targets the user-local ~/.hermes/skills/ tree.

What frontmatter fields are required in a SKILL.md?▼

The validator requires name and description, but repo standards also expect version, author, license, platforms, and metadata.hermes with tags and related_skills. The description must be 60 characters or fewer, one sentence, and end with a period.

Should a new skill go in skills/ or optional-skills/?▼

Bundled skills/ is for daily-driver behavior useful across many user types with a 5+ sessions per month bar. Niche, vertical-specific, or heavy skills belong in optional-skills/. When in doubt, choose optional since promoting later is easier than demoting.

Why does my new skill not appear in the current session?▼

The skill loader is initialized at session start and cached, so skill_view and skills_list will not see a newly added skill until a new session begins. This is expected behavior, not a bug.

What tests and docs are required for repo skills?▼

Add a pytest file at tests/skills/test_<skill>_skill.py using stdlib and unittest.mock only, then run the docs generator and revert unrelated drift. The final diff should show only your SKILL.md, one docs page, a catalog row, and one sidebar entry.