CtrlK
BlogDocsLog inGet started
Tessl Logo

prometheus

Strategic planner - decomposes complex goals into actionable steps

56

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/prometheus/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 well-structured, actionable planning skill with a clear sequenced methodology and a reusable plan template. It would benefit from an explicit plan-review/validation checkpoint and removal of the decorative quote.

Suggestions

Add an explicit validation step to the methodology, e.g. '5. Plan Review: verify each stage has clear inputs/outputs and dependencies before delegating.'

Remove the closing Abraham Lincoln quote — it is decorative padding that does not aid execution.

Tighten the 'When Called by Sisyphus' section or move agent-routing specifics to a reference if the skill grows.

DimensionReasoningScore

Conciseness

The body is largely lean with bullet-driven methodology and a compact template, but the closing Lincoln quote is decorative padding that does not earn its place, keeping it just below a 5.

4 / 5

Actionability

It provides a concrete, copy-paste-ready plan format template with explicit fields (Agent, Goal, Input, Output, Effort, Dependencies) and example stages; minor gaps keep it from a 5.

4 / 5

Workflow Clarity

The four-step methodology (Goal Analysis, Decomposition, Resource Planning, Execution Strategy) is clearly sequenced with fallback/risk notes, but it lacks an explicit validation checkpoint or review step before execution.

4 / 5

Progressive Disclosure

Content is well-organized into clear sections with no unnecessary external references, but the file exceeds the under-50-line simple-skill threshold and the closing quote is minor filler, so it sits at 4 rather than 5.

4 / 5

Total

16

/

20

Passed

Description

53%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 conveys a clear niche and one concrete capability but omits any explicit 'when to use' trigger guidance, which caps completeness. Adding a 'Use when...' clause with natural trigger phrases would substantially improve it.

Suggestions

Append a 'Use when...' clause with concrete trigger phrases, e.g. 'Use when the user asks to plan, strategize, or break down a complex multi-step goal.'

List 2-3 more concrete planning actions (dependency identification, risk assessment, timeline planning already in the body) in the description itself for fuller coverage.

Include natural synonyms users actually say ('plan', 'strategy', 'roadmap') to improve trigger-term quality.

DimensionReasoningScore

Specificity

The phrase 'decomposes complex goals into actionable steps' names the strategic-planning domain and one concrete action, matching the score-3 anchor of a clear domain plus 1-2 actions without comprehensive coverage.

3 / 5

Completeness

It clearly answers 'what' (strategic planner that decomposes goals) but provides no explicit 'Use when...' trigger guidance, so per the guideline a missing trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Natural terms like 'strategic', 'planner', 'goals', and 'steps' appear, but common synonyms and the natural trigger phrases users would say (e.g. 'plan', 'strategy') are only weakly present, fitting the score-3 anchor.

3 / 5

Distinctiveness Conflict Risk

The strategic-planning / task-decomposition niche is mostly distinct with only minor overlap risk against general project-management skills, matching the score-4 anchor better than the broader score-3 anchor.

4 / 5

Total

13

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
TurnaboutHero/oh-my-antigravity
Reviewed

Table of Contents

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.