oma-brainstorm

Design-first ideation that explores user intent, constraints, and approaches before any planning or implementation. Use for brainstorming, ideation, exploring concepts, and evaluating approaches.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

73%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.

The content is a well-sequenced, actionable workflow with strong validation checkpoints and feedback loops, appropriate for an instruction-only skill. Its main weakness is redundancy from restating the same workflow across multiple sections.

Suggestions

Consolidate the four restatements of the workflow (Scenes/Transitions, Canonical workflow path, Execution Phases, Guardrails) into a single canonical sequence plus a concise guardrail list to reduce token cost.

Clarify or remove the resources/triz-lite.md reference since no references/ directory exists in this skill's bundle, or add the missing bundle file.

Note which ../_shared/core/ references are auto-injected by oma agent:spawn versus required reading, so the reader knows which external paths are guaranteed present.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and avoids explaining concepts Claude already knows, but the core workflow is restated four times (Scenes/Transitions, Canonical workflow path, Execution Phases, and Guardrails), which is more than minor over-explanation and could be consolidated.	3 / 5
Actionability	Provides concrete executable guidance including specific commands ('oma state:emit', 'oma state:verify --checkpoint option-selection'), defined output formats (prose briefs with scenario/mechanism/solves-leaves/cost feel, tier 1/2/3 issue lists), and concrete file paths, with only minor gaps from non-inlined shared references.	4 / 5
Workflow Clarity	The multi-step process is clearly sequenced with explicit validation checkpoints (section-by-section approval, blind review with Tier 1 resolution before save, state:verify checkpoints) plus feedback loops and a Failure-and-recovery section for error recovery.	5 / 5
Progressive Disclosure	Good section structure with clearly signaled one-level-deep references in a dedicated References section, but the referenced paths point outside the skill bundle (../_shared/core/...) and resources/triz-lite.md is referenced despite no references/ directory existing in this bundle.	4 / 5
	Total	16 / 20 Passed

Description

87%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.

The description is strong, clearly stating both the skill's purpose and explicit use-when triggers with natural language users would say. It is distinct from sibling planning/QA/debugging skills and avoids vague fluff.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete actions ('explores user intent, constraints, and approaches', 'evaluating approaches') with only minor gaps in coverage, falling short of the comprehensive concrete-action list needed for a 5.	4 / 5
Completeness	Explicitly answers both what ('Design-first ideation that explores user intent, constraints, and approaches before any planning or implementation') and when ('Use for brainstorming, ideation, exploring concepts, and evaluating approaches') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural user phrases ('brainstorming, ideation, exploring concepts, and evaluating approaches') with good coverage, though a few natural synonyms like 'design' or 'I have an idea' are missing.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (design-first ideation before planning/implementation) with distinct triggers, and the body's 'When NOT to use' routing to oma-pm/oma-qa/oma-debug minimizes conflict risk.	5 / 5
	Total	18 / 20 Passed

Validation

100%

Warnings & errors only

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-brainstorm/SKILL.md
Commit: 032c988

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.