v2.0.0

Design Tool

ReviewClawScan verdict for this skill. Analyzed May 1, 2026, 7:41 AM.

Analysis

Review before installing: it is advertised as Penpot, but the artifacts implement a local command-line logging tool that stores whatever is entered under the user’s home directory.

GuidanceInstall only if you want a simple local command-line logger, not a Penpot integration. Verify the source because provenance is limited, and avoid entering passwords, tokens, or sensitive design information since entries are saved in local log files.

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.

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.

Human-Agent Trust Exploitation

SeverityMediumConfidenceHighStatusConcern

SKILL.md

name: Penpot
description: "Penpot: The open-source design tool for design and code collaboration..."
...
Design Tool v2.0.0 — a utility toolkit for logging, tracking, and managing design-related entries from the command line.

The same artifact brands the skill as Penpot while describing a generic local logging utility, which is a material mismatch from what a user would expect from a Penpot design tool integration.

User impactA user may install it expecting a Penpot-related design collaboration tool, but receive a local activity logger instead.

RecommendationClarify the name and description to accurately state that this is a local design-log CLI, or provide the missing Penpot integration if that is the intended purpose.

Agentic Supply Chain Vulnerabilities

SeverityLowConfidenceHighStatusNote

metadata

Source: unknown
Homepage: none
No install spec — this is an instruction-only skill.
Code file presence: scripts/script.sh

The package includes a script but has limited provenance and no installation specification, which is not inherently malicious but reduces clarity about source and setup.

User impactUsers have less information to confirm where the script came from or how it is meant to be installed.

RecommendationVerify the publisher/source before installing, and prefer packages with a clear homepage, source repository, and install instructions.

Sensitive data protection

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

Memory and Context Poisoning

SeverityLowConfidenceHighStatusNote

scripts/script.sh

DATA_DIR="${HOME}/.local/share/design-tool"
mkdir -p "$DATA_DIR"
...
echo "$ts|$input" >> "$DATA_DIR/run.log"
...
_log "run" "$input"

The script persistently stores user-provided text in local log files and history, which is expected for this tool but means sensitive notes would remain on disk.

User impactAnything entered into the tool can be stored locally and later shown through history, search, or export commands.

RecommendationDo not enter secrets or confidential design information unless local storage in this directory is acceptable; periodically review or delete the logs if needed.