CtrlK
BlogDocsLog inGet started
Tessl Logo

plan-mode

Structured planning mode for autonomous task execution. Creates plans as MemoryDocs, executes via Missions, tracks progress with live checklist.

66

Quality

80%

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 ./skills/plan-mode/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

100%

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 tight, actionable protocol with explicit tool calls, a concrete plan format, and sequenced workflows including an error-recovery feedback loop. It is well-organized and self-contained with no unnecessary concept explanation.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it never explains what MemoryDocs or Missions are, and each section earns its tokens with no padding or concept exposition.

3 / 3

Actionability

It gives concrete, executable guidance: named tool calls with parameters (e.g., `mission_create` with name/goal/cadence) and a copy-paste-ready plan document format with example step lines.

3 / 3

Workflow Clarity

Each phase is a clearly numbered sequence, and execution includes an explicit feedback loop (step fails → try ONE alternative → if still failing, mark status "failed" and stop), giving validation checkpoints for the risky autonomous path.

3 / 3

Progressive Disclosure

The skill is a self-contained protocol with well-organized sections and no nested or missing references; no bundle files exist and splitting into external files would add no value, so the single well-sectioned file is appropriate.

3 / 3

Total

12

/

12

Passed

Description

60%

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 conveys concrete capabilities but omits an explicit "when to use" trigger clause and leans on the separate activation block for natural trigger terms. Adding a "Use when…" clause with user-natural phrasing would raise completeness and trigger-term quality.

Suggestions

Append a "Use when…" clause naming natural user phrases (e.g., "Use when the user asks to plan out a task, create a step-by-step plan, or run autonomous execution").

Surface common trigger variations ("make a plan", "execution plan", "plan how to") directly in the description rather than only in the activation keywords.

Tighten the distinctiveness by naming what makes this skill unique (MemoryDoc-backed plans + Mission execution) in the description itself.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "Creates plans as MemoryDocs, executes via Missions, tracks progress with live checklist" — rather than vague language.

3 / 3

Completeness

It clearly states what the skill does but provides no explicit "Use when…" or equivalent trigger guidance for when Claude should invoke it, which caps completeness at 2.

2 / 3

Trigger Term Quality

It includes relevant terms ("planning", "plans", "Missions") but the natural user trigger phrases ("create a plan", "execution plan") live in the activation block, not the description, so common variations are missing from the evaluated text.

2 / 3

Distinctiveness Conflict Risk

"Structured planning mode" is a somewhat specific niche, but without explicit distinct triggers in the description it could still overlap with general planning or task-management skills.

2 / 3

Total

9

/

12

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
nearai/ironclaw
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.