Code Formatter

PassAudited by ClawScan on May 17, 2026.

Overview

This is a coherent instruction-only code-formatting guide; its examples may install standard developer tools or modify selected project files, but no hidden or unrelated behavior is shown.

This skill appears safe as a formatting reference. Before running its commands, confirm the target files or directories, review changes after write/fix operations, and install formatter packages only from sources you trust.

Findings (2)

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.

Low

#ASI02: Tool Misuse and Exploitation

What this means

Running the listed commands can change code formatting across files or directories.

Why it was flagged

These are purpose-aligned formatting examples, but the --write, --fix, and -w options can modify local project files if a user or agent runs them.

Skill content

npx prettier --write src/ ... ruff check --fix file.py ... shfmt -w script.sh

Recommendation

Run formatters only on intended files or directories and review the resulting diff before committing changes.

Low

#ASI04: Agentic Supply Chain Vulnerabilities

What this means

Installing formatter packages adds third-party code to the user’s development environment.

Why it was flagged

The guide references installing third-party formatter and linter packages. This is expected for a formatting guide, but following the examples downloads external development tools.

Skill content

pip install black ... npm install -D prettier ... repo: https://github.com/psf/black

Recommendation

Use trusted package sources, consider pinning versions where appropriate, and install only the tools needed for the project.