Quick Start
How It Works
| Phase | Process | Output |
|---|---|---|
| Discovery | Scan directories for SKILL.md files | Found skills list |
| Validation | Check format, dependencies, security | Validation report |
| Integration | Load into PraisonAI discovery roots | Active skills |
Migration Dimensions
Artifact Inventory
Hermes/OpenClaw skills typically follow this structure:Configuration Options
| Option | Type | Default | Description |
|---|---|---|---|
skill_dirs | List[str] | None | Directories to scan for skills |
include_defaults | bool | True | Include built-in skill directories |
validate_scripts | bool | True | Validate script security before execution |
namespace_conflicts | bool | False | Auto-namespace conflicting skill names |
Step-by-Step Migration
Runtime Bridges
Skills coexist with tools through layered integration:- Skills provide instructions and safety policy text
- Tools provide mechanisms (API keys, quotas, auditing)
- MCP bridges host capabilities and external services
Tool Integration Pattern
Best Practices
Namespace Management
Namespace Management
Use consistent naming to avoid conflicts:
Security Isolation
Security Isolation
Review and sanitize script execution:
Version Management
Version Management
Track skill versions and compatibility:
Testing Integration
Testing Integration
Test skills in isolation before deployment:
Troubleshooting
Common Issues
| Problem | Symptoms | Solution |
|---|---|---|
| Skill not detected | Empty discovery results | Check path, YAML format, UTF-8 encoding |
| Import errors | Module not found | Verify script dependencies, update requirements |
| Permission denied | Script execution fails | Review file permissions, security settings |
| Name conflicts | Skill override warnings | Use namespacing or rename conflicting skills |
Validation Checklist
- SKILL.md exists and has valid YAML frontmatter
- Required fields:
name,description - UTF-8 encoding throughout
- No hardcoded secrets in files
- Scripts have proper dependencies
- File permissions allow execution
Debug Commands
Capability Requirements
Hermes/OpenClaw skills can now declare capability requirements that are first-class parsed intoSkillRequirements and enforced via PraisonAI’s capability gates system.
Supported Frontmatter Keys
All these frontmatter keys from Hermes/OpenClaw skills are now parsed and enforced:| Hermes/OpenClaw Key | PraisonAI Field | Validation Result |
|---|---|---|
requires_tools | SkillRequirements.tools | Missing tools → DEGRADED/UNAVAILABLE |
requires_servers | SkillRequirements.servers | Missing servers → DEGRADED/UNAVAILABLE |
requires_env | SkillRequirements.env_vars | Missing env vars → DEGRADED |
openclaw | SkillRequirements.openclaw_hints | Passthrough metadata |
Updated Linting
Update your frontmatter linting to accept these new capability requirement keys:Related
Skills Overview
Learn about PraisonAI’s skill system architecture
Tool Integration
Understand tools vs skills differences

