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

78%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/oma-brainstorm/SKILL.md

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.

A well-structured, actionable workflow skill with strong sequencing and explicit validation checkpoints. Its main weakness is redundancy: the core workflow is restated in four overlapping sections, inflating token cost without adding clarity.

Suggestions

Consolidate the Scenes, Canonical workflow path, Execution Phases, and Transitions sections into a single canonical sequence to remove the repeated restatements of the same 5-7 step workflow.

Add one short worked example of a prose brief (scenario / mechanism / solves-leaves / cost feel) and the comparison matrix format so the 'prose before matrix' guardrail is concrete rather than only described.

Trim guardrail/phase overlap: several guardrails (e.g. 'Always propose 2-3 approaches', 'Blind review before save') restate Execution Phases content verbatim; cross-reference instead of repeating.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and avoids explaining concepts Claude already knows, but the same 5-7 step workflow is restated across Scenes, Canonical workflow path, Execution Phases, and Transitions, which is padding that could be consolidated.	3 / 5
Actionability	Concrete, executable guidance is present (specific commands like 'oma state emit' and 'oma state verify --checkpoint option-selection', paths 'docs/plans/designs/', tiered issue lists, tactical/structural labels), with minor gaps such as no sample prose brief or comparison matrix.	4 / 5
Workflow Clarity	A clearly sequenced multi-step process with explicit validation checkpoints (section-by-section approval, blind review, Tier 1 resolution, state verify checkpoint), feedback loops (Failure and recovery, rejection transitions), and a Common Pitfalls checklist; no destructive or batch operations so no validation cap applies.	5 / 5
Progressive Disclosure	No bundle files exist, but the body references external materials one level deep in a clearly signaled References section (e.g. 'resources/triz-lite.md', '../_shared/core/clarification-protocol.md') and is well-sectioned; the dense, somewhat redundant body keeps it just short of a clean overview.	4 / 5
	Total	16 / 20 Passed

Description

82%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, third-person description that clearly states both capability and trigger conditions with a distinct pre-planning design niche. The main weakness is that the named actions are abstract ideation verbs rather than concrete operations.

Dimension	Reasoning	Score
Specificity	Names the domain ('Design-first ideation') and a few actions ('explores user intent, constraints, and approaches', 'evaluating approaches'), but the actions are abstract ideation verbs rather than concrete operations, matching the 'names domain and 1-2 concrete actions but not comprehensive' anchor.	3 / 5
Completeness	It explicitly answers both 'what' ('Design-first ideation that explores user intent, constraints, and approaches before any planning or implementation') and 'when' with a concrete 'Use for ...' trigger clause listing multiple trigger activities.	5 / 5
Trigger Term Quality	'Use for brainstorming, ideation, exploring concepts, and evaluating approaches' gives good coverage of natural phrases users would say, though a few common variations (e.g. 'I have an idea', 'let's design something') that appear in the body are absent from the description.	4 / 5
Distinctiveness Conflict Risk	The 'before any planning or implementation' framing carves a clear pre-planning design niche with distinct triggers and minimal overlap with implementation/planning skills.	5 / 5
	Total	17 / 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: 7721120

Reviewed: 5 days 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.