Context Builder
Analysis
This is a coherent code-context generation skill, but it can read and save large parts of a project, including embedded secrets, so users should scope it carefully.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.
context-builder -d /path/to/project -y -o context.md ... `-y` skips confirmation prompts (recommended for agent workflows when path is explicitly scoped)
The documented workflow allows prompt-free generation of context files, which is appropriate for automation but relies on the path being explicitly scoped.
cargo install context-builder --features tree-sitter-all ... Verify: `context-builder --version` (expected: `0.8.3`)
The skill depends on installing an external CLI rather than including code in the artifact; the install command is user-directed and purpose-aligned, but users should verify provenance and version.
Checks for exposed credentials, poisoned memory or context, unclear communication boundaries, or sensitive data that could leave the user's control.
This tool reads file contents from the specified directory... The output may contain API keys, secrets, or credentials embedded in source files; always review
The skill is explicitly designed to read local project files and produce LLM-consumable context; the artifact itself acknowledges that secrets may be included.
