plano-config-fundamentals

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

Quality

72%

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

57%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 lean and well sectioned, but it leans on four named rules that resolve to nothing — no files, paths, or inline content — leaving the checklist not fully executable. Validation is framed as something to plan rather than perform, and the pinned v0.3.0 version adds time-sensitivity without context. The skill needs its rule content made resolvable and an explicit verification checkpoint.

Suggestions

Make the four rules resolvable: either link them as actual files (e.g. references/config-version.md with the rule content) or inline the essential rule details so the checklist is executable on its own.

Turn step 5 into an explicit validation checkpoint — run or instruct the user to run `planoai up` after applying the patch, with a fix-and-retry loop if validation fails, instead of merely returning a verification plan.

Move the pinned `version: v0.3.0` into a version-matrix or compatibility note so the checklist step does not go stale as the config schema evolves.

Dimension	Reasoning	Score
Conciseness	The body is lean with no padding and no explanation of concepts Claude already knows. However, "Ensure `version: v0.3.0` is present" pins a time-sensitive version number in the main checklist rather than a version-matrix or deprecated section, which the guidelines say should penalize conciseness.	4 / 5
Actionability	The checklist contains real specifics ("exactly one default provider", "$ENV_VAR substitution", "planoai up"), but the core rules — `config-version`, `config-listeners`, `config-providers`, `config-secrets` — have no paths, links, or backing files, and "Confirm listener type matches intended architecture" cannot be executed without their definitions. Concrete guidance is present but incomplete.	3 / 5
Workflow Clarity	A clear five-step numbered sequence is present, but validation is only something to propose ("Return minimal patch and a `planoai up` verification plan") rather than an explicit checkpoint with a validate→fix→retry loop. The sequence matches anchor 3: steps listed with an implicit checkpoint rather than explicit validation.	3 / 5
Progressive Disclosure	Sections are well organized and the skill is under 50 lines, but "Apply These Rules" references four rules that are neither file paths nor links, and no references/, scripts/, or assets/ directories exist — the references are dangling. This matches anchor 3: references present but not clearly signaled or resolvable.	3 / 5
	Total	13 / 20 Passed

Description

87%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 strong: it names the domain, lists concrete capability areas, and includes an explicit "Use for..." trigger clause covering the full config surface. It is concise and highly distinct from other skills. Minor room remains to surface natural trigger terms that live only in the body (config.yaml, planoai up, schema validation).

Dimension	Reasoning	Score
Specificity	"Validate and fix" provides two concrete verbs applied across five named areas (config versioning, listener types, provider registration, secrets handling, startup validation failures). It falls just short of anchor 5 because only two distinct actions are named, though coverage of the domain is broad.	4 / 5
Completeness	It explicitly answers both: what ("Validate and fix Plano config fundamentals") and when ("Use for config versioning, listener types, provider registration, secrets handling, and startup validation failures"). This matches the anchor-5 pattern of a clear what plus an enumerated, concrete trigger clause.	5 / 5
Trigger Term Quality	Phrases like "config versioning", "secrets handling", and "startup validation failures" are natural things a user would say, giving good keyword coverage. A few natural terms are missing, such as "config.yaml", "planoai up", or "schema validation" — terms that appear in the body but not the description.	4 / 5
Distinctiveness Conflict Risk	"Plano config" is a clearly defined niche with distinct trigger terms spanning five specific sub-areas, creating minimal conflict risk with generic or sibling skills. It does not use broad wording that other skills would also claim.	5 / 5
	Total	18 / 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-config-fundamentals/SKILL.md
Commit: 72002a6

Reviewed: 19 hours 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.