CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

superpowers-lab

Lab environment for Claude superpowers

Quality

39%

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/superpowers-lab/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

33%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 boilerplate skeleton: three sections that each restate the frontmatter description in slightly different words, plus an external repository link. It provides zero actionable guidance and no workflow. Its only strengths are brevity and harmless, shallow structure.

Suggestions

Replace the circular Instructions section ('This skill provides guidance and patterns for...') with concrete, executable guidance: actual commands, code, or specific step-by-step directions for working in the lab environment.

Remove the triple repetition of the description across Overview, When to Use, and Instructions; each section should add distinct information (what it is / when to trigger it / how to use it).

Either inline the essential content from the source repository or add real bundle files (references/, scripts/) with clearly signaled one-level-deep links, so the skill delivers value without depending on an external URL.

DimensionReasoningScore

Conciseness

The body is very short with no over-explanation of concepts Claude already knows, but the same vague sentence ('lab environment for claude superpowers') is repeated across the Overview, When to Use, and Instructions sections — a minor redundancy that could be trimmed, matching anchor 4 rather than anchor 5's 'every token earns its place'.

4 / 5

Actionability

'This skill provides guidance and patterns for lab environment for claude superpowers' is pure abstraction — no code, commands, or concrete steps anywhere; the body only describes rather than instructs, exactly matching anchor 1 ('Entirely vague or abstract; no concrete code or commands; only describes rather than instructs').

1 / 5

Workflow Clarity

There are no steps or sequence of any kind, matching anchor 1 ('Steps missing or incoherent; no sequence'); the simple-skill exception does not apply because the single action is entirely ambiguous — the body never says what to actually do.

1 / 5

Progressive Disclosure

The body is under 50 lines, has no bundle files to organize, uses clearly headed sections, and its only reference (the source repository link) is well-signaled and one level deep — matching anchor 4 ('Good structure; most content is appropriately placed; references mostly clear'), falling short of anchor 5 because the body is a hollow shell with no real content to navigate.

4 / 5

Total

10

/

20

Passed

Description

16%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 a bare domain label with no stated capabilities, no trigger conditions, and no 'use when' guidance. It would rarely be selected for the right task and carries high conflict risk. It is marginally better than fully generic filler only because it names a specific project.

Suggestions

State 2-4 concrete capabilities in third person (e.g., what the lab environment actually lets the agent do: run experiments, test superpower prompts, sandbox plugins) instead of the noun phrase 'Lab environment for Claude superpowers'.

Append an explicit 'Use when...' clause with natural trigger phrases a user would actually say (e.g., 'Use when testing superpowers, running lab experiments, or sandboxing Claude plugins').

Include synonyms or specific tool/file terms (e.g., 'superpowers', 'lab', 'sandbox', relevant file extensions) so the skill is distinguishable from other environment-related skills.

DimensionReasoningScore

Specificity

The description 'Lab environment for Claude superpowers' names a domain but contains no action verbs whatsoever, matching the anchor 'Names the domain but actions are minimal or generic' rather than anchor 1 only because the domain itself is not entirely generic.

2 / 5

Completeness

The 'what' is extremely vague (a noun phrase with no capability statement) and the 'when' is entirely absent, matching anchor 1 ('Missing both what and when, or both are extremely vague'); the missing 'Use when...' clause also caps this dimension at 3.

1 / 5

Trigger Term Quality

The only keywords are 'lab', 'environment', and 'superpowers' — generic terms users would rarely say when needing this skill, matching the anchor 'One or two generic keywords; missing the natural phrases users say' rather than anchor 3, which requires a relevant keyword set.

2 / 5

Distinctiveness Conflict Risk

'Lab environment' is very broad with high overlap risk against many possible skills; only the project name 'superpowers' hints at a niche, matching anchor 2 ('Very broad; high overlap risk') rather than anchor 3 because no concrete distinguishing triggers are stated.

2 / 5

Total

7

/

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

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

skills/superpowers-lab/SKILL.md

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.