<< All versions

Skill v1.0.0

currentAutomated scan100/100
devos-ing/omni-skills/creating-bundle-skills
──Details
PublishedNovember 4, 2026 at 05:29 AM
Content Hashsha256:bc94917012763dc5...
Git SHA55dedfa4d9dd
──Files
Files (1 file, 1.5 KB)
SKILL.md1.5 KBactive
SKILL.md · 56 lines · 1.5 KB

name: creating-bundle-skills description: Use when creating or editing an Omniskills workflow bundle with one callable entry skill. metadata: version: "1.0.0"


Creating Bundle Skills

Create the smallest repeatable workflow that solves one job.

  1. Create workflow.json, README.md, and

skills/<workflow-name>/SKILL.md.

  1. Declare the callable entry skill and every companion skill in skills[].
  2. Add only the ordered phases users must understand to steps[].
  3. Make every steps[].skill exactly match a declared skills[].source.
  4. Keep human gates explicit.
  5. Run omniskill lock, validate, and deps.

A simple entry skill looks like this:

markdown
---
name: workflow-name
description: Use when running the workflow-name Omniskills workflow.
---
# workflow-name
1.Use mattpocock:grilling to clarify one question at a time.
2.Run ./skills/custom-review and wait for approval.
3.Use mattpocock:to-tickets to create vertical tickets.

Declare the same sources in the manifest:

json
{
"skills": [
{ "source": "./skills/workflow-name" },
{
"source": "mattpocock:grilling",
"repo": "https://github.com/mattpocock/skills/tree/5b15a47f2d7150f545fbcacbfe381787fc0230dc"
},
{ "source": "./skills/custom-review" },
{
"source": "mattpocock:to-tickets",
"repo": "https://github.com/mattpocock/skills/tree/5b15a47f2d7150f545fbcacbfe381787fc0230dc"
}
]
}

Do not add a step for the entry skill. Do not create optional phases, abstractions, or local skills until the workflow needs them.

All versions