Back to skill
Skillv1.0.0

ClawScan security

Data Structure Protocol (DSP) · ClawHub's context-aware review of the artifact, metadata, and declared behavior.

Scanner verdict

BenignMar 14, 2026, 12:30 PM
Verdict
benign
Confidence
high
Model
gpt-5-mini
Summary
The skill's code and instructions align with its stated purpose (building and managing a .dsp project graph), require no external credentials or installs, and only read/write repository-local .dsp files.
Guidance
This skill appears to do what it says: it creates and updates a .dsp/ graph inside the repo and does not contact external services or require secrets. Before installing or using it, (1) review and back up your repository (or run in a sandbox) since the agent will create/modify .dsp/ files in-place, (2) verify you are comfortable with an autonomous agent modifying project metadata, and (3) if you want stricter controls, run dsp-cli manually rather than allowing autonomous invocation so you can review changes before committing them.

Review Dimensions

Purpose & Capability
okThe name/description (graph-based memory for codebases) matches the provided CLI and docs. The script implements UID generation, TOC management, imports/exports bookkeeping and bootstrap traversal — all expected for this functionality. No unrelated credentials or binaries are requested.
Instruction Scope
okSKILL.md instructs the agent to run the local dsp-cli and to read/update the .dsp directory and project files; those actions are appropriate for maintaining a structural memory. The instructions do not direct the agent to read unrelated system files, environment secrets, or to transmit data externally. (Minor doc quirk: examples include an invalid hex character in a UID example, but this is non-security.)
Install Mechanism
okThere is no install spec; the skill is instruction-only plus a local Python CLI script. No remote downloads, package installs, or external taps are used.
Credentials
okThe skill declares no required environment variables, credentials, or config paths. The CLI operates on repository-relative paths and writes only into .dsp under the project root, which is proportionate to the stated goal.
Persistence & Privilege
notealways:false (normal). The CLI writes persistent state into the repository's .dsp directory and can be invoked by the agent autonomously. This is expected for a tool that maintains project memory, but users should be aware the agent can modify .dsp files when invoking the skill.