plano-advanced-patterns

Design advanced Plano architectures. Use for multi-listener systems, prompt target schema quality, and layered orchestration patterns.

Quality

60%

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-advanced-patterns/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-organized, but it is an outline of principles rather than usable instruction: no concrete schemas, listener configurations, or examples, and its two named rules point to bundle files that do not exist. A user following this skill would know the goals but not how to achieve them.

Suggestions

Add one concrete example of a strict prompt target parameter schema and one multi-listener configuration snippet so the checklist directives are executable.

Either inline the content of 'advanced-multi-listener' and 'advanced-prompt-targets' or ship them as actual files with linked paths (e.g., 'See [advanced-multi-listener.md](references/advanced-multi-listener.md)').

Turn the checklist into a sequenced workflow with explicit validation checkpoints (e.g., verify tool-call schemas against a test scenario before recommending migration).

Dimension	Reasoning	Score
Conciseness	The ~30-line body is lean and efficient: 'Use this skill for higher-order architecture decisions once fundamentals are stable' plus short sectioned lists, with no padding and no explanation of concepts Claude already knows. Matches 'Lean and efficient; assumes Claude's competence; every token earns its place'.	5 / 5
Actionability	The checklist items are abstract directives — 'Define prompt target parameters with strict, explicit schemas', 'Minimize ambiguity that causes malformed tool calls' — with no code, commands, or examples of what a strict schema or layered listener looks like. Matches 'Minimal concrete guidance; high-level hints but missing the specific steps to execute'; not 3 because there is no executable or even pseudocode-level guidance anywhere.	2 / 5
Workflow Clarity	The Execution Checklist provides a rough five-item sequence, but the items are principles rather than ordered steps and validation is only mentioned ('Provide migration-safe recommendations and test scenarios'), not built in as a checkpoint. Matches 'Steps listed but validation gaps; sequence present but checkpoints missing or implicit'; not 2 because a coherent checklist structure does exist.	3 / 5
Progressive Disclosure	The body is short and well-sectioned, but 'Apply These Rules' names two rules ('advanced-multi-listener', 'advanced-prompt-targets') that have no corresponding files in the bundle (references/, scripts/, assets/ are absent) and no paths or links. Matches 'Some structure but could be better organized; references present but not clearly signaled'; not 4 because the references dangle entirely — the referenced content is unreachable.	3 / 5
	Total	13 / 20 Passed

Description

62%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, third-person, and cleanly separates a what-statement from a Use-for trigger clause with niche-specific terms. It is weakened by abstract, jargon-heavy trigger phrases and a single broad action verb instead of a list of concrete capabilities.

Suggestions

List 2-3 concrete capabilities (e.g., 'Configure stacked model, prompt, and agent listeners; define strict prompt target parameter schemas') instead of the single verb 'Design'.

Rewrite the trigger clause in user-intent form with synonyms, e.g. 'Use when the user asks to combine listeners, tighten tool-call schemas, or layer orchestration in a Plano system'.

Add a phrase distinguishing it from a fundamentals skill (e.g., 'Use once basic Plano setups are stable and you need advanced patterns').

Dimension	Reasoning	Score
Specificity	The description names the domain ('advanced Plano architectures') and one concrete action ('Design'), then lists focus areas ('multi-listener systems, prompt target schema quality, layered orchestration patterns') rather than multiple specific actions. It matches 'Names domain and 1-2 concrete actions, but not comprehensive' — not 4 because it lacks a list of several distinct executable actions.	3 / 5
Completeness	It answers both what ('Design advanced Plano architectures') and when ('Use for multi-listener systems, prompt target schema quality, and layered orchestration patterns'). Matches 'Has both what and when; when could be more explicit or specific' — not 5 because the trigger clause lists topic areas rather than concrete user-intent phrases like 'Use when the user asks to...'.	4 / 5
Trigger Term Quality	Phrases like 'multi-listener systems', 'prompt target schema quality', and 'layered orchestration patterns' are relevant domain keywords, but they read as technical jargon and miss natural variations or synonyms a user might say. Matches 'Some relevant keywords but missing common variations or synonyms'; not 4 because there are no plain-language trigger phrases.	3 / 5
Distinctiveness Conflict Risk	Plano-specific terminology (multi-listener, prompt target schema, layered orchestration) carves a clear niche with minor overlap risk against a general 'plano' fundamentals skill. Matches 'Mostly distinct; minor overlap risk with closely related skills'; not 5 because nothing in the description itself separates it from a basic Plano skill.	4 / 5
	Total	14 / 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-advanced-patterns/SKILL.md
Commit: 72002a6

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