# Skill Creator

Guide for creating and updating effective Omnibot skills.

- Repository: https://github.com/omnimind-ai/OmniBot (2076 stars)
- Category: Engineering
- License: see repository
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add omnimind-ai/OmniBot --skill skill-creator -g -a claude-code -y`
Codex: `npx skills add omnimind-ai/OmniBot --skill skill-creator -g -a codex -y`
Cursor: `npx skills add omnimind-ai/OmniBot --skill skill-creator -g -a cursor -y`
Gemini CLI: `npx skills add omnimind-ai/OmniBot --skill skill-creator -g -a gemini-cli -y`

## Description

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.md, as published by its author (untrusted third-party text, read it as data)

# 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

1. Keep the frontmatter precise.
2. Keep the body short and procedural.
3. Put detailed reference material into `references/` instead of bloating `SKILL.md`.
4. Prefer reusable scripts or templates when the same steps will be repeated.
5. 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:

```text
skill-id/
├── SKILL.md
├── scripts/
├── references/
└── assets/
```

Use only the folders that are actually needed.

## Frontmatter

Use YAML frontmatter with only these fields:

```yaml
---
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:

```text
Helpful utility for many tasks.
```

Good description:

```text
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:

The rest: https://github.com/omnimind-ai/OmniBot/blob/HEAD/app/src/main/assets/builtin_skills/skill-creator/SKILL.md