v1.1.0

Mini PIV - Lightweight Feature Builder

ReviewClawScan verdict for this skill. Analyzed May 1, 2026, 5:26 AM.

Analysis

This is a coherent feature-building workflow, but it gives sub-agents broad code-editing and command-running authority and can stage and commit repository changes.

GuidanceBefore installing or using this skill, treat it like a powerful coding agent: run it only in a clean branch or disposable worktree, limit PROJECT_PATH to the intended repository, inspect commands and diffs before approval, and review any generated PRP files before they are committed.

Findings (5)

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.

Abnormal behavior control

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.

Tool Misuse and Exploitation

SeverityMediumConfidenceHighStatusConcern

references/piv-executor.md

Use the available tools (read, write, edit, exec) to implement changes and run commands

The executor sub-agent is authorized to modify project files and execute commands based on the generated PRP, without a clearly bounded file scope, command allowlist, or approval gate in the artifact.

User impactA run could make broad changes to the local codebase and execute project commands or scripts with side effects.

RecommendationUse only in a clean branch or worktree, review the plan and diff before allowing edits, and require explicit confirmation before running commands or making broad changes.

Cascading Failures

SeverityMediumConfidenceHighStatusConcern

SKILL.md

cd PROJECT_PATH && git status && git diff --stat
git add -A
git commit -m "feat(

The commit step stages all repository changes with git add -A before committing, which can include unrelated, generated, deleted, or unreviewed files.

User impactUnintended changes or generated planning files could be captured in a commit and later propagated if the user pushes it.

RecommendationReview the full git diff before committing, prefer path-scoped git add commands, and require explicit user approval before any commit.

Unexpected Code Execution

SeverityLowConfidenceHighStatusNote

references/execute-prp.md

Run syntax & style validation commands ... Execute unit test validation ... Run integration testing commands

Running validation commands is expected for a coding workflow, but project test/build/lint commands can execute local scripts or start services.

User impactUsing this on an untrusted repository could run that repository's scripts during validation.

RecommendationRun it only on repositories you trust, inspect validation commands first, and use an isolated branch or environment for unfamiliar projects.

Sensitive data protection

Checks for exposed credentials, poisoned memory or context, unclear communication boundaries, or sensitive data that could leave the user's control.

Insecure Inter-Agent Communication

SeverityLowConfidenceHighStatusNote

SKILL.md

Use the `sessions_spawn` tool to create fresh sub-agent sessions. Each spawn is non-blocking — you'll receive results via an announce step.

The workflow intentionally passes project paths, discovery input, PRPs, summaries, and validation gaps among multiple spawned agents; this is purpose-aligned but expands who sees the task context.

User impactMultiple agent sessions may access project context and generated implementation details.

RecommendationUse the skill only with project paths appropriate for spawned agents and understand the platform's sub-agent permission boundaries.

Memory and Context Poisoning

SeverityLowConfidenceHighStatusNote

SKILL.md

Save to: {PROJECT_PATH}/PRPs/planning/mini-{FEATURE_NAME}-analysis.md

The skill stores codebase-derived analysis and PRP context inside the project for later use by executor and validator agents.

User impactGenerated planning files may contain project structure, implementation notes, or other internal context and may remain in the repository.

RecommendationReview generated PRP and analysis files before committing them, and add them to .gitignore or delete them if they should not persist.