CtrlK
BlogDocsLog inGet started
Tessl Logo

superpowers-lab

Lab environment for Claude superpowers

20

Quality

9%

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/skills/superpowers-lab/SKILL.md

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

SKILL.md
Quality
Evals
Security

Quality

Content

18%Scale 1-5

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

This skill is essentially a placeholder with no substantive content. It repeats its own description three times and provides no actionable instructions, concrete examples, workflows, or meaningful references. It would be entirely unhelpful to Claude in performing any task.

Suggestions

Define what 'superpowers' the lab environment provides and add concrete instructions for each capability (e.g., specific commands, code snippets, or tool usage patterns).

Add at least one executable example showing how to use the lab environment for a common task.

Remove the redundant 'When to Use This Skill' and 'Instructions' sections that merely restate the overview, and replace them with actual step-by-step guidance.

If the skill depends on the source repository, document the key workflows and patterns inline rather than deferring entirely to an external link.

DimensionReasoningScore

Conciseness

The content is short but almost entirely filler. It repeats the same phrase ('lab environment for claude superpowers') three times across the overview, 'when to use' section, and instructions, adding no real information. While not verbose in absolute terms, every token is wasted because none provide actionable content.

3 / 5

Actionability

There is zero concrete guidance—no code, no commands, no specific steps, no examples. The entire 'Instructions' section is a single vague sentence restating the description plus a link to a repository. Claude would have no idea what to actually do.

1 / 5

Workflow Clarity

There are no steps, no sequence, no validation, and no workflow of any kind. The skill provides no process to follow.

1 / 5

Progressive Disclosure

There is a link to an external repository, but no bundle files, no referenced paths, and no structured navigation. The sections exist but contain no meaningful content to organize. The reference to the source repo is the only navigation aid, but it provides no context about what can be found there.

2 / 5

Total

7

/

20

Passed

Description

0%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.

This description is extremely vague and provides no actionable information for skill selection. It lacks concrete actions, natural trigger terms, any 'when to use' guidance, and any distinguishing characteristics. It would be essentially unusable in a multi-skill selection context.

Suggestions

Replace the abstract phrase 'Claude superpowers' with specific, concrete actions the skill enables (e.g., 'Runs code experiments, tests API integrations, and prototypes solutions in a sandboxed environment').

Add an explicit 'Use when...' clause with natural trigger terms that describe scenarios where this skill should be selected (e.g., 'Use when the user wants to experiment, prototype, or test code in an isolated environment').

Define the skill's domain clearly to distinguish it from other skills — what specific type of 'lab environment' is this, and what makes it different from general coding or testing skills?

DimensionReasoningScore

Specificity

The description is entirely vague with no concrete actions. 'Lab environment for Claude superpowers' describes nothing specific about what the skill does — no domain, no actions, no outputs.

1 / 5

Completeness

Both 'what' and 'when' are missing. The description does not explain what the skill does or when Claude should select it. There is no 'Use when...' clause or any equivalent guidance.

1 / 5

Trigger Term Quality

There are no natural keywords a user would say. 'Lab environment' and 'superpowers' are not terms users would use when requesting a task. No actionable or domain-specific trigger terms are present.

1 / 5

Distinctiveness Conflict Risk

The description is entirely generic and could apply to virtually anything. 'Claude superpowers' provides no distinguishing information that would differentiate this skill from any other.

1 / 5

Total

4

/

20

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

10

/

11

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.