Brainstorm Beagle
v1.0.1Use when the user has a fuzzy idea and wants to shape it into a concrete project spec before planning or building. Triggers on: "brainstorm this", "I have an...
⭐ 0· 69·1 current·1 all-time
byKevin Anderson@anderskev
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name, description, and included files (SKILL.md + spec templates/checklist) align with the stated goal of producing WHAT/WHY spec documents; there are no unrelated dependencies or credential requests.
Instruction Scope
Runtime instructions explicitly tell the agent to read project files, docs, and git history for context and to write the final spec to docs/specs/YYYY-MM-DD-<topic>.md. That behavior is coherent with the purpose, but it implies the agent will access repository files and write to the workspace — users should be aware of file reads and potential file writes.
Install Mechanism
No install spec or code is included; this is instruction-only so nothing is downloaded or written to disk by an installer.
Credentials
No environment variables, credentials, or external config paths are requested; required scope matches the described functionality.
Persistence & Privilege
The skill will write a spec document to the workspace as its terminal state, but the workflow requires user review/approval before writing. always:false and no system-wide config changes are requested.
Assessment
This is an instruction-only brainstorming/spec-writing skill and appears internally consistent. Before enabling or invoking it, be aware it will ask to read your project files and git history for context and — after you approve the drafted spec — save the spec to docs/specs/.... If those files contain sensitive data you do not want accessed, don't grant file access. Consider: (1) running it in a copy of the repo or a restricted workspace, (2) confirming the agent prompts you for approval before any write, and (3) backing up any existing docs/specs files to avoid accidental overwrite. No network installs or secrets are required by the skill itself.Like a lobster shell, security has layers — review code before you run it.
latestvk97ffww4y2mm1pebre3h497yh184px64
License
MIT-0
Free to use, modify, and redistribute. No attribution required.