| name | mdpr-skill |
| description | Review MDPR Markdown presentation workflows with semantic hints, visual checks, and deterministic renderer boundaries. |
| category | productivity |
| risk | safe |
| source | community |
| source_repo | ch040602/mdpr-skill |
| source_type | community |
| date_added | 2026-07-01 |
| author | ch040602 |
| tags | ["mdpr","presentations","markdown","powerpoint","codex","visual-review","agent-hints"] |
| tools | ["claude","cursor","gemini","codex","antigravity"] |
| license | MIT |
| license_source | https://github.com/ch040602/mdpr-skill/blob/main/LICENSE |
mdpr-skill
Overview
Use this skill as the optional agent companion for
MDPR, a deterministic
Markdown-to-presentation runtime. MDPR owns parsing, layout, theming,
validation, and final PPTX/HTML/PDF rendering. This skill helps an agent review
MDPR workflows, propose weak semantic hints, and explain visual findings without
taking control of slide geometry.
The upstream skill source is
ch040602/mdpr-skill, which includes
schemas, review commands, compatibility artifacts, visual evidence examples, and
MDPR boundary documentation.
When to Use This Skill
- Use when the user asks about MDPR,
mdpresent, Markdown-to-PPTX, or
Markdown presentation review.
- Use when generated MDPR artifacts need semantic, narrative, accessibility, or
visual review notes.
- Use when the user wants Codex-style presentation workflow hints while keeping
MDPR as the deterministic renderer.
- Use when comparing MDPR output against image-only deck generators such as a
codex-ppt style workflow.
- Use when a reusable theme or style-pack proposal should be expressed as an
approval-bound MDPR candidate instead of direct final slide edits.
Core Boundary
- Let MDPR own parsing, slide splitting, recipes, layout, coordinates,
geometry, typography, colors, z-order, arrows, effects, exact icon assets,
renderer object IDs, and final PPTX objects.
- Keep agent output semantic, evidence-based, and schema-valid.
- Express fixes as Markdown cleanup, MDPR rulebook changes, config changes,
deterministic policy changes, or approval-bound proposals.
- Preserve the ability to build the same deck with all agent hints disabled.
- Do not mutate source Markdown unless the user explicitly asks for a cleaned
source draft.
How It Works
Step 1: Identify the MDPR Surface
Classify the user's request before producing advice:
semantic hints: compact intent, grouping, importance, and icon-keyword
suggestions.review report: visual or narrative concerns grounded in rendered evidence,
manifests, or validation reports.layout intent: high-level layout goals from a summarized template catalog,
never concrete placeholder coordinates.theme candidate: reusable token and style-pack proposal for later MDPR
approval/import gates.codex-ppt compatibility: feature mapping and comparison notes only; do not
turn MDPR into a full-slide image renderer.
