requirement-clarifier
v1.0.0需求澄清与分析技能。在实现任何需求前，先确保需求完整、清晰、无歧义。适用于需求开发、修改、分析、设计等场景。
⭐ 1· 119·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 and description match the runtime instructions: the skill's goal is to analyze and clarify requirements before implementation. It declares no binaries, env vars, or config paths, which is proportionate for a purely conversational/analysis skill.
Instruction Scope
SKILL.md asks the agent to 'analyze current project structure, existing code, business background' — this is reasonable for requirement clarification but is vague about data sources. In practice the agent will need project context provided by the user or by the execution environment; the instructions do not explicitly direct the agent to read specific system files or secrets, but the wording grants broad discretion to use any available project context.
Install Mechanism
No install spec and no code files (instruction-only). This is the lowest-risk installation footprint — nothing is written to disk or fetched at install time.
Credentials
The skill requests no environment variables, credentials, or config paths. There are no disproportionate or unexplained credential requests.
Persistence & Privilege
always is false and there are no special persistence requests. The skill may be invoked autonomously by the agent (platform default), but it does not request forced inclusion or system-wide configuration changes.
Assessment
This skill appears coherent and low-risk: it is a prompt/instruction template to clarify requirements and asks for no credentials or installs. Before installing, decide how the agent should obtain project context: if you do not want the agent to read repository files or environment data automatically, ensure the runtime environment enforces file-access policies or require the user to paste the relevant context. Consider whether you prefer explicit user invocation (disable autonomous invocation on the platform if possible) to avoid the skill activating whenever a development-related request is made. If you plan to use this on sensitive projects, require the user to provide only the minimal necessary excerpts (not full config or secrets) when requesting clarification.Like a lobster shell, security has layers — review code before you run it.
latestvk97d4jac8wsebvb29ppx1854e983g17g
License
MIT-0
Free to use, modify, and redistribute. No attribution required.