Deck Pipeline

PassAudited by ClawScan on May 12, 2026.

Overview

Deck Pipeline appears purpose-aligned and benign, but it can edit or overwrite local presentation/spreadsheet files and leave local handoff/glossary records.

Install only if you are comfortable letting it process and modify local deck files. Use copies for important presentations, verify output paths before writes, pin dependencies if possible, and review generated HANDOFF/Excel files for confidential content before sharing or reusing them.

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.

What this means

A deck or companion spreadsheet could be changed in place if the workflow is run on an original file.

Why it was flagged

The skill is designed to modify presentation and spreadsheet files, including documented default overwrite behavior. This is aligned with deck editing, and lock-file checks are disclosed, but users should consciously control backups and output paths.

Skill content
File-write discipline / 文件写入纪律
- Overwrite the original by default / 默认覆盖原文件
- Scan for `~$xxx` lock file before writing
Recommendation

Run it on a copy or confirm the output paths before allowing writes, and keep the page-by-page checkpoints enabled.

What this means

Different package versions could behave differently or introduce dependency risk.

Why it was flagged

The setup instructions rely on manually installed, unpinned third-party Python packages. This is expected for a local PPT/PDF/XLSX processing skill, but package versions and provenance are not locked by the skill artifacts.

Skill content
pip3 install python-pptx openpyxl pymupdf pyyaml
Recommendation

Install in a virtual environment and pin trusted package versions if using this for important or confidential decks.

What this means

Generated handoff or glossary files may contain sensitive project details and can steer future deck work.

Why it was flagged

The workflow intentionally writes a local handoff file and tracks glossary/rewrite decisions for later continuation. This is useful and disclosed, but it can persist project context and decisions across sessions.

Skill content
`HANDOFF.md` | Session contract: goal · tools · completed · unresolved · cautions · principles · constraints
Recommendation

Review HANDOFF.md, comparison spreadsheets, and glossary entries before sharing them or reusing them in a different project.