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.
Step 2: Ground Every Finding
Reference available evidence such as:
- source Markdown path or heading text
- MDPR manifest summaries
- rendered preview image paths
- validation report IDs
- source notes or citation metadata
- schema names such as
agent-hint.json, review-report.json, or
mdpr-theme-candidate-v1
If evidence is missing, say what artifact is needed instead of inventing a
pass/fail result.
Step 3: Keep Hints Weak
Allowed hints:
- slide or section intent
- content grouping
- relative importance
- icon-search keywords
- accessibility or citation review notes
- generated-image candidate briefs when an icon would be too small or too
semantically ambiguous
Disallowed hints:
- final coordinates, sizes, z-order, geometry, or object IDs
- exact colors, typography, arrows, effects, or icon asset choices
- final layout IDs or placeholder IDs
- pass/fail validation decisions not backed by MDPR validation
Step 4: Route Fixes to MDPR-Owned Changes
When repeated issues appear, recommend a deterministic follow-up surface:
- Markdown cleanup
- MDPR rulebook change
- MDPR config/profile change
- MDPR theme-pack registration
- MDPR validation improvement
- approval-bound deck-local override or style-pack candidate
Useful Local Commands
Run these only when the upstream mdpr-skill CLI is available in the current
workspace and the referenced input files exist.
node bin/mdpr-skill.js hint --source-sha256 <64hex> --out .mdpresent/proposals/agent-hint.json
node bin/mdpr-skill.js review --manifest dist/mdpresent-manifest.json --out .mdpresent/review/review-report.json
node bin/mdpr-skill.js narrative --markdown deck.md --manifest dist/mdpresent-manifest.json --out .mdpresent/review/narrative-review.json
node bin/mdpr-skill.js layout-intent --layout-catalog template-layout-catalog.json --out .mdpresent/review/layout-intent.json
node bin/mdpr-skill.js accessibility --markdown deck.md --audience "executive review" --out .mdpresent/review/accessibility-review.json
Examples
Review a Rendered MDPR Deck
- Read the source Markdown, manifest summary, rendered image list, and any
validation report.
- Separate source-content problems from renderer/rulebook problems.
- Report only evidence-backed visual concerns.
- Recommend deterministic MDPR fixes when the same issue repeats.
Finding: Slide 4 has weak visual hierarchy between the metric and explanation.
Evidence: rendered/slide-04.png, manifest slide id `s4`, heading "Revenue Mix".
MDPR-owned fix: adjust the metric-card recipe spacing rule or choose a
deterministic layout profile with stronger numeric emphasis.
Propose a Theme Candidate
- Treat the source design as a visual system, not content to copy.
- Extract reusable tokens, semantic layout blueprints, decoration grammar, and
best-fit scenarios.
- Emit an approval-bound
mdpr-theme-candidate-v1.
- Keep
mdprOwnsFinalLayout, mdprOwnsFinalThemeBinding, and
noRawUseInAgentHints true.
{
"schema": "mdpr-theme-candidate-v1",
"source": "rendered reference set approved by user",
"useCases": ["executive review", "research update"],
"constraints": {
"mdprOwnsFinalLayout": true,
"mdprOwnsFinalThemeBinding": true,
"noRawUseInAgentHints": true
}
}
Compare with codex-ppt Style Workflows
Use codex-ppt only as a capability reference or image-only baseline. Preserve
the output-model distinction: codex-ppt style workflows may produce full-slide
images, while MDPR defaults to editable PPTX/HTML/PDF with deterministic
validation.
Comparison note: codex-ppt style output may optimize for a single rasterized
slide image. MDPR should instead preserve editable slide objects and route
visual improvements through recipes, themes, and validation policies.
Best Practices
- Do: Prefer concise semantic hints over restating the source.
- Do: Keep review notes actionable for MDPR maintainers.
- Do: Call out missing evidence before making quality claims.
- Do: Treat LLM judgment as triage only; MDPR validation remains the release
gate.
- Avoid: Turning generated asset prompts into final asset selections.
- Avoid: Recommending raw colors, coordinates, or renderer object IDs from
agent judgment alone.
Limitations
- This skill does not replace MDPR runtime validation.
- This skill does not generate final slide coordinates or final PPTX objects.
- This skill does not make MDPR depend on an LLM.
- This skill should not be used to copy private deck designs or proprietary
slide content.
Common Pitfalls
Problem: Treating mdpr-skill output as final slide layout.
Solution: Keep hints semantic and let MDPR choose final layout, geometry,
and renderer objects.
Problem: Reporting visual issues without evidence.
Solution: Link each finding to source Markdown, a manifest entry, rendered
previews, validation reports, or another concrete artifact.
Problem: Copying codex-ppt image-only behavior into MDPR.
Solution: Use image-only generators as comparison baselines while
preserving MDPR's editable PPTX/HTML/PDF output model.
Security & Safety Notes
- Review only files the user has provided or authorized.
- Do not fetch private references, credentials, or paid assets without explicit
permission.
- Do not include secrets, API keys, or private source content in generated
review reports or theme candidates.
- Treat all CLI commands as local workspace commands; confirm input paths exist
before running them.
Related Skills
@frontend-slides - Use for browser-native HTML presentation generation.
@2slides-ppt-generator - Use for hosted API-based presentation generation.
@office-productivity - Use for broader document, spreadsheet, and slide
workflow coordination.
1---2name: mdpr-skill3description: "Review MDPR Markdown presentation workflows with semantic hints, visual checks, and deterministic renderer boundaries."4category: productivity5risk: safe6source: community7source_repo: ch040602/mdpr-skill8source_type: community9date_added: "2026-07-01"10author: ch04060211tags: [mdpr, presentations, markdown, powerpoint, codex, visual-review, agent-hints]12tools: [claude, cursor, gemini, codex, antigravity]13license: "MIT"14license_source: "https://github.com/ch040602/mdpr-skill/blob/main/LICENSE"15metadata:16 source: https://skillmd.com/skills/mhassan0000/mdpr-skill17---1819# mdpr-skill2021## Overview2223Use this skill as the optional agent companion for24[MDPR](https://github.com/ch040602/MdPr), a deterministic25Markdown-to-presentation runtime. MDPR owns parsing, layout, theming,26validation, and final PPTX/HTML/PDF rendering. This skill helps an agent review27MDPR workflows, propose weak semantic hints, and explain visual findings without28taking control of slide geometry.2930The upstream skill source is31[`ch040602/mdpr-skill`](https://github.com/ch040602/mdpr-skill), which includes32schemas, review commands, compatibility artifacts, visual evidence examples, and33MDPR boundary documentation.3435## When to Use This Skill3637- Use when the user asks about MDPR, `mdpresent`, Markdown-to-PPTX, or38 Markdown presentation review.39- Use when generated MDPR artifacts need semantic, narrative, accessibility, or40 visual review notes.41- Use when the user wants Codex-style presentation workflow hints while keeping42 MDPR as the deterministic renderer.43- Use when comparing MDPR output against image-only deck generators such as a44 codex-ppt style workflow.45- Use when a reusable theme or style-pack proposal should be expressed as an46 approval-bound MDPR candidate instead of direct final slide edits.4748## Core Boundary4950- Let MDPR own parsing, slide splitting, recipes, layout, coordinates,51 geometry, typography, colors, z-order, arrows, effects, exact icon assets,52 renderer object IDs, and final PPTX objects.53- Keep agent output semantic, evidence-based, and schema-valid.54- Express fixes as Markdown cleanup, MDPR rulebook changes, config changes,55 deterministic policy changes, or approval-bound proposals.56- Preserve the ability to build the same deck with all agent hints disabled.57- Do not mutate source Markdown unless the user explicitly asks for a cleaned58 source draft.5960## How It Works6162### Step 1: Identify the MDPR Surface6364Classify the user's request before producing advice:6566- `semantic hints`: compact intent, grouping, importance, and icon-keyword67 suggestions.68- `review report`: visual or narrative concerns grounded in rendered evidence,69 manifests, or validation reports.70- `layout intent`: high-level layout goals from a summarized template catalog,71 never concrete placeholder coordinates.72- `theme candidate`: reusable token and style-pack proposal for later MDPR73 approval/import gates.74- `codex-ppt compatibility`: feature mapping and comparison notes only; do not75 turn MDPR into a full-slide image renderer.7677### Step 2: Ground Every Finding7879Reference available evidence such as:8081- source Markdown path or heading text82- MDPR manifest summaries83- rendered preview image paths84- validation report IDs85- source notes or citation metadata86- schema names such as `agent-hint.json`, `review-report.json`, or87 `mdpr-theme-candidate-v1`8889If evidence is missing, say what artifact is needed instead of inventing a90pass/fail result.9192### Step 3: Keep Hints Weak9394Allowed hints:9596- slide or section intent97- content grouping98- relative importance99- icon-search keywords100- accessibility or citation review notes101- generated-image candidate briefs when an icon would be too small or too102 semantically ambiguous103104Disallowed hints:105106- final coordinates, sizes, z-order, geometry, or object IDs107- exact colors, typography, arrows, effects, or icon asset choices108- final layout IDs or placeholder IDs109- pass/fail validation decisions not backed by MDPR validation110111### Step 4: Route Fixes to MDPR-Owned Changes112113When repeated issues appear, recommend a deterministic follow-up surface:114115- Markdown cleanup116- MDPR rulebook change117- MDPR config/profile change118- MDPR theme-pack registration119- MDPR validation improvement120- approval-bound deck-local override or style-pack candidate121122## Useful Local Commands123124Run these only when the upstream `mdpr-skill` CLI is available in the current125workspace and the referenced input files exist.126127```bash128node bin/mdpr-skill.js hint --source-sha256 <64hex> --out .mdpresent/proposals/agent-hint.json129node bin/mdpr-skill.js review --manifest dist/mdpresent-manifest.json --out .mdpresent/review/review-report.json130node bin/mdpr-skill.js narrative --markdown deck.md --manifest dist/mdpresent-manifest.json --out .mdpresent/review/narrative-review.json131node bin/mdpr-skill.js layout-intent --layout-catalog template-layout-catalog.json --out .mdpresent/review/layout-intent.json132node bin/mdpr-skill.js accessibility --markdown deck.md --audience "executive review" --out .mdpresent/review/accessibility-review.json133```134135## Examples136137### Review a Rendered MDPR Deck1381391. Read the source Markdown, manifest summary, rendered image list, and any140 validation report.1412. Separate source-content problems from renderer/rulebook problems.1423. Report only evidence-backed visual concerns.1434. Recommend deterministic MDPR fixes when the same issue repeats.144145```markdown146Finding: Slide 4 has weak visual hierarchy between the metric and explanation.147Evidence: rendered/slide-04.png, manifest slide id `s4`, heading "Revenue Mix".148MDPR-owned fix: adjust the metric-card recipe spacing rule or choose a149deterministic layout profile with stronger numeric emphasis.150```151152### Propose a Theme Candidate1531541. Treat the source design as a visual system, not content to copy.1552. Extract reusable tokens, semantic layout blueprints, decoration grammar, and156 best-fit scenarios.1573. Emit an approval-bound `mdpr-theme-candidate-v1`.1584. Keep `mdprOwnsFinalLayout`, `mdprOwnsFinalThemeBinding`, and159 `noRawUseInAgentHints` true.160161```json162{163 "schema": "mdpr-theme-candidate-v1",164 "source": "rendered reference set approved by user",165 "useCases": ["executive review", "research update"],166 "constraints": {167 "mdprOwnsFinalLayout": true,168 "mdprOwnsFinalThemeBinding": true,169 "noRawUseInAgentHints": true170 }171}172```173174### Compare with codex-ppt Style Workflows175176Use codex-ppt only as a capability reference or image-only baseline. Preserve177the output-model distinction: codex-ppt style workflows may produce full-slide178images, while MDPR defaults to editable PPTX/HTML/PDF with deterministic179validation.180181```markdown182Comparison note: codex-ppt style output may optimize for a single rasterized183slide image. MDPR should instead preserve editable slide objects and route184visual improvements through recipes, themes, and validation policies.185```186187## Best Practices188189- Do: Prefer concise semantic hints over restating the source.190- Do: Keep review notes actionable for MDPR maintainers.191- Do: Call out missing evidence before making quality claims.192- Do: Treat LLM judgment as triage only; MDPR validation remains the release193 gate.194- Avoid: Turning generated asset prompts into final asset selections.195- Avoid: Recommending raw colors, coordinates, or renderer object IDs from196 agent judgment alone.197198## Limitations199200- This skill does not replace MDPR runtime validation.201- This skill does not generate final slide coordinates or final PPTX objects.202- This skill does not make MDPR depend on an LLM.203- This skill should not be used to copy private deck designs or proprietary204 slide content.205206## Common Pitfalls207208- **Problem:** Treating mdpr-skill output as final slide layout.209 **Solution:** Keep hints semantic and let MDPR choose final layout, geometry,210 and renderer objects.211212- **Problem:** Reporting visual issues without evidence.213 **Solution:** Link each finding to source Markdown, a manifest entry, rendered214 previews, validation reports, or another concrete artifact.215216- **Problem:** Copying codex-ppt image-only behavior into MDPR.217 **Solution:** Use image-only generators as comparison baselines while218 preserving MDPR's editable PPTX/HTML/PDF output model.219220## Security & Safety Notes221222- Review only files the user has provided or authorized.223- Do not fetch private references, credentials, or paid assets without explicit224 permission.225- Do not include secrets, API keys, or private source content in generated226 review reports or theme candidates.227- Treat all CLI commands as local workspace commands; confirm input paths exist228 before running them.229230## Related Skills231232- `@frontend-slides` - Use for browser-native HTML presentation generation.233- `@2slides-ppt-generator` - Use for hosted API-based presentation generation.234- `@office-productivity` - Use for broader document, spreadsheet, and slide235 workflow coordination.