meta-kid-project-planner

Retired compatibility definition for historical meta-kid-project-planner runs. It is not available for discovery, automatic activation, or new invocation; its plan remains bundled only so persisted and in-flight run snapshots can be inspected, resumed, or replayed safely.

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./src/opensquilla/skills/bundled/meta-kid-project-planner/SKILL.md

Quality

Content

67%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 a well-structured, concise design overview that clearly explains composition, safety, and limitations, but its concrete executable detail resides in the frontmatter rather than the markdown body itself.

Suggestions

Move or mirror a concise step-by-step summary of the full DAG sequence into the body so the workflow is actionable without reading the frontmatter.

Resolve or remove opaque cross-references like "portfolio design §4.2" and "first-wave" that point to material not present in the bundle.

Add a short quick-start block for how to inspect, resume, or replay a snapshot to give the body concrete, copy-ready guidance.

Dimension	Reasoning	Score
Conciseness	The body is lean for its scope — a composition table, three safety layers, and limitations — and largely avoids explaining concepts Claude already knows, with only minor passages that could be trimmed.	4 / 5
Actionability	The body gives a concrete skill-to-step-to-role table and names specific gates, but the executable guidance (DAG prompts, commands) lives in the frontmatter rather than the body, leaving the body itself at a high-level instruction tier.	3 / 5
Workflow Clarity	The safety short-circuit (preferences -> feasibility -> redirect_unsafe) and the audit "final quality gate" are clearly sequenced with explicit checkpoints, though the full DAG sequence is not enumerated in the body.	4 / 5
Progressive Disclosure	Sections are well-organized with clear headers and no nested references, and no bundle files are needed; minor opaque cross-references ("portfolio design §4.2", "first-wave") keep it just below 5.	4 / 5
	Total	15 / 20 Passed

Description

58%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 clear and concrete about its unusual purpose as a retired compatibility artifact for snapshot inspection/resume/replay, but it is framed as an anti-trigger rather than providing positive "Use when..." guidance.

Suggestions

Add a positive trigger clause such as "Use when inspecting, resuming, or replaying a persisted or in-flight meta-kid-project-planner run snapshot" to lift completeness and trigger-term quality.

Include common user synonyms (e.g. "resume run", "replay snapshot", "inspect saved run") to broaden natural keyword coverage.

Name the snapshot artifacts explicitly so the niche is even more distinct from other run-inspection skills.

Dimension	Reasoning	Score
Specificity	Names the domain (retired compatibility definition for run snapshots) and several concrete actions — snapshots can be "inspected, resumed, or replayed safely" — with only minor coverage gaps.	4 / 5
Completeness	It clearly states what the definition is for, but offers an anti-trigger ("not available for...new invocation") rather than a positive "Use when..." clause, which caps completeness at 3 per the guidelines.	3 / 5
Trigger Term Quality	Terms like "inspected, resumed, or replayed" and "persisted and in-flight run snapshots" are relevant, but common variations or synonyms a user would naturally say are missing and no positive trigger phrase is given.	3 / 5
Distinctiveness Conflict Risk	The retired, non-invokable status and specific named scope make it highly distinct with minimal conflict risk, though it lacks distinct positive triggers that would push it to 5.	4 / 5
	Total	14 / 20 Passed

Validation

75%

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

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (1010 lines); consider splitting into references/ and linking	Warning
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	12 / 16 Passed

Repository: TokenRhythm/opensquilla
Path: src/opensquilla/skills/bundled/meta-kid-project-planner/SKILL.md
Commit: 94ac35e

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.