- Introduced new skills tools: `skills_categories`, `skills_list`, and `skill_view` in `model_tools.py`, allowing for better organization and access to skill-related functionalities. - Updated `toolsets.py` to include a new `skills` toolset, providing a dedicated space for skill tools. - Enhanced `batch_runner.py` to recognize and validate skills tools during batch processing. - Added comprehensive tool definitions for skills tools, ensuring compatibility with OpenAI's expected format. - Created new shell script `test_skills_kimi.sh` for testing skills tool functionality with Kimi K2.5. - Added example skill files demonstrating the structure and usage of skills within the Hermes-Agent framework, including `SKILL.md` for example and audiocraft skills. - Improved documentation for skills tools and their integration into the existing tool framework, ensuring clarity for future development and usage.
1.7 KiB
1.7 KiB
name, description
| name | description |
|---|---|
| example-skill | An example skill demonstrating the skill file format and structure |
Example Skill
This is an example skill file that demonstrates how to create skills for the Hermes Agent.
Skill File Format
Skills are markdown files with YAML frontmatter at the top:
---
name: your-skill-name
description: A brief one-line description of what this skill does
---
The frontmatter fields:
- name: The identifier used to reference this skill (lowercase, hyphens for spaces)
- description: A brief description shown when listing skills (keep under 200 chars)
Writing Effective Skills
1. Be Specific and Actionable
Good skills provide clear, actionable instructions:
When reviewing code:
1. Check for security vulnerabilities first
2. Verify error handling is comprehensive
3. Ensure tests cover edge cases
2. Include Examples
Show concrete examples of what you want:
# Good: Descriptive variable names
user_authentication_token = get_token()
# Bad: Cryptic abbreviations
uat = gt()
3. Define When to Use
Help the agent understand when this skill applies:
Use this skill when: reviewing pull requests, auditing security, or checking code quality.
Skill Categories
Consider organizing skills by purpose:
- Conventions: Coding standards, API patterns, naming rules
- Workflows: Step-by-step processes for deployments, reviews, releases
- Knowledge: Domain-specific information, system architecture, gotchas
- Templates: Boilerplate for common tasks, response formats
Tips
- Keep the description concise - it's shown in the skills list
- Use headers to organize longer skills
- Include code examples where helpful
- Reference other skills if they're related