CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

plan

Lightweight planning with optional interview

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/oh-my-codex/skills/plan/SKILL.md

The canonical home for this skill is plan in Yeachan-Heo/oh-my-codex

SKILL.md
Quality
Evals
Security

Quality

Content

75%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 is a well-structured, dense instruction set: modes, triggers, sequencing, stop conditions, output format, and quality gates are all explicit and mostly executable, with a final checklist providing validation. Weaknesses are minor — some repeated policy statements, a few vague directives (outcome-first framing, role consults), and optional-only validation in Direct mode — and no external references are needed or used.

DimensionReasoningScore

Conciseness

The body is telegraphic and lean — "Ask one question at a time; gather codebase facts first", "Right-size steps to scope; save to `.omx/plans/`" — with no explanations of concepts Claude already knows. It is not 5 because "`omx explore` is deprecated" is stated twice (Execution_Policy and Tool_Usage) and the 80%/90% thresholds are repeated across Execution_Policy, Final_Checklist, and Advanced, and the "outcome-first framing" sentence is dense filler that could be trimmed.

4 / 5

Actionability

Concrete, executable guidance dominates: explicit flags (`--interview`, `--direct`, `--review`), a save path (`.omx/plans/`), a specific command (`omx question` with `OMX_QUESTION_RETURN_PANE`), verdict values (APPROVED/REVISE/REJECT), and testable thresholds (80%+ claims cite file/line, 90%+ criteria testable). Not 5 because directives like "apply outcome-first framing, concise visible updates" and "consult Analyst for hidden requirements" are non-executable without further definition; not 3 because there is no pseudocode and the specifics cover the common cases.

4 / 5

Workflow Clarity

The multi-step processes are clearly sequenced — a Mode Selection table, numbered steps per mode, and explicit checkpoints ("Stop interviewing when requirements are clear — do not over-interview", the Final Checklist, the Review verdict gate). Not 5 because the Direct mode's validation is only "Optional Critic review if requested" and the interview-to-plan flow lacks an explicit validate-and-revise feedback loop; not 3 because checkpoints are explicit rather than implicit, and the operations are neither destructive nor batch (no cap applies).

4 / 5

Progressive Disclosure

There are no bundle files (references/, scripts/, assets/ are absent) and the body references none, so everything lives inline — appropriately, since the content is compact and policy-like, organized into well-labeled sections (Purpose, Use_When, Do_Not_Use_When, Execution_Policy, Steps, Tool_Usage, Escalation, Final_Checklist, Advanced). Not 5 because at ~90 lines it exceeds the under-50-line simple-skill exception and the Advanced section nests "##" headers inside a tag block, a minor organization gap; not 3 because no content that belongs in separate files is inlined and navigation is easy.

4 / 5

Total

16

/

20

Passed

Description

45%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 but under-specified: it names the planning domain and one feature (optional interview) without listing concrete capabilities (plan creation, review/evaluation, requirements scoping) or any "use when" trigger guidance. It reads closer to a title than a capability description, and its trigger surface relies almost entirely on the single word "planning".

Suggestions

Add a "Use when..." clause with natural trigger phrases, e.g. "Use when the user asks to plan before implementing, says 'plan this' or 'let's plan', or when requirements are vague and need scoping".

List the concrete capabilities instead of naming only the domain, e.g. "Creates concise, actionable work plans, gathers requirements via Socratic interview, and evaluates existing plans with APPROVED/REVISE/REJECT verdicts".

Include synonyms and mode keywords users would naturally say — "plan", "planning", "scope requirements", "review a plan" — to strengthen trigger coverage and distinctiveness against neighboring execution/goal skills.

DimensionReasoningScore

Specificity

"Lightweight planning with optional interview" names the domain ("planning") but lists no concrete actions such as creating, reviewing, or scoping plans — matching the anchor "Names the domain but actions are minimal or generic" ("Processes PDF files"). It is not 3 because "with optional interview" describes a mode feature rather than a concrete action like "extracts content", and not 1 because the domain is explicitly named rather than pure abstraction.

2 / 5

Completeness

A domain-level "what" is present ("Lightweight planning") but the "when" is entirely absent — no "Use when" clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. Not 4 because there is no "when" at all; not 2 because the "what", while thin, is more informative than pure vagueness.

3 / 5

Trigger Term Quality

"planning" is a natural keyword a user would say, but common variations and synonyms ("plan this", "create a plan", "scope", "requirements gathering") are missing — the anchor 3 fit "Some relevant keywords but missing common variations or synonyms". Not 4 because only one strong natural term is present; not 2 because "planning" is domain-relevant rather than generic filler like "works with files".

3 / 5

Distinctiveness Conflict Risk

"planning" is a broad activity that overlaps with other orchestration/goal skills (the body itself references "ultragoal" and "team"), leaving moderate overlap risk — anchor 3 "Somewhat specific but could still overlap with similar skills". Not 4 because no distinct triggers are named to separate it from planning-adjacent skills; not 2 because "optional interview" adds a narrowing, distinctive element.

3 / 5

Total

11

/

20

Passed

Validation

100%

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

Yeachan-Heo/oh-my-codex

Path

plugins/oh-my-codex/skills/plan/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.