CtrlK
BlogDocsLog inGet started
Tessl Logo

using-superpowers

Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

56

Quality

64%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/using-superpowers/SKILL.md

The canonical home for this skill is using-superpowers in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

78%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, mostly lean instruction skill with a clear decision flowchart and concrete actionable guidance. Its main weaknesses are minor redundancy in the emphatic opening block and the absence of an explicit recovery feedback loop for when a skill turns out to be wrong.

DimensionReasoningScore

Conciseness

Mostly tight with well-organized sections and a compact Red Flags table; the only padding is the all-caps <EXTREMELY-IMPORTANT> block, which restates the rule already given in the description and '## The Rule' section.

4 / 5

Actionability

Gives concrete actionable guidance — exact announce phrase, TodoWrite-per-checklist, a decision flowchart, and worked example mappings — but the 'how to find skills' / non-Claude-Code path is hand-wavy ('check your platform's documentation').

4 / 5

Workflow Clarity

The graphviz flowchart lays out a clear, coherent sequence from message receipt through skill invocation to response, but there is no explicit error-recovery/feedback loop beyond a single sentence noting an invoked skill need not be used.

4 / 5

Progressive Disclosure

No bundle files exist and none are needed; the body is self-contained with clear, well-organized section headers, satisfying the simple-skill exception for progressive disclosure.

5 / 5

Total

17

/

20

Passed

Description

51%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 states both a purpose and a trigger, but the trigger ('starting any conversation') is so broad that it creates extreme conflict risk with every other skill. Specificity and trigger-term coverage are mid-tier because the language is largely about internal mechanism rather than user-facing task signals.

Suggestions

Replace 'Use when starting any conversation' with task-specific triggers that name concrete situations (e.g., 'Use when the user's request may match an installed skill, before taking any action or asking clarifying questions').

Add concrete trigger keywords a user would actually say (task verbs, domain names) rather than mechanism language like 'Skill tool invocation'.

Narrow the scope so the description signals a distinct niche instead of firing on every conversation.

DimensionReasoningScore

Specificity

Names the skill-discovery domain and two concrete actions ('establishes how to find and use skills', 'requiring Skill tool invocation before ANY response') but coverage is not comprehensive — no enumeration of skill types or task categories.

3 / 5

Completeness

Both 'what' (find/use skills, invoke Skill tool) and 'when' ('Use when starting any conversation') are present, but the 'when' is overly broad and could be far more specific to user tasks.

4 / 5

Trigger Term Quality

Contains one genuine natural trigger phrase ('Use when starting any conversation') but the remainder is internal-mechanism language ('Skill tool invocation', 'before ANY response including clarifying questions') with no synonyms or variations.

3 / 5

Distinctiveness Conflict Risk

'Use when starting any conversation' is maximally broad and would apply to virtually every conversation, conflicting with essentially any other skill.

1 / 5

Total

11

/

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.

Validation15 / 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
administrakt0r/AI-Agents-Safe-Coding-Skills
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.