smartart-extractor

Extract per-slide SmartArt data and validate specs against the smartart_spec schema.

3|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/SteveGJones/jack-tar-deckhand --skill smartart-extractor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: smartart-extractor
Source: https://github.com/SteveGJones/jack-tar-deckhand/tree/main/plugins/jack-tar-deckhand/skills/smartart-extractor
Command: npx skills add https://github.com/SteveGJones/jack-tar-deckhand --skill smartart-extractor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Transforms unstructured slide content into engine-ready SmartArt specifications, reducing manual data mapping and errors.

Core Features & Use Cases

  • Extract per-slide SmartArt data from SlideOutline body_points and approved recommendations.
  • Validate the generated specs against target engine schemas to ensure compatibility.
  • Use Case: A designer feeds in a deck with approved SmartArt slides and automatically receives a smartart-spec.json ready for rendering.

Quick Start

Run the extractor for each approved SmartArt slide to generate ./tmp/deck/smartart-spec.json

Frequently Asked Questions about smartart-extractor

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

FAQPage Schema
How do I extract structured data from slide content for SmartArt rendering?

To extract structured data for SmartArt rendering, run an automated extractor that parses SlideOutline body_points and approved recommendations to generate per-slide specifications. This process transforms unstructured slide content into engine-ready SmartArt specifications, reducing manual mapping and errors.

What is the process for validating SmartArt specs against target engine schemas?

Validating SmartArt specs involves checking the generated per-slide specifications against the smartart_spec schema. This ensures compatibility with the target rendering engine and prevents structural errors before the data is written to the output JSON file.

Do I need to classify slides with a strategy-map before generating SmartArt data?

Yes, you need to classify slides using a strategy-map to generate per-slide specs before extraction. The extractor is designed to apply its data extraction logic after a smartart-selector has produced approved slides and the strategy-map has classified them.

Can I automate deck SmartArt specifications without manual data mapping?

Yes, you can automate deck SmartArt specifications by feeding an approved deck into the extractor. It automatically processes the slide content and writes the validated, engine-ready SmartArt data directly to a smartart-spec.json file for rendering.

What are the limitations when extracting per-slide SmartArt data from slide outlines?

A key limitation is its strict prerequisite chain: the extractor only processes slides after a smartart-selector has approved them and a strategy-map has classified them. It cannot independently parse unapproved or unclassified slide content.