ralplan

Alias for /omc-plan --consensus

1.64x

Quality

38%

Does it follow best practices?

Impact

82%

1.64x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/ralplan/SKILL.md

Quality

Discovery

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

This description is critically deficient across all dimensions. It functions only as a technical pointer to another command without explaining what the skill does, when to use it, or providing any user-facing context. A user or Claude would have no way to understand when this skill should be selected.

Suggestions

Replace the alias reference with an actual description of what /omc-plan --consensus does (e.g., 'Creates implementation plans through team consensus' or similar concrete actions)

Add a 'Use when...' clause with natural trigger terms that describe scenarios when this skill should be selected (e.g., 'Use when the user wants collaborative planning, team agreement, or consensus-based decisions')

Include domain-specific keywords users would naturally say when they need this functionality, avoiding internal command names

Dimension	Reasoning	Score
Specificity	The description provides no concrete actions whatsoever. 'Alias for /omc-plan --consensus' is purely technical reference without explaining what the skill actually does.	1 / 3
Completeness	Fails to answer both 'what does this do' and 'when should Claude use it'. The description only references another command without explaining either the purpose or usage triggers.	1 / 3
Trigger Term Quality	Contains no natural keywords a user would say. 'omc-plan' and '--consensus' are internal technical jargon that users would not naturally use when seeking this functionality.	1 / 3
Distinctiveness Conflict Risk	Without any explanation of what the skill does, it's impossible to distinguish it from other skills. The alias reference provides no meaningful differentiation criteria.	1 / 3
	Total	4 / 12 Passed

Implementation

77%

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

This is a well-crafted skill with excellent workflow clarity and actionability. The consensus planning process is thoroughly documented with clear sequencing, validation steps, and iteration limits. The main weakness is verbosity in the Pre-Execution Gate section, which while useful, adds significant length and could benefit from being extracted to a separate reference file.

Suggestions

Consider extracting the Pre-Execution Gate section to a separate GATE.md file and referencing it, reducing the main skill to a concise overview

Trim the 'Why the Gate Exists' rationale section - Claude understands orchestration overhead without the detailed explanation

Dimension	Reasoning	Score
Conciseness	The skill is moderately efficient but includes some redundancy. The Pre-Execution Gate section is thorough but lengthy, and some explanations (like the 'Why the Gate Exists' rationale) could be trimmed since Claude understands orchestration concepts.	2 / 3
Actionability	Provides concrete, executable guidance with specific command syntax, clear flag definitions, detailed workflow steps, and practical examples in the Good vs Bad Prompts table. The signal detection table is particularly actionable.	3 / 3
Workflow Clarity	Excellent multi-step workflow with explicit sequencing (steps 1-8), clear validation checkpoints (Critic approval), iteration limits (max 5), and explicit warnings about sequential execution requirements. The re-review loop includes proper feedback mechanisms.	3 / 3
Progressive Disclosure	Content is well-structured with clear sections, but the skill is somewhat monolithic. The Pre-Execution Gate section is substantial and could potentially be split into a separate reference file. References to other skills (Plan, team, ralph) are present but inline content is heavy.	2 / 3
	Total	10 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: Yeachan-Heo/oh-my-claudecode
Commit: 48ffaac

Reviewed: 4 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.