prometheus

Strategic planner - decomposes complex goals into actionable steps

Quality

38%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./skills/prometheus/SKILL.md

Quality

Content

77%

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

This is a solid strategic planning skill with excellent actionability through its concrete plan template and clear workflow methodology. The main weaknesses are moderate verbosity (persona framing, decorative quote) and keeping all content inline rather than using progressive disclosure for the detailed template. The skill effectively teaches Claude how to decompose complex goals into actionable stages.

Suggestions

Remove the persona framing ('You are Prometheus') and decorative quote to improve token efficiency

Consider extracting the detailed plan format template to a separate PLAN_TEMPLATE.md file and referencing it from the main skill

Dimension	Reasoning	Score
Conciseness	The content is reasonably efficient but includes some unnecessary elements like the Lincoln quote, the persona framing ('You are Prometheus'), and some explanatory text that Claude would already understand about planning methodology.	2 / 3
Actionability	Provides a concrete, copy-paste ready plan format template with specific fields, clear examples of what each section should contain, and explicit guidance on agent assignment, dependencies, and execution order.	3 / 3
Workflow Clarity	Clear 4-step methodology (Goal Analysis → Decomposition → Resource Planning → Execution Strategy) with explicit sequencing, the plan format shows clear stage dependencies, and includes risk mitigation as a validation checkpoint.	3 / 3
Progressive Disclosure	Content is well-structured with clear sections, but everything is inline in a single file. For a planning skill of this complexity, the detailed plan format template could be separated into a reference file, and the methodology could link to examples.	2 / 3
	Total	10 / 12 Passed

Description

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 is too vague and abstract to be useful for skill selection. It lacks concrete actions, natural trigger terms, explicit usage guidance, and distinctive characteristics that would help Claude choose it appropriately from a pool of skills.

Suggestions

Add a 'Use when...' clause with specific trigger scenarios (e.g., 'Use when user asks to break down a project, create a roadmap, plan a multi-step task, or needs help organizing complex work')

Replace abstract language with concrete actions (e.g., 'Creates step-by-step project plans, identifies dependencies, estimates timelines, breaks large tasks into subtasks')

Include natural keywords users would say (e.g., 'project plan', 'break down', 'roadmap', 'milestones', 'task list', 'how to approach')

Dimension	Reasoning	Score
Specificity	The description uses vague, abstract language ('strategic planner', 'complex goals', 'actionable steps') without listing any concrete actions. It doesn't specify what types of goals, what decomposition looks like, or what outputs are produced.	1 / 3
Completeness	The description weakly addresses 'what' (decomposes goals into steps) but completely lacks any 'when' guidance. There is no 'Use when...' clause or explicit trigger guidance for Claude to know when to select this skill.	1 / 3
Trigger Term Quality	Contains no natural keywords users would actually say. Terms like 'strategic planner' and 'decomposes' are not how users typically phrase requests - they might say 'break down', 'plan', 'steps', 'roadmap', 'how do I', etc.	1 / 3
Distinctiveness Conflict Risk	Extremely generic - 'complex goals' and 'actionable steps' could apply to virtually any planning, project management, task breakdown, or problem-solving skill. High conflict risk with many potential skills.	1 / 3
	Total	4 / 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

Repository: TurnaboutHero/oh-my-antigravity
Commit: fab464f

Reviewed: 4 months 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.