Artifact Deck

Public OpenClaw skill for generating reproducible PPTX decks from project notes, status bullets, and screenshots. Use when the user wants a stakeholder-ready...

Security Scan

The skill's code, runtime instructions, and requested resources are consistent with its stated purpose of building local PPTX decks from repo-local notes and screenshots.

Purpose & Capability

Name/description ask for turning local notes/screenshots into a reproducible .pptx; the scripts only read local markdown/image files, build a PPTX via python-pptx, and emit JSON/markdown summaries. No unrelated services, credentials, or binaries are requested.

Instruction Scope

SKILL.md instructs the user/agent to validate inputs, install python-pptx, and run the provided scripts. The scripts only access manifest, markdown and image paths the user supplies and write local outputs; they do not access external networks, other env vars, or system config.

Install Mechanism

There is no install spec in the registry (instruction-only). SKILL.md recommends installing python-pptx via pip, which is an expected, minimal dependency for generating PPTX files. No downloads from untrusted URLs or archive extraction occur.

Credentials

The skill requires only Python on PATH (python3/python) and a local python-pptx package; no credentials, tokens, or config paths are requested. The scripts only read file paths provided in the manifest.

Persistence & Privilege

always is false and the skill is user-invocable. The skill does not attempt to modify other skills or system-wide agent settings; it only writes its own output files (manifest/build/summary).

Assessment

This skill appears to do exactly what it says: read local markdown and image files, validate them, and produce a reproducible .pptx using python-pptx. Before installing/running: (1) ensure you run it in an environment you control and that you trust the manifest and image paths (the scripts will read any files the manifest points to); (2) install python-pptx in an isolated venv if you prefer; (3) review or run the scripts on sample data to confirm behavior; (4) note a minor doc/path inconsistency in the summary's rebuild command (it references 'skill/artifact-deck/scripts/...' while the packaged scripts are under scripts/), but this is a documentation nit, not a security issue. If you need higher assurance, review the GitHub repo contents or run the tooling in a sandboxed/container environment.

Goal

Turn curated project notes and screenshots into a clean, reproducible .pptx deck:

• one manifest that defines the deck title, subtitle, status slides, and optional appendix images
• one input check before build
• one local PPTX build
• one share-safe markdown summary with a rebuild command template and slide list

This skill is for deterministic stakeholder packaging, not autonomous research or design generation. It requires Python 3.9+ and python-pptx.

Use This Skill When

• release notes, weekly updates, or launch artifacts need to become a decision-ready deck
• browser screenshots or diagrams should be included as appendix slides
• the user wants a rebuildable .pptx instead of a one-off manual slide edit
• you need a concise executive or client status deck from repo-local notes

Quick Start

1. Initialize the manifest.

   • Install the dependency once in the environment: python3 -m pip install python-pptx.
   • Use python3 {baseDir}/scripts/init_artifact_deck_manifest.py --title <title> --subtitle <subtitle> --section "What Changed=/abs/path/changes.md" --out <manifest.json>.
   • Repeat --section for more markdown-backed status slides.
   • Optional: repeat --slide "Risks=Pending scan|Need approval" for direct bullet slides.
   • Optional: repeat --image "Browser Proof=/abs/path/screenshot.png|Upload flow after publish" for appendix slides.

2. Validate the inputs.

   • Use python3 {baseDir}/scripts/check_artifact_deck_inputs.py --manifest <manifest.json> --out <check.json>.
   • Fix missing content or image-path errors before building.

3. Build the deck.

   • Use python3 {baseDir}/scripts/build_artifact_deck.py --manifest <manifest.json> --deck-out <deck.pptx> --out <build.json>.
   • This writes the .pptx and a small JSON build summary.

4. Render the summary.

   • Use python3 {baseDir}/scripts/render_artifact_deck_summary.py --manifest <manifest.json> --check <check.json> --build <build.json> --out <summary.md>.
   • Share the deck and the summary together; the summary omits absolute local paths and keeps only a rebuild command template.

Operating Rules

Scope rules

• Keep the promise narrow: curated notes and screenshots in, reproducible .pptx out.
• Prefer concise bullets. Six bullets per slide is a practical ceiling.
• Treat missing or mistyped file paths as hard failures.

Deck rules

• Use a title slide plus focused status slides.
• Put screenshots and diagrams in appendix slides unless the user explicitly wants them inline.
• Keep slide titles explicit: What Changed, Risks, Asks, Appendix, or equivalent.

Bundled Scripts

• scripts/init_artifact_deck_manifest.py
  • Build a manifest from markdown sections, direct bullet slides, and optional image appendix entries.
• scripts/check_artifact_deck_inputs.py
  • Validate manifest structure, bullet availability, and image paths.
• scripts/build_artifact_deck.py
  • Generate the .pptx and a machine-readable build summary.
• scripts/render_artifact_deck_summary.py
  • Render a concise markdown summary with the deck filename, slide count, and a rebuild command template.