CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ralplan

Consensus planning entrypoint that auto-gates vague ralph/autopilot/team requests before execution

1.00x
Quality

74%

Does it follow best practices?

Impact

100%

1.00x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/ralplan/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%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 body delivers highly actionable, explicitly sequenced guidance: concrete commands, verdict tokens, provider-fallback rules, and a capped re-review feedback loop with thorough validation checkpoints. Its weaknesses are repeated restatements of the reviewer isolation/parallelism rules and references to docs files that are not shipped in the bundle.

Suggestions

State the reviewer parallel-vs-sequential and no-Architect-output-to-Critic rules once in a single note; they are currently repeated in steps 3-4, the blockquote after step 4, and the 'Important' note after step 8.

Ship or remove the dangling 'docs/company-context-interface.md' and 'docs/quality-gates-configuration.md' references, and consider moving the Pre-Execution Gate signal table and troubleshooting into a reference file.

Remove the empty '## Behavior' heading, which is immediately followed by another heading with no content between them.

DimensionReasoningScore

Conciseness

The body is dense operational rules with no explanations of concepts Claude already knows, but the reviewer parallelism/isolation rules are restated three to four times ("Architect output MUST NOT be passed to Critic" and "the same fixed plan snapshot" appear in steps 3-4, the blockquote, and the 'Important' note), and the '## Behavior' heading is empty. Mostly efficient but needs tightening, so it sits below the 'minor instances' level.

3 / 5

Actionability

Guidance is fully concrete and executable: exact commands ('omc quality-gates list --stage ralplan --json'), exact invocations ('/oh-my-claudecode:plan --consensus', 'Skill("oh-my-claudecode:team")'), exact verdict tokens ('VERDICT: PASS', 'APPROVE/ITERATE/REJECT'), config paths ('.claude/omc.jsonc'), and good/bad prompt examples covering the common cases.

5 / 5

Workflow Clarity

Steps 0-8 are explicitly sequenced with validation checkpoints at every stage (Critic verdict gating, the 5-iteration cap, blocking quality-gate PASS/BLOCK, 'gate_unavailable' reporting, 'pending approval' marking) and an explicit error-recovery feedback loop (non-APPROVE verdict → Planner revision → Architect → Critic → repeat).

5 / 5

Progressive Disclosure

Sections are well-organized with clear headers, but 'docs/company-context-interface.md' and 'docs/quality-gates-configuration.md' are cited as references yet absent from the bundle (no references/ directory exists), and the ~65-line Pre-Execution Gate section (signal table, examples, troubleshooting) is inlined content that could live in a separate file. Dangling references keep this below the 'good structure, minor gaps' level.

3 / 5

Total

16

/

20

Passed

Description

61%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 concise, third-person, and names the exact execution-mode keywords (ralph/autopilot/team) that should trigger it, giving it a distinct niche with low misfire risk. Its weaknesses are the absence of an explicit 'Use when...' clause and coverage of only one action (gating), leaving both completeness and specificity at the mid level.

Suggestions

Add an explicit 'Use when...' clause naming the trigger situations, e.g. 'Use when the user invokes ralph/autopilot/team with an underspecified request, or asks for consensus or multi-agent planning.'

Mention the core actions beyond gating: running the Planner/Architect/Critic loop to consensus and producing a plan marked 'pending approval'.

Include natural trigger synonyms such as 'plan', 'planning', 'scope the task', or '/ralplan' to broaden keyword coverage.

DimensionReasoningScore

Specificity

"Consensus planning entrypoint that auto-gates vague ralph/autopilot/team requests" names the domain plus one concrete action (gating underspecified execution requests), but never mentions the Planner/Architect/Critic consensus loop, plan artifacts, or approval workflow, matching the 'names domain and 1-2 concrete actions' anchor rather than the 'several specific actions' level.

3 / 5

Completeness

The 'what' is clear (consensus planning entrypoint that auto-gates vague requests before execution) but there is no 'Use when...' clause or equivalent explicit trigger guidance — the 'when' is only weakly implied by the mode keywords, which caps completeness at 3. Not 2 because the 'what' is concrete rather than vague.

3 / 5

Trigger Term Quality

"ralph", "autopilot", and "team" are the exact mode names users type when this skill should fire, giving good keyword coverage; common variations like "plan", "planning", "scope", or "/ralplan" are absent, so it falls short of the comprehensive-synonyms anchor.

4 / 5

Distinctiveness Conflict Risk

The specific execution-mode names (ralph/autopilot/team) and 'consensus planning' carve a clear niche with distinct triggers, but the skill is an alias for '/oh-my-claudecode:plan --consensus', creating minor overlap risk with that closely related planning skill.

4 / 5

Total

14

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

Yeachan-Heo/oh-my-claudecode

Path

skills/ralplan/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.