测试2123
v1.0.0在任何创造性工作之前必须使用 - 创建功能、构建组件、添加新功能或修改行为。通过协作对话探索用户意图、需求和设计。
⭐ 0· 91·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description describe collaborative brainstorming and turning ideas into designs. The SKILL.md's actions (ask questions, propose options, produce design writeups) match that purpose. It also instructs the agent to inspect project files, docs, and recent commits and to write docs and commit them to git — these follow from the purpose but imply repository/file read/write and git privileges that are not explicitly declared.
Instruction Scope
Instructions stay within design/brainstorming scope. They explicitly tell the agent to 'first view current project status (files, documentation, recent commits)', create docs under docs/plans/..., and commit the design doc to git. Those file-system and git actions are relevant to the skill but are broader than a pure conversational helper — the instructions are precise about outputs but leave implementation (how to read/commit) unspecified.
Install Mechanism
No install spec or code files are included (instruction-only), so nothing is written to disk or downloaded by an installer. This is the lowest-risk install profile.
Credentials
The skill declares no required environment variables or credentials. However, its runtime instructions implicitly require access to the workspace/repository and ability to create and commit files via git (or equivalent). That implicit need is proportional to the purpose but should be acknowledged: enabling the skill effectively grants repository read/write rights to whatever agent/tool executes it.
Persistence & Privilege
always:false and normal agent invocation are used. The skill does not request persistent presence or attempt to modify other skills or global agent settings. It does reference required/recommended sub-skills, which is normal.
Assessment
This skill appears to do what it says: guide brainstorming, propose design options, and produce/commit design docs. Before enabling it, confirm the execution environment (the agent) should have read access to your project files and permission to write and commit to the repository. If you are uncomfortable with automatic commits, require manual review of generated docs or run the skill in a sandbox/copy of the repo. Also verify any referenced sub-skills (e.g., core-writing-plans) before granting broader access, and ensure no secrets are present in the repo files the agent will read.Like a lobster shell, security has layers — review code before you run it.
latestvk9706jeykqb3pzbm8d5fx0h2mn84g78r
License
MIT-0
Free to use, modify, and redistribute. No attribution required.