plano-cli-operations

Apply Plano CLI best practices. Use for startup troubleshooting, cli_agent workflows, and template-based project bootstrapping.

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/plano-cli-operations/SKILL.md

Quality

Content

68%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 admirably concise and well-structured for a simple CLI skill, but it stops short of giving the exact commands it tells the reader to provide, and the named rules reference no underlying material.

Suggestions

Add the actual exact CLI commands for each checklist step (e.g. 'planoai up', 'planoai cli_agent --agent <name>', 'planoai init --template <tmpl>') so the runbook is copy-paste ready rather than a directive to produce one.

Either link the three rule labels (cli-startup, cli-agent, cli-init) to reference files that define them, or inline a one-line definition for each so they are not dangling labels.

Insert an explicit validation checkpoint in the checklist, e.g. 'After planoai up, verify the agent endpoint responds before debugging deeper', to add a feedback loop for startup troubleshooting.

Dimension	Reasoning	Score
Conciseness	The body is lean (~20 lines) with no padding or over-explanation of concepts Claude already knows; every line carries an instruction, matching the score-5 anchor of lean and efficient content that assumes Claude's competence.	5 / 5
Actionability	The checklist gives high-level steps ('Follow startup validation order', 'Use cli_agent to route coding-agent traffic') and the When To Use section quotes command names, but the execution steps themselves omit the actual exact CLI commands, fitting the score-3 anchor of some concrete guidance that is incomplete.	3 / 5
Workflow Clarity	A clear four-step numbered sequence is present, but validation is only implicit ('Follow startup validation order') with no explicit checkpoint or error-recovery loop, matching the score-3 anchor of steps listed with missing or implicit checkpoints.	3 / 5
Progressive Disclosure	The skill is short, single-purpose, and well-organized into clear sections (When To Use, Apply These Rules, Execution Checklist), but the 'Apply These Rules' entries (cli-startup, cli-agent, cli-init) are labels that point to no content or reference, a minor organization gap placing it at the score-4 anchor rather than 5.	4 / 5
	Total	15 / 20 Passed

Description

66%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 clearly answers both what and when and is well-scoped to the Plano CLI niche, but the 'what' relies on generic 'best practices' phrasing and the trigger terms are somewhat technical without natural synonyms.

Suggestions

Replace 'Apply Plano CLI best practices' with concrete verbs, e.g. 'Diagnose planoai startup failures, route coding-agent traffic through cli_agent, and bootstrap projects from planoai init templates.'

Add natural user-facing synonyms to the trigger list, such as 'planoai up errors', 'CLI agent routing', or 'scaffold a new project', so the description matches phrases users actually say.

Drop the vague 'best practices' framing in favor of the three concrete capabilities already listed in the body's When To Use section.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Plano CLI') and three operational areas ('startup troubleshooting, cli_agent workflows, and template-based project bootstrapping'), but the action verb is generic ('Apply...best practices') rather than a concrete action, matching the score-3 anchor of domain plus a few concrete actions without comprehensive coverage.	3 / 5
Completeness	Both 'what' ('Apply Plano CLI best practices') and 'when' ('Use for startup troubleshooting, cli_agent workflows, and template-based project bootstrapping') are present and explicit, but the 'what' is generic ('best practices') so it sits at the score-4 anchor rather than the fully-concrete score-5 anchor.	4 / 5
Trigger Term Quality	It includes relevant terms ('startup troubleshooting', 'cli_agent workflows', 'bootstrapping') but they lean technical and lack common synonyms or file extensions, fitting the score-3 anchor of some relevant keywords missing natural variations.	3 / 5
Distinctiveness Conflict Risk	Tied specifically to the 'Plano CLI' tool and three named workflows, giving it a clear niche with distinct triggers and minimal conflict risk, matching the score-5 anchor.	5 / 5
	Total	15 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: katanemo/plano
Path: skills/plano-cli-operations/SKILL.md
Commit: 003c36a

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