ppt-source-analysis

Classify uploaded inputs into content, style, template, or mixed sources.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill identifies the role and value of each user-provided input (files, links, screenshots, templates, or existing decks) so downstream PPT workflows can decide whether to research content, apply style guidance, or reuse a template.

Core Features & Use Cases

  • Per-input role classification: Labels each artifact as content_source, style_reference, template_reference, or mixed_source.
  • Value and limitation analysis: Records strengths, limitations, and ambiguity for each input to surface risks and guide routing.
  • Downstream routing: Produces a consumable source-map.json that recommends the appropriate next skills such as ppt-task-pack, ppt-research-pack, ppt-template-pack, and ppt-style-spec.
  • Use Case: When a user uploads a research report, a brand screenshot, and an existing deck, the Skill will produce a source-map.json that marks the report as content_source, the screenshot as style_reference, and the deck as mixed_source with recommended next steps.

Quick Start

Use the skill to analyze the uploaded files and generate a source-map.json that classifies each input and recommends next skills.

Frequently Asked Questions about ppt-source-analysis

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

FAQPage Schema
How do I classify uploaded files into content sources and style references for PPT generation?

Classify uploaded files by analyzing their roles to identify each as a content_source, style_reference, template_reference, or mixed_source. The analysis produces a source-map.json that labels each artifact to guide downstream PPT workflows and skill routing.

What is the best way to analyze mixed source presentations and screenshots before building a deck?

Analyzing mixed source presentations involves evaluating each input's strengths, limitations, and ambiguity. The process generates a source-map.json that flags unreadable or ambiguous inputs and records per-item summaries to route artifacts correctly.

Can I use existing presentations and webpages as both content and template references?

Existing presentations and webpages can be evaluated as mixed_source inputs. The analysis identifies multiple roles within a single artifact and outputs a source-map.json that recommends appropriate next skills based on the extracted content and template value.

How do I route a research report and brand screenshot to the correct PPT workflow skills?

Route artifacts by generating a source-map.json that recommends downstream skills like ppt-task-pack, ppt-research-pack, ppt-template-pack, and ppt-style-spec. The report is marked as content_source and the screenshot as style_reference to guide the workflow.

What are the limitations of source analysis when handling ambiguous user uploads?

Source analysis limitations include flagging unreadable or ambiguous inputs within the source-map.json. The process records specific limitations for each artifact to surface risks, ensuring downstream PPT workflows handle uncertain or mixed_source data appropriately.