Back to skill
Skillv1.0.0
ClawScan security
测试审核记录保存4 · ClawHub's context-aware review of the artifact, metadata, and declared behavior.
Scanner verdict
BenignApr 23, 2026, 9:23 AM
- Verdict
- benign
- Confidence
- high
- Model
- gpt-5-mini
- Summary
- This is an instruction-only brainstorming/design skill that is internally consistent: it asks the agent to inspect project context, produce design text, and (optionally) write a design file and commit it to git — nothing in the skill requests unrelated credentials or installs.
- Guidance
- This skill is an instruction-only brainstorming helper and appears coherent, but note two practical points before installing: - The SKILL.md asks the agent to inspect the current project (files, docs, recent commits). If you install this, ensure the agent runtime has only the repository and filesystem access you intend to expose — it will read project files to form context. - The skill also directs writing validated design docs to docs/plans/... and committing them to git. Committing uses whatever git credentials/config are present in the runtime. If you don't want automatic commits, restrict the agent's write or git access or confirm changes before committing. Also review any referenced sub-skills (core-writing-plans, embedded-* etc.) before allowing the agent to invoke them, and consider testing the skill in a sandboxed repository first.
Review Dimensions
- Purpose & Capability
- okThe name and description describe a collaborative brainstorming/design helper; the SKILL.md content matches that purpose (questions to understand intent, propose options, produce 200–300 word design sections). There are no unrelated dependencies or requested credentials.
- Instruction Scope
- noteThe instructions explicitly tell the agent to '查看当前项目状态（文件、文档、最近提交）' and to write validated designs to docs/plans/... and commit them to git. Asking to read the repository and commit files is coherent for this skill, but it implies the agent will access project files and perform write/git actions — verify you want the agent to have that filesystem/repo access.
- Install Mechanism
- okNo install spec and no code files: lowest-risk model. The skill is instruction-only and does not pull external binaries or archives.
- Credentials
- okThe skill declares no environment variables or credentials. This is proportional to a purely instructional skill; however, practical execution (committing to git) will rely on the agent runtime having git and the user's existing repo credentials configured — those are not requested by the skill itself.
- Persistence & Privilege
- okalways is false and the skill is user-invocable. It does not request permanent presence or attempt to modify other skills or global agent settings.