test-driven-development
Write the failing test, then the code — so 'done' means a test passed, not that it looks done.
Examining code for the line that is wrong
What it can touch
No script files in its folder
Its folder holds text, not programs — but the instructions do tell your AI to run commands (see below).
How we know
Listed the 2 files in the skill’s folder on GitHub; none is a script or program.
Uses terminal commands
It shows your AI commands to run. In a coding agent that means your terminal; in a chat app it usually can’t.
How we know
The SKILL.md contains shell code blocks.
No known risk pattern found
Launch7’s automated check read all 2 text files in this skill and matched none of its risk patterns. This is not a guarantee: a check like this can miss new or disguised tricks, and the author can change the files after the check.
How we know
Read 2026-10-05, commit 8ca22db by pipeline/trust/analyze.py — 40+ patterns for hidden text, prompt injection, downloads that run, credential access and more. It reads; it never runs the skill.
Recently maintained
Its repository has had changes recently.
How we know
Last push to obra/superpowers: 2026-09-27 (8 days before the scan).
Read automatically from the skill’s own files on GitHub on 5 Oct 2026. Launch7 does not run or manually review skills: this lists what the check saw, and nothing here means “safe”. How we check
Add it to your AI
Supported. Upload it once in Claude’s settings. Works on every plan, including Free.
Built in your browser from the SKILL.md on GitHub — nothing passes through Launch7.
In Claude, open Customize → Skills, press +, then Create skill → Upload a skill, and choose the .zip.
Make sure code execution is switched on (Settings → Capabilities). Skills need it.
Start a new chat and ask for the job in your own words — Claude picks the skill up when it fits.
How Claude does this: support.claude.com · checked 28 Sep 2026 · “Supported” means documented by the vendor; Launch7 has not run it end to end
More from obra
All from this publisher →- using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback
- writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
- brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior.
- executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
- receiving-code-review
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind