ppt-master

Name: ppt-master
Author: OpsinTech

91stars18forks

How to install ppt-master?

opsintech/opsintech-platform/ppt-master

$npx -y skills add OpsinTech/opsintech-platform --skill ppt-master

Installs into the current project.

Summary

AI-driven multi-format SVG content generation system. Converts source documents (PDF/DOCX/URL/Markdown) into high-quality SVG pages and exports to PPTX through multi-role collaboration. Use when user asks to "create PPT", "make presentation", "生成PPT", "做PPT", "制作演示文稿", or mention

Files · 1

View on GitHub

SKILL.md

1	# PPT Master Skill
2
3	> AI-driven multi-format SVG content generation system. Converts source documents into high-quality SVG pages through multi-role collaboration and exports to PPTX.
4
5	Core Pipeline: `Source Document → Create Project → [Template] → Strategist → [Image_Generator] → Executor Live Preview → Quality Check → Post-processing → Export`
6
7	> [!CAUTION]
8	> ## 🚨 Global Execution Discipline (MANDATORY)
9	>
10	> This workflow is a strict serial pipeline. The following rules have the highest priority — violating any one of them constitutes execution failure:
11	>
12	> 1. SERIAL EXECUTION — Steps MUST be executed in order; the output of each step is the input for the next. Non-BLOCKING adjacent steps may proceed continuously once prerequisites are met, without waiting for the user to say "continue"
13	> 2. BLOCKING = HARD STOP — Steps marked ⛔ BLOCKING require a full stop; the AI MUST wait for an explicit user response before proceeding and MUST NOT make any decisions on behalf of the user
14	> 3. NO CROSS-PHASE BUNDLING — Cross-phase bundling is FORBIDDEN. (Note: the Eight Confirmations in Step 4 are ⛔ BLOCKING — the AI MUST present recommendations and wait for explicit user confirmation before proceeding. Once the user confirms, all subsequent non-BLOCKING steps — design spec output, SVG generation, speaker notes, and post-processing — may proceed automatically without further user confirmation)
15	> 4. GATE BEFORE ENTRY — Each Step has prerequisites (🚧 GATE) listed at the top; these MUST be verified before starting that Step
16	> 5. NO SPECULATIVE EXECUTION — "Pre-preparing" content for subsequent Steps is FORBIDDEN (e.g., writing SVG code during the Strategist phase)
17	> 6. NO SUB-AGENT SVG GENERATION — Executor Step 6 SVG generation is context-dependent and MUST be completed by the current main agent end-to-end. Delegating page SVG generation to sub-agents is FORBIDDEN
18	> 7. SEQUENTIAL PAGE GENERATION ONLY — In Executor Step 6, after the global design context is confirmed, SVG pages MUST be generated sequentially page by page in one continuous pass. Grouped page batches (for example, 5 pages at a time) are FORBIDDEN
19	> 8. SPEC_LOCK RE-READ PER PAGE — Before generating each SVG page, Executor MUST `read_file <project_path>/spec_lock.md`. All colors / fonts / icons / images MUST come from this file — no values from memory or invented on the fly. Executor MUST also look up the current page's `page_rhythm` (`anchor` / `dense` / `breathing`), `page_layouts` (which template SVG to inherit, if any), and `page_charts` (which chart template to adapt, if any). Empty / absent entries are intentional Strategist signals — see executor-base.md §2.1. This rule exists to resist context-compression drift on long decks and to break the uniform "every page is a card grid" default
20	> 9. SVG MUST BE HAND-WRITTEN, NOT SCRIPT-GENERATED — Every SVG page is written by the main agent directly, one page at a time (see rules 6 and 7). Writing or running a Python / Node / shell script that produces the SVG files in batch — looping over pages, templating from data, or emitting them via a generator — is FORBIDDEN, including under "save tokens", "quick draft", or "user is in a hurry" pretexts. The script-generation path was tried on a feature branch and abandoned: cross-page visual consistency depends on per-page authoring with full upstream context, which a generator script cannot reproduce
21
22	> [!IMPORTANT]
23	> ## 🌐 Language & Communication Rule
24	>
25	> - Response language: match the user's input and source materials. Explicit user override (e.g., "请用英文回答") takes precedence.
26	> - Template format: `design_spec.md` MUST follow its original English template structure (section headings, field names) regardless of conversation language. Content values may be in the user's language.
27
28	> [!IMPORTANT]
29	> ## 🔌 Compatibility With Generic Coding Skills
30	>
31	> - `ppt-master` is a repository-specific workflow, not a general application scaffold
32	> - Do NOT create `.worktrees/`, `tests/`, branch workflows, or generic engineering structure by default
33	> - On conflict with a generic coding skill, follow this skill unless the user explicitly says otherwise
34
35	## Main Pipeline Scripts
36
37	\| Script \| Purpose \|
38	\|--------\|---------\|
39	\| `${SKILL_DIR}/scripts/source_to_md/pdf_to_md.py` \| PDF to Markdown \|
40	\| `${SKILL_DIR}/scripts/source_to_md/doc_to_md.py` \| Documents to Markdown — native Python for DOCX/HTML/EPUB/IPYNB, pandoc fallback for legacy formats (.doc/.odt/.rtf/.tex/.rst/.org/.typ) \|
41	\| `${SKILL_DIR}/scripts/source_to_md/excel_to_md.py` \| Excel workbooks to Markdown — supports .xlsx/.xlsm; legacy .xls

People who liked this also viewed

6 picks

Type

ppt-master

91stars18forks

View on GitHub

How to install ppt-master?

opsintech/opsintech-platform/ppt-master

$npx -y skills add OpsinTech/opsintech-platform --skill ppt-master

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# PPT Master Skill
2
3	> AI-driven multi-format SVG content generation system. Converts source documents into high-quality SVG pages through multi-role collaboration and exports to PPTX.
4
5	Core Pipeline: `Source Document → Create Project → [Template] → Strategist → [Image_Generator] → Executor Live Preview → Quality Check → Post-processing → Export`
6
7	> [!CAUTION]
8	> ## 🚨 Global Execution Discipline (MANDATORY)
9	>
10	> This workflow is a strict serial pipeline. The following rules have the highest priority — violating any one of them constitutes execution failure:
11	>
12	> 1. SERIAL EXECUTION — Steps MUST be executed in order; the output of each step is the input for the next. Non-BLOCKING adjacent steps may proceed continuously once prerequisites are met, without waiting for the user to say "continue"
13	> 2. BLOCKING = HARD STOP — Steps marked ⛔ BLOCKING require a full stop; the AI MUST wait for an explicit user response before proceeding and MUST NOT make any decisions on behalf of the user
14	> 3. NO CROSS-PHASE BUNDLING — Cross-phase bundling is FORBIDDEN. (Note: the Eight Confirmations in Step 4 are ⛔ BLOCKING — the AI MUST present recommendations and wait for explicit user confirmation before proceeding. Once the user confirms, all subsequent non-BLOCKING steps — design spec output, SVG generation, speaker notes, and post-processing — may proceed automatically without further user confirmation)
15	> 4. GATE BEFORE ENTRY — Each Step has prerequisites (🚧 GATE) listed at the top; these MUST be verified before starting that Step
16	> 5. NO SPECULATIVE EXECUTION — "Pre-preparing" content for subsequent Steps is FORBIDDEN (e.g., writing SVG code during the Strategist phase)
17	> 6. NO SUB-AGENT SVG GENERATION — Executor Step 6 SVG generation is context-dependent and MUST be completed by the current main agent end-to-end. Delegating page SVG generation to sub-agents is FORBIDDEN
18	> 7. SEQUENTIAL PAGE GENERATION ONLY — In Executor Step 6, after the global design context is confirmed, SVG pages MUST be generated sequentially page by page in one continuous pass. Grouped page batches (for example, 5 pages at a time) are FORBIDDEN
19	> 8. SPEC_LOCK RE-READ PER PAGE — Before generating each SVG page, Executor MUST `read_file <project_path>/spec_lock.md`. All colors / fonts / icons / images MUST come from this file — no values from memory or invented on the fly. Executor MUST also look up the current page's `page_rhythm` (`anchor` / `dense` / `breathing`), `page_layouts` (which template SVG to inherit, if any), and `page_charts` (which chart template to adapt, if any). Empty / absent entries are intentional Strategist signals — see executor-base.md §2.1. This rule exists to resist context-compression drift on long decks and to break the uniform "every page is a card grid" default
20	> 9. SVG MUST BE HAND-WRITTEN, NOT SCRIPT-GENERATED — Every SVG page is written by the main agent directly, one page at a time (see rules 6 and 7). Writing or running a Python / Node / shell script that produces the SVG files in batch — looping over pages, templating from data, or emitting them via a generator — is FORBIDDEN, including under "save tokens", "quick draft", or "user is in a hurry" pretexts. The script-generation path was tried on a feature branch and abandoned: cross-page visual consistency depends on per-page authoring with full upstream context, which a generator script cannot reproduce
21
22	> [!IMPORTANT]
23	> ## 🌐 Language & Communication Rule
24	>
25	> - Response language: match the user's input and source materials. Explicit user override (e.g., "请用英文回答") takes precedence.
26	> - Template format: `design_spec.md` MUST follow its original English template structure (section headings, field names) regardless of conversation language. Content values may be in the user's language.
27
28	> [!IMPORTANT]
29	> ## 🔌 Compatibility With Generic Coding Skills
30	>
31	> - `ppt-master` is a repository-specific workflow, not a general application scaffold
32	> - Do NOT create `.worktrees/`, `tests/`, branch workflows, or generic engineering structure by default
33	> - On conflict with a generic coding skill, follow this skill unless the user explicitly says otherwise
34
35	## Main Pipeline Scripts
36
37	\| Script \| Purpose \|
38	\|--------\|---------\|
39	\| `${SKILL_DIR}/scripts/source_to_md/pdf_to_md.py` \| PDF to Markdown \|
40	\| `${SKILL_DIR}/scripts/source_to_md/doc_to_md.py` \| Documents to Markdown — native Python for DOCX/HTML/EPUB/IPYNB, pandoc fallback for legacy formats (.doc/.odt/.rtf/.tex/.rst/.org/.typ) \|
41	\| `${SKILL_DIR}/scripts/source_to_md/excel_to_md.py` \| Excel workbooks to Markdown — supports .xlsx/.xlsm; legacy .xls

People who liked this also viewed

6 picks

Type