oma-skill-creation
Create or revise OMA skills and their references. Use for skill
Install / Use
npx skills add first-fluke/oh-my-agent --skill oma-skill-creationInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
LegalSupported Platforms
Tags
Our assessment of oma-skill-creation
oma-skill-creation scores 82/100 on our quality scale, 162nd of 209 Legal skills we index.
Its SKILL.md is 5.9 KB long, well organised into 18 sections and no code examples: a thorough specification that gives an agent plenty to work with.
With 1,324 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so oma-skill-creation is actively maintained.
- Our last check on 2026-11-07 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-01. Automated pattern scan on 2026-10-01. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
oma-skill-creation compared with similar skills
All 4 of these similar skills score higher than oma-skill-creation; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| oma-skill-creation (this skill)by first-fluke | 82 | 1.3k | 54d ago | SKILL.md |
| x402by browser-use | 100 | 121.0k | 3d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
| pptxby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
| designby nextlevelbuilder | 100 | 149.0k | 6d ago | SKILL.md |
Frequently asked questions
- How do I install oma-skill-creation?
- Run
npx skills add first-fluke/oh-my-agent --skill oma-skill-creation. The install tabs above show the steps for each supported agent. - Which AI agents does oma-skill-creation work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is oma-skill-creation safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is oma-skill-creation still maintained?
- The repository was last updated about 2 months ago, so oma-skill-creation is actively maintained.
Skill content
View source on GitHubname: oma-skill-creation description: Create or revise OMA skills and their references. Use for skill routing, execution contracts, conditional loading, and authoring validation.
OMA Skill Authoring
Scheduling
Goal
Create or revise a usable OMA skill with clear routing, one execution path, domain-specific recovery, and proportionate context.
Intent signature
- Create, update, audit, or normalize an OMA skill, its resources, or the SSL-lite format.
- Decide whether content belongs inline, in a conditional resource, or should be removed.
When to use
- Authoring
.agents/skills/{name}/SKILL.mdand supporting resources. - Reviewing skill routing, execution contracts, reference loading, or duplicated instructions.
When NOT to use
- Installing third-party skills -> skill installer; creating a Codex plugin -> plugin tooling.
- Application implementation -> the owning specialist; project requirements ->
oma-pm.
Expected inputs
Skill purpose, triggers, boundaries, execution model, and existing commands/resources or user edits to preserve.
Expected outputs
A four-section SKILL.md, only necessary supporting resources, and validation results with unresolved limitations.
Dependencies
resources/ssl-lite-template.md for the skeleton and resources/validation-checklist.md for acceptance criteria. Use native file tools and available oma skill validators. Follow repository rules for source ownership and generated copies.
Structural Flow
Transitions
- New skill: compare 1–3 analogous skills, then use the template.
- Existing skill: preserve working domain detail and change only the requested scope.
- Repeated instructions: retain one authoritative location and a short reference where independently invoked entry points need it.
- Long or conditional detail: move to a named resource with a load condition. Do not move a duplicate merely to keep it elsewhere.
- Machine-checkable artifacts: declare structured
outputs:as documented in the template.
Failure and recovery
| Failure | Recovery | |---|---| | Overbroad routing | Narrow triggers and add a concrete When NOT to use cross-route | | Vague execution | Add actual objects, paths, command flags, and evidence to the canonical path | | Repeated procedure in multiple sections | Keep the canonical procedure; retain only distinct branches or state transitions elsewhere | | Required tool unavailable | Use the documented fallback; otherwise report which result cannot be verified | | Conflicting source and generated copies | Use the repository's generation flow; do not hand-edit protected definitions |
Exit
A completed skill has valid structure, useful routing, executable steps, recoverable failures, valid references, and applicable validation evidence. Missing tools or unresolved assumptions must remain explicit.
Logical Operations
Canonical workflow path
- Read the target, its invoked resources, and relevant repository rules. Identify which entry points run independently and which content the runtime already injects.
- Select command-heavy, judgment-heavy, or reference-heavy behavior. Use the template's minimal skeleton and optional sections only where they add information.
- Write the canonical procedure once. Preserve exact command/output contracts, failure mechanisms, side effects, and harmful-action limits; remove generic restatements and redundant examples.
- Index resources once under References with load conditions. Keep source-adjacent evidence one hop from SKILL.md where possible.
- Run
oma skill lint --skill <name>andgit diff --check. If routing descriptions changed, runoma skill audit. Apply the content checks inresources/validation-checklist.mdthat automated lint does not cover. - Report the changes, checks, and remaining limits. Do not claim reduced token usage merely from removing duplicate files; measure the context actually loaded when making that claim.
Resource scope and effects
Skill work reads and may change local definitions/resources and generated vendor copies through the authorized repository flow. User data and credentials are not skill examples. Commits and publishing require the corresponding authorization.
Guardrails
- Keep YAML
nameand a routing-gradedescription. Preserve the four top-level headings: Scheduling, Structural Flow, Logical Operations, References. - Keep one canonical command/workflow path, an Intent signature, When to use/When NOT to use, input/output expectations, failure recovery, and relevant effects/guardrails. Section titles beyond these are optional when their information is already represented.
- Entry, Scenes, Actions, and tool/scope tables must add distinct information. Do not repeat a procedure to fill the template.
- Keep SKILL.md under 500 body lines. Load supporting resources conditionally; do not create README/changelog/install documents inside a skill merely to explain the skill.
- Keep parsed output/schema examples. Do not prescribe decorative report layouts or add generic self-review loops; use runnable validators and explicit evidence requirements.
- Process bulk data through deterministic tools and return summaries/artifact paths instead of streaming raw data into context.
- Preserve unrelated user edits. Apply the shared execution policy to clarification, authorization, and verification.
References
- Prompt behavior and model comparisons:
resources/prompt-evaluation.md(routing, injection, authorization, or review-contract changes) - Skeleton and optional sections:
resources/ssl-lite-template.md(authoring or restructuring) - Acceptance criteria:
resources/validation-checklist.md(validation) - Context loading:
../_shared/core/context-loading.md(resource/injection decisions) - Quality principles:
../_shared/core/quality-principles.md(domain verification requirements) - Eval fixtures:
web/docs/guide/skill-eval.md(when measuring held-out task utility withoma skill evaloroma skill optimize)
Related Skills
x402
121.0kSet up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
pptx
177.9kUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an em…
design
149.0kComprehensive design skill: brand identity, design tokens, UI styling, logo generation (55 styles, Gemini, Atlas Cloud, or MuAPI AI), corporate identity program (50 deliverables, CIP mockups), HTML presentations (Chart.js), banner design (22 styles, social/ads/web/print), icon design (15 styles, SVG…
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
