Why use Skills
- Specialize the agent – Add domain-specific instructions and workflows (e.g. financial ratios, report templates).
- Reduce repetition – Define once in a skill; the agent picks it up automatically when the task matches.
- Compose capabilities – Combine multiple skills and tools for complex workflows.
Using Skills
Pass a list of skill names to the agent. Skills are resolved from the filesystem (./skills). You can also restrict which skills are active for a given run with RunOptions(enabled_skills=...).
Agent configuration
Run Agent with skills
UseRunOptions(enabled_skills=[...]) to enable only certain skills for a single run (e.g. when streaming):
tools; the skill’s instructions tell the agent how to use that data.
Skill structure
Every skill must have aSKILL.md file with YAML frontmatter and a body. Optional files include tools.py, REFERENCE.md, and EXAMPLES.md.
Required: SKILL.md
name– Required. Lowercase letters, numbers, and hyphens only; max 64 characters. Used as the skill identifier (e.g. inskills=["your-skill-name"]).description– Required. Short summary of the skill’s purpose and when it should be used; max 1024 characters.
version and tags.
Optional files
| File | Purpose |
|---|---|
tools.py | Defines tool/toolkit objects the skill can use. |
REFERENCE.md | Reference material (APIs, schemas). |
EXAMPLES.md | Extra examples. |
Security considerations
Skills give the agent instructions and can bundle code (e.g. intools.py) and reference data. Only use skills from sources you trust (your own or vetted internal ones).
Next steps
- Add a skill under
~/.hypertic/skillsor./skillswith a validSKILL.md, then reference it inAgent(skills=[...]). - Use
RunOptions(enabled_skills=[...])when you want only specific skills active for a run (e.g. streaming).