Back to skill
Skillv1.0.0
ClawScan security
Marp Slide Show/Deck Generator · ClawHub's context-aware review of the artifact, metadata, and declared behavior.
Scanner verdict
BenignApr 28, 2026, 7:20 PM
- Verdict
- benign
- Confidence
- high
- Model
- gpt-5-mini
- Summary
- The skill's requirements and instructions match its stated purpose: it builds Marp markdown slides and renders them with the marp CLI; nothing in the SKILL.md asks for unrelated credentials or system access.
- Guidance
- This skill appears coherent and focused: it builds Marp markdown and runs the marp CLI to render outputs. Before installing, confirm you trust the npm package @marp-team/marp-cli and the registry version you will install (supply-chain risk is the main technical concern). Be aware the skill will run a local binary and write output files to the agent's working directory, so avoid sending highly sensitive secrets or private credentials into slide content you don't want stored. If you prefer to limit risk, install the marp CLI yourself ahead of time (or review the package source) and only then enable the skill. If you do not want the agent to invoke skills autonomously, adjust agent settings to require manual invocation.
Review Dimensions
- Purpose & Capability
- okThe skill is a Marp slide generator and declares the marp binary as required. The install spec installs @marp-team/marp-cli (which provides the marp binary). Requested binaries and the workflow (create .slides.md, run marp CLI to render) are appropriate and proportional to the described purpose.
- Instruction Scope
- okSKILL.md stays on-topic: it explains how to classify inputs, author Marp markdown, and invoke marp to render outputs. It does not instruct the agent to read unrelated system files, exfiltrate data, or contact unexpected endpoints. Verification steps (render-checking) are reasonable, though they assume the agent can access generated files.
- Install Mechanism
- noteThe install uses an npm package (@marp-team/marp-cli) which is a standard way to get the marp CLI. Installing from the public npm registry is expected but carries the usual supply-chain considerations (verify package provenance, version). No arbitrary download URLs or extract-from-unknown-host operations are used.
- Credentials
- okNo environment variables, credentials, or config paths are required. The skill does not request unrelated secrets or broad environment access — which is appropriate for a local rendering tool.
- Persistence & Privilege
- okThe skill is not always-enabled and does not request elevated or persistent system-wide privileges. It will invoke the marp binary and produce files in the working directory; autonomy (model invocation) is the platform default and is not by itself a concern here.