Brainstorming Pro
v1.0.0Facilitates structured ideation sessions for features, products, content, and strategy. Use when: (1) planning new features, (2) exploring product directions...
⭐ 0· 119·0 current·0 all-time
byAlexander Schneider@arn0ld87
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 assets (templates, facilitation scripts, metrics, follow-up checklists) align with a brainstorming/facilitation skill. There are no unexpected required binaries, environment variables, or install steps that would be disproportionate to facilitation tasks.
Instruction Scope
SKILL.md is detailed and stays within facilitation scope (goal clarification, divergent/convergent phases, templates, scripts). It does instruct the agent to "check out the current project state first (files, docs, recent commits)" and to integrate outputs with tools (Slack/Jira/Email/Dashboards). These are reasonable for contextual ideation and handoff, but they imply reading repository/files and interacting with external services — actions that depend on the agent's granted access and are not explicitly declared in requires.env or required config paths.
Install Mechanism
No install spec and no code files to execute. Instruction-only skills are lower-risk because nothing is written to disk or fetched at install time.
Credentials
The skill requests no environment variables or credentials, which is appropriate. However, the instructions reference posting to Slack/Teams/Jira and sending emails or dashboard updates; those integrations would require credentials if automated. The lack of declared credential requirements is consistent with a guidance/template skill but means the agent would need explicit separate permissions or other skills to perform such integrations.
Persistence & Privilege
always is false and the skill is user-invocable; it does not request permanent presence or elevated privileges. There is no evidence it modifies other skills or system-wide settings.
Assessment
This skill appears coherent and is mostly a collection of facilitation templates and runtime instructions. Before installing or allowing autonomous use, consider: (1) The skill suggests the agent 'check project files, docs, recent commits' — ensure you are comfortable granting the agent read access to any repositories or files it might use. (2) Handoff steps reference Slack/Jira/Email/Dashboard integrations — those actions require separate credentials and explicit permission; the skill itself does not request them. (3) Because the source and homepage are unknown, review the included templates (they are bundled here) and confirm they meet your privacy and compliance needs. If you want to limit risk, keep this skill user-invocable only (no autonomous runs) and deny or carefully scope any filesystem or token access the agent might request during use.Like a lobster shell, security has layers — review code before you run it.
latestvk977q3gbv74k1z29h1xtzvmarx83h31t
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
