Skill Creator
Guide for creating and updating effective Omnibot skills.
Install
npx skills add omnimind-ai/OmniBot --skill skill-creator -g -a claude-code -y- Repository
- omnimind-ai/OmniBot2.1k
- Category
- Engineering
- Updated
- 3d ago
- License
- See repository
- Context cost
- Lightabout 1,116 tokens
- Runs scripts
- No, instructions only
What it does
Guide for creating and updating effective Omnibot skills. Use when the user wants to add a new skill or improve an existing skill for the built-in {{OMNIBOT_TERMINAL_DISTRIBUTION}} workspace, tool workflows, or reusable domain knowledge.
Skill Creator
Use this skill when the task is to create, refine, or maintain an Omnibot skill.
Omnibot skills live inside the workspace at .omnibot/skills/<skill-id>/ and are discovered by the agent through the SKILL.md frontmatter plus any bundled scripts/, references/, or assets/.
Core Rules
- Keep the frontmatter precise.
- Keep the body short and procedural.
- Put detailed reference material into
references/instead of bloatingSKILL.md. - Prefer reusable scripts or templates when the same steps will be repeated.
- Design for Omnibot's real runtime: the selected {{OMNIBOT_TERMINAL_DISTRIBUTION}} shell, workspace files, built-in tools, and optional Shizuku-backed Android actions.
Skill Shape
Every skill needs a SKILL.md file.
Recommended layout:
skill-id/
├── SKILL.md
├── scripts/
├── references/
└── assets/
Use only the folders that are actually needed.
Frontmatter
Use YAML frontmatter with only these fields:
---
name: my-skill
description: What the skill does and when Omnibot should use it.
---
Write the description as the trigger contract:
- State the task type clearly.
- State the signals that should trigger the skill.
- Mention important environments or tools when they matter.
Bad description:
Helpful utility for many tasks.
Good description:
Create or update deployment runbooks for Omnibot workspaces. Use when the user asks to document {{OMNIBOT_TERMINAL_DISTRIBUTION}} setup, workspace paths, scheduled runs, or recovery steps for on-device agents.
Body Guidance
Write the body as instructions for another Omnibot agent.
Prefer:
- imperative steps
- short heuristics
- references to concrete files or directories
- explicit failure handling
Avoid:
- long product overviews
- repeated basics the model already knows
- user-facing marketing text
- duplicate content that belongs in
references/
Resource Choices
Use scripts/ when:
