ppt-info-pack

Aggregate user inputs, uploads, and research into a traceable JSON info-pack.

8|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/SenseTime-FVG/sensenova-claw --skill ppt-info-pack
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ppt-info-pack
Source: https://github.com/SenseTime-FVG/sensenova-claw/tree/main/.sensenova-claw/skills/ppt-info-pack
Command: npx skills add https://github.com/SenseTime-FVG/sensenova-claw --skill ppt-info-pack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill consolidates scattered user input, uploaded materials, and research outputs into a single, traceable JSON information source for presentation storyboarding, eliminating ad-hoc lookups and inconsistent data during slide creation.

Core Features & Use Cases

  • Aggregates task-pack.json, optional source-map.json, optional research-pack.json and uploaded materials into a normalized info-pack.json containing stable InfoAtom entries with atom_id, source tracing, and confidence metadata.
  • Structures chart data, metrics, titles, captions, and other visible elements into explicit payloads so downstream storyboard and page rendering can reference atoms reliably; records known_gaps or unresolved_atoms when data is missing.
  • Use case: prepare a deck's unified content pool before layout so designers and automated storyboard steps only consume the verified info-pack.json and avoid re-parsing original uploads or research outputs.

Quick Start

Run the ppt-info-pack step to read task-pack.json and any available uploads or research, then emit info-pack.json in the deck directory containing stable InfoAtom records and gap markers.

Frequently Asked Questions about ppt-info-pack

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I consolidate scattered research and uploads into traceable data for presentation storyboarding?

To consolidate scattered inputs for presentation storyboarding, aggregate user text, uploaded files, and research outputs into a single normalized JSON info-pack containing stable InfoAtom records with source tracing and confidence metadata.

What is an InfoAtom record and how does it help pre-layout slide rendering?

An InfoAtom record is a structured data entry within the info-pack that contains a stable atom_id, source_type, and source_ref tracing. It helps pre-layout slide rendering by providing explicit payloads for charts, metrics, and titles so downstream steps reference verified data reliably.

How do I handle missing data or incomplete research when structuring presentation content?

When structuring presentation content with missing data, the aggregation process records known_gaps and unresolved_atoms explicitly within the JSON info-pack, allowing downstream storyboard and page rendering steps to identify incomplete information without re-parsing original uploads.

Can I use uploaded files and research outputs together to prepare a unified content pool for deck generation?

Yes, you can aggregate task-pack.json, optional source-map.json, optional research-pack.json, and uploaded materials together into a normalized info-pack.json, creating a unified content pool that designers and automated rendering steps consume without parsing original sources.

Best way to structure chart data and metrics before laying out a presentation deck?

The best way to structure chart data and metrics before layout is to aggregate them into explicit structured payloads within an info-pack.json, assigning each element a stable atom_id and confidence metadata so storyboard rendering can reference the atoms reliably.

Why does my presentation storyboard have inconsistent data across slides?

Inconsistent data across slides occurs when storyboard steps parse original uploads independently; consolidating all inputs into a single traceable JSON info-pack with stable InfoAtom records eliminates ad-hoc lookups and ensures downstream rendering consumes verified, uniform data.