plano-config-fundamentals

Validate and fix Plano config fundamentals. Use for config versioning, listener types, provider registration, secrets handling, and startup validation failures.

Quality

75%

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-config-fundamentals/SKILL.md

Quality

Content

65%

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 lean and well-organized for a simple skill, but its actionability and workflow clarity suffer from a lack of executable examples and an explicit validation loop, and its rule references dangle without backing files.

Suggestions

Add a short before/after YAML snippet showing a correct config (version, one default provider, $ENV_VAR secrets) vs a broken one, so the checklist items are copy-paste actionable.

Turn "Apply These Rules" into real, clearly signaled one-level-deep references (e.g., linked reference files under references/) or inline the key rules directly so nothing dangles.

Make step 5 an explicit validate->fix->retry checkpoint (run `planoai up`; if validation fails, fix and re-run) instead of just instructing Claude to return a verification plan.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — it does not explain what config.yaml or listeners are, and every section (When To Use, Apply These Rules, Execution Checklist) earns its place, matching the score-3 "lean and efficient" anchor.	3 / 3
Actionability	It has concrete specifics like "version: v0.3.0", "$ENV_VAR substitution", and "planoai up", but lacks executable example snippets and the "Apply These Rules" entries (config-version, config-listeners, etc.) resolve to nothing, fitting the score-2 "some concrete guidance but incomplete" anchor rather than copy-paste-ready 3.	2 / 3
Workflow Clarity	The five-step Execution Checklist is sequenced and ends with a verification plan, but validation is expressed as "return a ... verification plan" rather than an explicit validate->fix->retry checkpoint loop, matching the score-2 "steps listed but validation checkpoints implicit" anchor.	2 / 3
Progressive Disclosure	The skill is short and well-sectioned, but the "Apply These Rules" entries are unsignaled backticked names that reference no actual files (no references/, scripts/, or assets/ bundle exists), fitting the score-2 "references present but not clearly signaled" anchor rather than well-resolved one-level-deep references.	2 / 3
	Total	9 / 12 Passed

Description

85%

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, action-oriented, and clearly answers both what the skill does and when to use it with an explicit trigger clause. Its only weakness is trigger-term coverage, which is solid but leans slightly technical.

Dimension	Reasoning	Score
Specificity	The phrase "Validate and fix Plano config fundamentals" paired with the enumerated concrete concerns ("config versioning, listener types, provider registration, secrets handling, and startup validation failures") lists multiple specific concrete actions, matching the score-3 anchor rather than the single-domain score-2 anchor.	3 / 3
Completeness	It states what ("Validate and fix Plano config fundamentals") and explicitly when via a "Use for ..." trigger clause, so it clears the bar that would cap a missing trigger clause at 2.	3 / 3
Trigger Term Quality	Terms like "secrets handling" and "startup validation failures" are reasonably natural, but "listener types" and "provider registration" lean technical and the coverage is moderate rather than the broad natural-term spread of a 3; it sits at the score-2 "some relevant keywords but missing common variations" level.	2 / 3
Distinctiveness Conflict Risk	It targets a specific product niche (Plano config) with distinct, domain-specific triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 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-config-fundamentals/SKILL.md
Commit: d23e276

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