Superpowers Brainstorming
v1.0.0Use before any creative work - creating features, building components, adding functionality, or modifying behavior - guides through exploration, questioning,...
⭐ 0· 551·5 current·5 all-time
by@axelhu
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name and description promise a guided brainstorming/design workflow; the SKILL.md only asks the agent to explore project files, ask clarifying questions, propose options, write a short design, run a self-review, get owner approval, commit the spec, and then call a dedicated 'writing-plans' skill. These actions are proportionate to the stated purpose.
Instruction Scope
Instructions legitimately direct the agent to inspect the current project state (files, docs, recent commits) and to write & commit a design document to docs/.... This is within scope, but it implies read/write access to the repository and the filesystem; the skill does not declare how git authentication or repository access is handled.
Install Mechanism
No install spec or code is provided (instruction-only), so nothing is written to disk or fetched during install. Low install risk.
Credentials
The skill declares no environment variables or credentials, which matches the simple brainstorming purpose. However, the requirement to commit to git implies the agent will need repository write permissions (or credentials) at runtime — these are not declared here. Also the skill calls another skill ('superpowers-writing-plans'), so you should confirm that that secondary skill's requirements are acceptable before chaining.
Persistence & Privilege
always is false and the skill does not request any special persistent privileges or modify other skills' settings. Autonomous invocation is enabled by default on the platform but that is normal and not excessive here.
Assessment
This skill appears to do what it says: guide a structured design and require owner approval before implementation. Before installing, confirm two runtime realities: (1) the agent will need permission to read the repo and to write/commit files — ensure the platform or agent has only the minimal git access you want to grant, and (2) check the 'superpowers-writing-plans' skill (which this skill will call) to verify its access and behavior. If you prefer explicit control, require manual commit steps or ensure human approval is enforced in your workflow rather than fully automated commits.Like a lobster shell, security has layers — review code before you run it.
latestvk97a41ms9vn830x91z4qcbcrn583mn1k
License
MIT-0
Free to use, modify, and redistribute. No attribution required.