CtrlK
BlogDocsLog inGet started
Tessl Logo

ralplan

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

76

2.69x
Quality

65%

Does it follow best practices?

Impact

97%

2.69x

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

70%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 delivers a clear, well-validated multi-step consensus workflow with strong actionability and feedback loops, but it is padded by repeated restatements of the sequential-review rule and makes no use of bundle files for progressive disclosure.

Suggestions

State the Architect/Critic sequential-and-independent rule once in a dedicated callout and reference it from steps 3-4 instead of restating it four times.

Move the company-context interface details into a bundled references/ file and link to it with a clearly signaled section rather than burying the reference in step 0.

DimensionReasoningScore

Conciseness

The body is mostly efficient, but the Architect/Critic sequential-and-independent rule is restated roughly four times (steps 3, 4, the blockquote, and the 'Important' note), which is unnecessary padding that could be tightened.

3 / 5

Actionability

It gives concrete slash-commands, exact flag behaviors, specific approval options, and good/bad prompt examples, with only minor gaps from delegating full detail to the Plan skill documentation.

4 / 5

Workflow Clarity

Steps 0-8 are clearly sequenced with explicit validation checkpoints (pending-approval gate, APPROVE/ITERATE/REJECT verdicts, a max-5 re-review feedback loop, and a pre-execution gate), matching the anchor for clear sequences with feedback loops.

5 / 5

Progressive Disclosure

No bundle files are provided and all content is inlined in one file; the single external reference (docs/company-context-interface.md) is buried inside step 0 rather than clearly signaled, fitting the some-structure anchor.

3 / 5

Total

15

/

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 specific and distinct with good trigger-term coverage of the ralph/autopilot/team keywords, but it lacks an explicit 'Use when...' trigger clause, leaving the 'when' only weakly implied and capping completeness.

Suggestions

Add an explicit trigger clause such as 'Use when a user issues a vague ralph, autopilot, or team request that lacks a concrete target' to satisfy the 'when' requirement.

Expand the action list beyond 'auto-gates' (e.g., 'redirects vague requests into consensus planning, drafts a pending-approval plan, then stops') to lift specificity toward comprehensive coverage.

DimensionReasoningScore

Specificity

Names the domain ('consensus planning entrypoint') and one concrete action ('auto-gates vague ralph/autopilot/team requests before execution'), but lists only a single action rather than several, matching the 1-2 concrete actions anchor.

3 / 5

Completeness

The 'what' is clear but there is no explicit 'Use when...' clause; the 'when' is only weakly implied by 'auto-gates vague requests', so completeness is capped at 3 per the missing-trigger-guidance rule.

3 / 5

Trigger Term Quality

Includes natural trigger terms users actually say ('ralph', 'autopilot', 'team') plus 'consensus planning', giving good keyword coverage with only minor synonyms missing.

4 / 5

Distinctiveness Conflict Risk

It carves a distinct niche as a gating entrypoint for specific execution modes with minimal conflict risk, though minor overlap remains with the related plan/ralph/team skills.

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.

Validation15 / 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
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.