CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

oma-image

Generate raster images or reference-guided variations through the OMA image CLI. Use for image assets or explicit vendor comparisons; pixel editing uses an editor.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

The canonical home for this skill is oma-image in first-fluke/oh-my-agent

SKILL.md
Quality
Evals
Security

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-guarded skill body with copy-paste commands, explicit cost/auth/exit-code handling, and clearly signaled one-level references. Its weaknesses are meta-scaffolding sections that add tokens without adding guidance and a slightly disorganized References section interrupted by a nested Configuration block.

Suggestions

Delete the meta-scaffolding sections ('Scheduling', 'Goal', 'Intent signature', 'Control-flow features', 'Resource scope' table, 'Preconditions', 'Effects and side effects') — they restate routing and routing-adjacent information already in 'When to use'/'When NOT to use' and the transitions, cutting the body by roughly a third.

Move the '### Configuration' subsection out of '## References' and reunify the split reference list (invocation, execution-protocol, vendor-matrix, prompt-tips, checklist, context-loading) into one annotated list so navigation is unbroken.

Merge 'Dependencies' and 'Tools and instruments', which duplicate the same CLI and resource enumerations, into a single line or fold into the canonical command path section.

DimensionReasoningScore

Conciseness

The core content (guardrails, canonical commands, exit codes, config migration) is dense and non-obvious, but several sections are padded scaffolding Claude does not need: 'Scheduling/Goal', 'Intent signature', 'Control-flow features', the 'Resource scope' table, and 'Preconditions/Effects' restate information already covered elsewhere. This fits anchor 3 (mostly efficient, some sections that could be tightened) rather than 2, since the padding is a minority of the document and most tokens carry real information.

3 / 5

Actionability

Fully executable guidance throughout: copy-paste-ready commands ('oma image doctor', 'oma image generate "<prompt>" --vendor auto --size auto --quality auto --output json', the --reference variant), a concrete cost threshold ('$0.20'), bypass flags (--yes / OMA_IMAGE_YES=1), env vars, config keys with file paths, and enumerated exit codes. This matches anchor 5 — specific examples cover the common cases.

5 / 5

Workflow Clarity

Entry/Transitions/Failure-and-recovery/Exit gives a clear sequence with explicit error-recovery loops (auth missing, timeout, outdated CLI) and defined exit criteria including partial success. It falls short of anchor 5 because the handoff checklist is delegated to an external file rather than shown, and validation (doctor) is listed as a command rather than woven into the step sequence as an explicit checkpoint.

4 / 5

Progressive Disclosure

References are one level deep and purpose-annotated ('Execution steps (follow for the selected task): resources/execution-protocol.md', 'selected vendor or reference-image operation only' for invocation.md), which is good navigation. It is not a 5 because the '### Configuration' subsection is oddly nested under '## References' and splits the reference list in two, and no bundle files ship alongside SKILL.md in this workspace to verify the referenced paths resolve.

4 / 5

Total

16

/

20

Passed

Description

78%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, concise description in third-person voice that states concrete capabilities, explicit triggers, and a clear boundary. Its main weakness is that the 'Use for' clause could name more of the natural vocabulary (illustration, photo, picture) that would broaden trigger coverage.

Suggestions

Expand the 'Use for' clause with concrete natural phrases users actually say, e.g., 'Use when the user asks to generate an image, illustration, product photo, or concept art, or to compare image models'.

Mention reference-image regeneration in the trigger clause explicitly (e.g., 'or supplies a reference image to vary') since that is a core capability currently only implied.

DimensionReasoningScore

Specificity

The description lists several concrete actions — 'Generate raster images', 'reference-guided variations', 'explicit vendor comparisons', routed 'through the OMA image CLI' — plus a boundary ('pixel editing uses an editor'). It falls just short of anchor 5 because coverage has minor gaps (e.g., manifests, output options, regeneration controls are unmentioned), and it is well above anchor 3 since more than 1-2 actions are named.

4 / 5

Completeness

Both parts are present: what ('Generate raster images or reference-guided variations through the OMA image CLI') and when ('Use for image assets or explicit vendor comparisons'). It is not a 5 because 'image assets' is a somewhat generic trigger phrase compared to concrete triggers like 'when the user asks to generate an image, illustration, or compare image models'.

4 / 5

Trigger Term Quality

Natural phrases like 'image assets', 'vendor comparisons', and 'reference-guided variations' match what users would say, but common synonyms such as 'illustration', 'picture', 'photo', 'concept art', or file extensions (.png/.jpg) are missing. This sits between anchor 3 (missing common variations) and anchor 5 (comprehensive synonyms/extensions), closer to 4.

4 / 5

Distinctiveness Conflict Risk

The description anchors a clear niche to the OMA image CLI, names a distinct use (vendor comparison), and explicitly routes pixel editing elsewhere, minimizing conflict with editor or general image skills. It clearly matches the anchor 5 example pattern of a distinct trigger set.

5 / 5

Total

17

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

first-fluke/oh-my-agent

Path

.agents/skills/oma-image/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.