Agent skill

Omk Skill Creation

by KaimingWan in KaimingWan/oh-my-kiro

Create high-quality, production-ready skills from scratch. An agent skill from KaimingWan/oh-my-kiro.

MITAuto-check passedAgent Workflows

Install Omk Skill Creation

skills CLI
$ npx skills add KaimingWan/oh-my-kiro --skill omk-skill-creation -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install KaimingWan/oh-my-kiro omk-skill-creation --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/KaimingWan/oh-my-kiro.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/omk-skill-creation .claude/skills/omk-skill-creation && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
omk-skill-creation
GitHub stars
107
Token cost
~2k tokens
SKILL.md length
831 words
Files
3 (incl. references)
Skills in repo
15
Repo updated
First seen
Licence
MIT

At a glance

Create high-quality, production-ready skills from scratch. An agent skill from KaimingWan/oh-my-kiro.

  • Works in 5 steps: Should This Be a Skill? → Design (Before Writing SKILL.md) → Write SKILL.md → …
  • User says create skill
  • SKILL.md covers Trigger Examples, Philosophy, Phase 0: Should This Be a Skill? and Phase 1: Design (Before…, plus 5 more sections
  • Calls bash and python3

What it does

Omk Skill Creation is an agent skill from KaimingWan/oh-my-kiro. Create high-quality, production-ready skills from scratch. Trigger when user says 'create skill', 'new skill', 'write a skill', 'make a skill', '创建 skill', '写个 skill', 'skillify', or when packaging a repeated workflow into a reusable skill. Also trigger when reviewing or improving existing skills.

Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/authoring-guide.md`).

It sits in Agent Workflows, covering Skill authoring. The licence is MIT.

When your agent uses it

  • User says create skill
  • Packaging a repeated workflow into a reusable skill
  • Improving existing skills

Example prompts

  • “create skill”
  • “new skill”
  • “write a skill”
  • “/omk-skill-creation”

Requirements

  • Python 3

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Should This Be a Skill?
  2. Design (Before Writing SKILL.md)
  3. Write SKILL.md
  4. Test
  5. Review Checklist

What it can do on your machine

Read from SKILL.md and the folder at commit ba228be. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • bash
    • python3

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Omk Skill Creation loads about 2k tokens when it runs, and up to ~3.5k if it reads all its reference files. Until then it costs about 79 tokens; SKILL.md has 831 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~79
When it runs · the whole SKILL.md, loaded when a task matches
~2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from KaimingWan/oh-my-kiro at commit ba228be, republished under its MIT licence (© KaimingWan). 831 words, ~2,023 tokens.

Download SKILL.mdSave it as .claude/skills/omk-skill-creation/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
omk-skill-creation
description
Create high-quality, production-ready skills from scratch. Trigger when user says 'create skill', 'new skill', 'write a skill', 'make a skill', '创建 skill', '写个 skill', 'skillify', or when packaging a repeated workflow into a reusable skill. Also trigger when reviewing or improving existing skills.

Skill Creation — From Idea to Production

Trigger Examples

  • "把这个重复流程做成 skill"
  • "create a new skill for code review"
  • "帮我写一个 SEO 研究的 skill"
  • "review and improve this skill"
  • "这个工作流应该 skillify"

Philosophy

Context window is a public good. Only add what the agent doesn't already know.

A skill is an onboarding manual for the agent — after reading it, the agent knows your process, standards, and preferences without re-teaching every session.

Phase 0: Should This Be a Skill?

Before writing anything, decide the right mechanism:

SignalMechanism
Rule needed in EVERY conversationAGENTS.md / rules.md
Must run automatically on eventsHook (gate/ or feedback/)
Teaches agent a specific workflowSkill ← you are here
Gives agent a new tool/APIMCP server
Needs isolated context executionSubagent

Skill ROI threshold: Will this workflow run ≥3 times? If not, just explain in conversation.

Phase 1: Design (Before Writing SKILL.md)

Step 1: Define Use Cases

Write 3-5 concrete user prompts that should trigger this skill. Not abstract descriptions — actual sentences users will type:

Example for a "daily planning" skill:
- "plan my day"
- "start work"
- "今天做什么?"
- "morning routine"
- "daily standup prep"

These prompts shape everything: skill name, description, input/output, workflow steps.

Step 2: Define Input → Output
QuestionAnswer
What does the user provide?(file, URL, text, nothing?)
What does the skill produce?(file, report, action, decision?)
What format?(markdown, JSON, email, code?)
Step 3: Choose Pattern
Need external APIs/real-time data?→ Pattern C: Skill + MCP
Need deterministic computation?→ Pattern B: Prompt + Scripts
Agent judgment alone is enough?→ Pattern A: Prompt-Only

When in doubt, start with Pattern A. Add scripts later if needed.

Step 4: Choose Freedom Level
FragilityFreedomExample
High (DB migration, deploy)Low — exact commands, no variationRun exactly: python migrate.py --verify
Medium (code generation)Medium — template with parametersPseudocode + config options
Low (code review, writing)High — guidelines + heuristics"Check for X, Y, Z"

Phase 2: Write SKILL.md

File Structure
my-skill/
├── SKILL.md              # Required. < 500 lines
├── scripts/              # Optional. Deterministic code
├── references/           # Optional. Loaded on demand
└── assets/               # Optional. Templates, data
Frontmatter (Critical)

The description determines whether the skill ever triggers. Agent defaults to NOT triggering — your description must be "pushy."

yaml
---
name: kebab-case-name        # ≤64 chars, lowercase + hyphens only
description: >                # ≤1024 chars, third person
  [What it does]. Trigger when user says [keyword1], [keyword2],
  [keyword3], or [scenario description]. Also trigger when
  [implicit trigger condition].
---

Rules:

  • Third person always ("Processes X", not "I help you" or "You can use this")
  • First sentence: what it does (purpose)
  • Second sentence: explicit trigger keywords (list actual user phrases)
  • Third sentence: implicit triggers (file types, contexts, patterns)
  • Be specific > be brief. Use all 1024 chars if needed

Bad: description: Helps with data tasks Good: description: Analyze sales/revenue CSV files to find patterns and calculate metrics. Trigger when user mentions sales data, revenue analysis, profit margins, or uploads xlsx/csv with financial column headers.

Body Structure
markdown
## Trigger Examples
- "realistic user prompt 1"
- "realistic user prompt 2" (different language/style)
- "realistic user prompt 3"
- "realistic user prompt 4"
- "realistic user prompt 5"

## [Workflow Steps]
Step 1: ...
Step 2: ...

## [Rules / Constraints]

## [Output Format] (if applicable)
Writing Principles
  1. Concise is key — Claude is smart. Only add what it doesn't know. Challenge every paragraph: "Does this justify its token cost?"
  2. Reasons > commands — "Show command before executing, because users need to verify safety" beats "ALWAYS show commands. NEVER execute directly."
  3. Examples > explanations — One input/output pair teaches more than three paragraphs of description
  4. One default, one escape hatch — Don't list 5 options. Pick the best one, mention the alternative for edge cases
  5. Consistent terminology — Pick one term, use it everywhere. Not "endpoint/URL/route/path" interchangeably
Show full SKILL.md (343 more words)Show less
Progressive Disclosure
  • SKILL.md = overview + navigation (< 500 lines)
  • references/ = detailed docs, loaded on demand
  • scripts/ = executable code, runs without entering context
  • Reference depth: max 1 level. SKILL.md → reference.md. Never reference.md → sub-reference.md
  • For references > 100 lines, add a table of contents at top

Phase 3: Test

Write Messy Test Prompts

Real users make typos, use slang, forget file names. Test with realistic prompts, not clean ones:

# Good (realistic)
"ok so my boss sent me this xlsx (its in downloads, called
something like 'Q4 sales final FINAL v2.xlsx') and she wants
profit margin as a percentage"

# Bad (too clean)
"Please analyze the sales data in the uploaded Excel file
and add a profit margin column"
Iteration Loop
  1. Run skill with test prompts
  2. Did it trigger? If not → fix description
  3. Did it produce correct output? If not → fix workflow steps
  4. Is output format right? If not → fix template/examples
  5. Repeat
Check Trigger Rate

Short simple requests rarely trigger skills. Ensure test set includes prompts with enough complexity and matching keywords.

Phase 4: Review Checklist

Before shipping, verify:

  • Description is specific, includes trigger keywords, third person
  • SKILL.md body < 500 lines
  • Has 5 Trigger Examples with realistic prompts
  • Long content split into references/
  • No time-sensitive info (or in "old patterns" section)
  • Consistent terminology throughout
  • Concrete examples, not abstract explanations
  • Reasons given for rules (not just MUST/NEVER)
  • Scripts handle errors explicitly (don't punt to agent)
  • No hardcoded secrets or magic numbers
  • Tested with messy realistic prompts

Anti-Patterns

Don'tDo Instead
Stuff everything in SKILL.mdSplit to references/ at 500 lines
Vague description ("helps with data")Specific + trigger keywords
First/second person descriptionThird person always
List 5 equivalent optionsOne default + one escape hatch
MUST/NEVER without reasonExplain why the rule exists
Test with clean prompts onlyTest with messy realistic prompts
Write skill before iterating in conversationGet workflow right first, then extract
Deeply nested references (A→B→C)Max 1 level deep
Assume packages installedList dependencies explicitly
Magic numbers in scriptsDocument why each value was chosen

OMK-Specific Conventions

When creating skills for oh-my-kiro projects:

  1. Naming: omk- prefix for framework skills, project-specific names for project skills
  2. Location: Framework skills → oh-my-kiro/skills/, project skills → skills/
  3. Security: Run bash tools/audit-skill.sh <dir> before installing external skills
  4. Sync: After creating in submodule, run bash tools/sync-omk.sh . to propagate
  5. Registration: python3 scripts/generate_configs.py to update platform configs

© KaimingWan, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in skills/omk-skill-creation of KaimingWan/oh-my-kiro.

  • SKILL.md
  • omk-skill-creation
  • references/authoring-guide.md

Open the folder on GitHubat commit ba228be

Compare with similar skills

Omk Skill Creation next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Omk Skill Creation compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Omk Skill Creation this skillKaimingWan/oh-my-kiro107—~2kAutomated safety check: PassMIT
Skill CreatorAzure/azqr79589 repos~8.2kAutomated safety check: PassApache-2.0
Claude Code Skill Developer Guidediet103/claude-code-infrastructure-showcase10k11 repos~3.5kAutomated safety check: PassMIT
Darwin Skill Optimizeralchaincyf/darwin-skill6.2k1 repos~4.7kAutomated safety check: PassMIT
Claude Code Command Developmentanthropics/claude-plugins-official38k10 repos~4.8kAutomated safety check: PassApache-2.0
Claude Code Plugin Structureanthropics/claude-plugins-official38k10 repos~3.4kAutomated safety check: PassApache-2.0

Similar skills

  • Skill Creator

    Azure/azqr

    Official

    Create new skills, modify and improve existing skills, and measure skill performance.

    795 GitHub starsUsed in 89 repos~8.2k tokens
    Agent WorkflowsAuto-check passed
  • Claude Code Skill Developer Guide

    diet103/claude-code-infrastructure-showcase

    A guide to creating and managing Claude Code skills with auto-activation: skill-rules.json triggers, hooks, enforcement levels, YAML frontmatter and progressive disclosure.

    10k GitHub starsUsed in 11 repos~3.5k tokens
    Agent WorkflowsAuto-check passed
  • Darwin Skill Optimizer

    alchaincyf/darwin-skill

    Scores SKILL.md files on a nine-dimension rubric, then improves them in a keep-or-revert loop with independent judge agents, test prompts, git history and human checkpoints.

    6.2k GitHub starsUsed in 1 repo~4.7k tokens
    Agent WorkflowsAuto-check passed
  • Claude Code Command Development

    anthropics/claude-plugins-official

    Official

    Explains how to write Claude Code slash commands: Markdown files with YAML frontmatter, arguments, file references, bash context and interactive prompts.

    38k GitHub starsUsed in 10 repos~4.8k tokens
    Agent WorkflowsAuto-check passed
  • Claude Code Plugin Structure

    anthropics/claude-plugins-official

    Official

    Explains the directory layout, plugin.json manifest and component organization of a Claude Code plugin, including auto-discovery and portable paths.

    38k GitHub starsUsed in 10 repos~3.4k tokens
    Agent WorkflowsAuto-check passed
  • Skill Release Gate

    rohitg00/ai-engineering-from-scratch

    Evaluates an Agent Skill bundle before release for structure, trigger quality, artifact improvement, script correctness, safety, installed-tree integrity and host portability.

    66k GitHub stars~1k tokensUpdated today
    Agent WorkflowsAuto-check passed

More from KaimingWan/oh-my-kiro

All 15 skills in this repo
  • Omk Research

    KaimingWan/oh-my-kiro

    Multi-level research: built-in knowledge → web search → Tavily deep research API.

    107 GitHub stars~827 tokensUpdated 6 mo ago
    Auto-check passed
  • Omk Reviewing

    KaimingWan/oh-my-kiro

    Code and plan review with multi-angle dispatch. An agent skill from KaimingWan/oh-my-kiro.

    107 GitHub stars~1.9k tokensUpdated 6 mo ago
    Auto-check passed
  • Omk Youtube

    KaimingWan/oh-my-kiro

    Extract and summarize YouTube video content via subtitle extraction.

    107 GitHub stars~381 tokensUpdated 6 mo ago
    Auto-check passed
  • Documentation Lookup

    KaimingWan/oh-my-kiro

    Fetch current library/framework documentation via Context7. An agent skill from KaimingWan/oh-my-kiro.

    107 GitHub stars~616 tokensUpdated 6 mo ago
    Auto-check passed
  • Omk Coding

    KaimingWan/oh-my-kiro

    Enforces coding best practices: deep-read before modify, LSP-first navigation, TDD red-green-refactor, minimal changes, self-review, verification.

    107 GitHub stars~2.4k tokensUpdated 6 mo ago
    Auto-check passed
  • Omk Debugging

    KaimingWan/oh-my-kiro

    Systematic debugging: reproduce → hypothesize → verify → fix.

    107 GitHub stars~4.7k tokensUpdated 6 mo ago
    Auto-check passed

Categories

Questions about Omk Skill Creation

What does Omk Skill Creation do?

Create high-quality, production-ready skills from scratch. An agent skill from KaimingWan/oh-my-kiro. Omk Skill Creation is an agent skill from KaimingWan/oh-my-kiro. Create high-quality, production-ready skills from scratch.

When should I use Omk Skill Creation?

Omk Skill Creation fits situations like: user says create skill; packaging a repeated workflow into a reusable skill; improving existing skills.

How do I install Omk Skill Creation in Claude Code?

Run `npx skills add KaimingWan/oh-my-kiro --skill omk-skill-creation -a claude-code`. Or copy the skill folder (skills/omk-skill-creation in KaimingWan/oh-my-kiro) into .claude/skills/omk-skill-creation in your project. Claude Code loads it when a task matches its description.

How do I install Omk Skill Creation in Codex?

Run `npx skills add KaimingWan/oh-my-kiro --skill omk-skill-creation -a codex`. Or copy the skill folder (skills/omk-skill-creation in KaimingWan/oh-my-kiro) into .agents/skills/omk-skill-creation in your project. Codex loads it when a task matches its description.

Can I use Omk Skill Creation in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add KaimingWan/oh-my-kiro --skill omk-skill-creation -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/omk-skill-creation, .gemini/skills/omk-skill-creation, .github/skills/omk-skill-creation and .opencode/skills/omk-skill-creation in your project.

What does Omk Skill Creation need to run?

Going by SKILL.md and its folder, Omk Skill Creation needs the command-line tools its instructions call (bash and python3). Our summary lists: Python 3.

Does Omk Skill Creation access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Omk Skill Creation safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Omk Skill Creation use?

Omk Skill Creation is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Omk Skill Creation use?

About 2k tokens (SKILL.md is roughly 8.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.5k tokens, read only when the agent opens those files.

What are the alternatives to Omk Skill Creation?

Skills that share tags, products or a category with Omk Skill Creation: Skill Creator (Azure/azqr, 795 stars), Claude Code Skill Developer Guide (diet103/claude-code-infrastructure-showcase, 10k stars), Darwin Skill Optimizer (alchaincyf/darwin-skill, 6.2k stars) and Claude Code Command Development (anthropics/claude-plugins-official, 38k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Omk Skill Creation?

KaimingWan (a GitHub user) maintains it in KaimingWan/oh-my-kiro, which has 107 GitHub stars. The repository holds 15 skills in this directory. The repository was last updated on April 2, 2026.

Source: KaimingWan/oh-my-kiro on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.