| name | easyslides |
| description | Canonical EasySlides entry point for creating, distilling, editing, reviewing, and exporting editable academic PPTX presentations. Use whenever the user explicitly says EasySlides/easyslides or asks for PPTX distillation, a content-free reusable template, template/component/symbol extraction, template reuse, thesis-defense or research slides, slide reconstruction, native PowerPoint preview, or visual QA, including 蒸馏PPT、提取PPT模板、 拆分组件与符号资产、复用模板、论文汇报PPT和答辩PPT。
|
EasySlides Academic PPTX
EasySlides is a repository-backed Codex plugin. This skill is a thin adapter
around the canonical operating guide at ../../SKILL.md; read that file
completely before executing a presentation task.
Required startup reading
From the plugin/repository root, read:
SKILL.md, the complete route and execution contract.ARCHITECTURE.md, the layer model and supported capability paths.workflows/routing.md, deterministic route selection for the request.skills/easyslides-clarify/SKILL.md, the blocking user-choice gate.
Run the clarification gate before selecting a route whenever the request is
ambiguous. Then read the specific workflow selected by the routing guide. For
a source PPTX that should become a reusable template, invoke the plugin-local
skills/easyslides-distill/SKILL.md first, followed by the PPTX, template-reuse, and
template-spec guidance selected by workflows/pptx-to-easyslides-template.md.
Do not invent a second PPTX export backend: use the existing SVG/shape IR to
DrawingML/PPTX pipeline or the documented native PPTX route.
The plugin-local skills are authoritative. Treat separately installed legacy
skills such as ppt-distill, easyppt, or easyslides-template-reuse as
compatibility references only; do not let them replace this canonical route or
reintroduce source-slide-order filling.
Runtime conventions
- Run commands from the plugin/repository root.
- Use
python scripts/easyslides.py --help to discover the command hub.
- Keep generated projects and private source material under the existing
ignored project/output locations.
- Preserve the existing templates, references, workflows, and QA gates.
- Never place API keys, tokens, or private source material in committed files.
Common command entry points
python scripts/easyslides.py --help
python scripts/easyslides.py clarify --help
python scripts/easyslides.py project --help
python scripts/easyslides.py source-to-md --help
python scripts/easyslides.py distill --help
python scripts/easyslides.py semantic-render --help
python scripts/easyslides.py template-gate --help
python scripts/easyslides.py review --help
python scripts/easyslides.py workflow --help
For PPTX-to-template work, use the same command hub:
python scripts/easyslides.py distill "path\to\source.pptx" --template-id my_template
Before selecting a cover, TOC, transition, or ending variant from a
functional_page_variants.json registry, run the named-slot geometry gate:
python scripts/functional_page_variant_adapter.py <template_dir> --role toc --check-all
This gate is fail-closed. It rejects variants whose editable text slots
overlap or whose same slot id occupies multiple independent text boxes, because
those defects otherwise become duplicated or mutually obscured text in the
native PPTX export. Repair the SVG geometry or choose another variant before
rendering content.
The plugin is intentionally lightweight: the repository remains the runtime,
template library, and source of truth. Add a dedicated MCP server only after a
stable command contract is demonstrated by the existing CLI and tests.
