Presentation source intake
Skill samulee003/agentic-ppt-skills/skills/presentation-source-intake
Agent skills that route a presentation from source to stage-ready through an 8-gate pipeline. Extracted from open-slide.
npx -y skills add samulee003/agentic-ppt-skills --skill presentation-source-intakeAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Inventories presentation source folders, classifies materials, identifies authoritative versions, and records conflicts or missing access before deck work starts. Use when the source-intake gate is current for a presentation project or when a router asks for a source inventory.
SKILL.md
1.6 KB, as published. Nobody here has run it
Build the source inventory
Use when source-intake is the current gate.
- Read repo instructions and nearby handoff docs first.
- Keep the source folder read-only. Create working notes only in the presentation work area.
- Read existing deck, source, and work artifacts before creating new ones.
- Inspect file contents with structured tools appropriate to each type: PDF, PPTX, DOCX, spreadsheet, image, script, note, and export.
- Classify every relevant item by role, recency, and reuse value instead of copying folders into the work area.
- Identify version lineage: draft, revision, export, derivative, duplicate, and latest known source.
- Mark the most authoritative source for each topic, chart, claim set, and visual asset.
- Record reusable assets that can move forward without rework.
- Record stale materials that should not drive current decisions.
- Record conflicts, missing files, and access blockers explicitly.
Write SOURCE-INVENTORY.md from templates/SOURCE-INVENTORY.md.
- Fill every section with concrete paths, dates when visible, and short evidence notes.
- Prefer exact filenames over vague summaries.
- If discoverable answers exist in the files, find them before asking the user.
- Stop after the inventory is complete enough for product grilling to begin.