planner-rt-ica

Identify required inputs, dependencies, and uncertainty during planning. Use when generating plans or task graphs under incomplete information. Does not block plan generation; instead localizes gaps and creates unblock dependencies.

Install with Tessl CLI

npx tessl i github:Jamie-BitFlight/claude_skills --skill planner-rt-ica

What are skills?

Review — 64%

Does it follow best practices?

If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:

npx tessl skill review --optimize ./path/to/skill

Learn more

Validation — 10 / 11 Passed

Validation for skill structure

SKILL.md

Review

Evals

Discovery

67%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This description has good structural completeness with an explicit 'Use when' clause and explains both purpose and trigger conditions. However, it uses somewhat abstract/technical language that may not match natural user queries, and the domain of 'planning under incomplete information' could benefit from more concrete examples of what this looks like in practice.

Suggestions

Add more natural trigger terms users might say, such as 'missing information', 'what do I need to know', 'blockers', or 'unclear requirements'

Include concrete examples of the actions performed, such as 'flags unknown variables', 'marks assumptions', or 'identifies questions to ask'

Dimension	Reasoning	Score
Specificity	Names the domain (planning/task graphs) and some actions ('identify required inputs, dependencies, and uncertainty', 'localizes gaps', 'creates unblock dependencies'), but the actions are somewhat abstract rather than concrete operations a user would recognize.	2 / 3
Completeness	Clearly answers both what ('Identify required inputs, dependencies, and uncertainty', 'localizes gaps and creates unblock dependencies') and when ('Use when generating plans or task graphs under incomplete information') with an explicit 'Use when' clause.	3 / 3
Trigger Term Quality	Includes relevant terms like 'planning', 'task graphs', 'incomplete information', and 'dependencies', but these are more technical/internal terms than natural phrases users would say. Missing common variations like 'missing info', 'what do I need', 'blockers'.	2 / 3
Distinctiveness Conflict Risk	The focus on 'incomplete information' and 'unblock dependencies' provides some distinction, but 'planning' and 'task graphs' could overlap with general planning or project management skills. The niche is moderately specific but not sharply defined.	2 / 3
	Total	9 / 12 Passed

Implementation

62%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill provides solid conceptual guidance for planning-phase input analysis with clear workflow sequencing and explicit behavioral rules. However, it lacks concrete examples of the output format and could be more concise by consolidating overlapping sections. The actionability would significantly improve with sample outputs showing what an 'APPROVED-WITH-GAPS' analysis actually looks like.

Suggestions

Add a concrete example showing a complete output (Completeness Summary through Planning Annotations) for a realistic planning scenario

Consolidate 'Core Principles' and 'Behavioral Rules for the Planner' sections to reduce redundancy

Include a template or schema for the 'Missing Inputs' entries showing exact field structure

Add a link to the related rt-ica skill file if it exists, or clarify the reference

Dimension	Reasoning	Score
Conciseness	The skill is reasonably efficient but includes some redundancy (e.g., restating 'The planner MUST' patterns multiple times, explaining the relationship to RT-ICA which could be briefer). Some sections like 'Core Principles' overlap with 'Behavioral Rules'.	2 / 3
Actionability	Provides clear conceptual guidance and output structure, but lacks concrete examples of the output format, sample annotations, or template task blocks. The 'Output Contract' describes what to produce but doesn't show executable examples of the structured analysis.	2 / 3
Workflow Clarity	Clear sequence: pre-pass analysis → completeness summary → missing inputs identification → unblock actions → annotations. The workflow explicitly states when this runs (before task decomposition), what outputs are required, and how it connects to downstream rt-ica execution checks.	3 / 3
Progressive Disclosure	Content is well-organized with clear sections, but everything is inline in a single file. For a skill of this complexity, examples of output formats and annotation templates could be split into referenced files. The relationship to RT-ICA section suggests external dependencies but doesn't link to them.	2 / 3
	Total	9 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

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