plano-deployment-security

Apply Plano deployment and production security practices. Use for Docker networking, state storage choices, readiness checks, and environment-based secret handling.

Quality

78%

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-deployment-security/SKILL.md

Quality

Content

86%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 content is a tight, well-organized, actionable checklist that assumes Claude's competence and includes a validation checkpoint. Its only weakness is the absence of fully executable code examples and an explicit failure-recovery loop.

Suggestions

Add a short executable snippet or exact command for the readiness check (e.g., a curl /healthz example) to move actionability toward fully executable.

Expand the final step into an explicit feedback loop: 'If a check fails, surface the failure-mode diagnostic, fix, and re-verify before declaring success.'

Optionally clarify the state-storage decision criteria (when to choose PostgreSQL vs. alternatives) so the guidance is copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The body is lean and efficient: short bullets, no padding, and no explanation of concepts Claude already knows; every line earns its place.	5 / 5
Actionability	Concrete, specific guidance is provided throughout ('Use `host.docker.internal`', 'Prefer PostgreSQL state storage', 'Verify `/healthz`', 'secrets remain environment-based'), but it lacks complete executable code blocks for every step, leaving minor gaps.	4 / 5
Workflow Clarity	A numbered execution checklist gives a clear sequence and includes a validation checkpoint ('Verify `/healthz` before traffic or CI assertions') plus a failure-mode diagnostic step, but it lacks an explicit fix-and-retry feedback loop.	4 / 5
Progressive Disclosure	Under 50 lines with no external references needed and well-organized sections (When To Use, Apply These Rules, Execution Checklist), which the rubric scores 5 for simple, well-structured skills.	5 / 5
	Total	18 / 20 Passed

Description

70%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 with a concrete, Plano-specific trigger set and good keyword coverage. It is concise without fluff, though its capability list reads as topic areas rather than vivid concrete actions and lacks explicit user-sayable trigger phrasings.

Suggestions

Reframe capability areas as concrete verbs (e.g., 'Configure Docker networking, set up persistent state storage, add readiness checks, manage environment-based secrets') to lift specificity.

Add an explicit user-trigger phrasing such as 'Use when the user asks about unreachable Plano agents, production state storage, or /healthz checks' to strengthen completeness and trigger-term quality.

Include natural synonyms (e.g., 'health checks', 'liveness probes', 'env vars') to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Lists several concrete capability areas ('Docker networking, state storage choices, readiness checks, and environment-based secret handling') but these are topics rather than verbatim concrete actions, matching the anchor naming a domain with a few concrete actions without comprehensive coverage.	3 / 5
Completeness	Explicitly states both what ('Apply Plano deployment and production security practices') and when ('Use for...'), but the when clause lists topic areas rather than concrete user trigger phrasings, keeping it just below a 5.	4 / 5
Trigger Term Quality	Natural trigger phrases like 'Docker networking' and 'readiness checks' appear, giving good keyword coverage, though a few common synonyms or variations a user might say are missing.	4 / 5
Distinctiveness Conflict Risk	The named 'Plano deployment' niche combined with the specific security/deployment trigger set is mostly distinct, with only minor overlap risk against generic devops or deployment skills.	4 / 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-deployment-security/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.