skills/slides-visuals/authoring-marp-slides/SKILL.md
Write, revise, structure, or validate Marp/Marpit Markdown slides, including directives, layouts, themes, templates, and rendered-deck checks. Use for slide authoring when palette or illustration design is not the primary task.
npx skillsauth add narumiruna/agent-skills authoring-marp-slidesInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Load only the authoring detail the deck needs.
| Need | Read or use |
| --- | --- |
| Directives and syntax | references/syntax-guide.md |
| Common layouts | references/patterns.md |
| Complex layouts | references/advanced-layouts.md |
| Theme behavior | references/themes.md |
| Content and QA guidance | references/best-practices.md |
| Structural precheck | scripts/check_marpit_structure.sh <deck.md> |
| Syntax, render, and visual checks | references/preview-workflow.md |
| Starting point | assets/templates/ |
| Known-good patterns | assets/examples/ |
bg syntax for full-slide or split-layout visuals; keep logos, icons, and other small visuals inline.bash "$SKILL_DIR/scripts/check_marpit_structure.sh" path/to/deck.md. It checks delimiters and marp: true but does not parse YAML or Marp syntax. Then follow references/preview-workflow.md to export with the actual Marp renderer; inspect whether directives took effect, plus the title, densest slide, and every image/SVG slide. Report structural, strict-YAML, renderer, and visual evidence separately; never infer one from another.Do not claim visual validation from Markdown inspection alone. Do not commit, publish, or convert formats unless requested.
development
Score or compare one or more agent skills across trigger clarity, workflow actionability, safety boundaries, verification rigor, incremental knowledge value, and leanness. Use only when the user explicitly asks for ratings, numerical quality scores, rubric-based scorecards, or scored comparisons; use creating-agent-skills for unscored reviews or revisions.
development
Assess or improve an existing codebase's architecture when the user asks about module boundaries, coupling, scattered ownership, testability, change locality, deep modules, seams, or behavior-preserving structural refactoring. Use for cross-module design rather than ordinary diff review or a confirmed edge-case bug fix.
development
Perform read-only security audits, vulnerability assessments, or threat-focused reviews of diffs, pull requests, code paths, or explicitly scoped repositories when security is the primary objective or acceptance criterion. Use reviewing-code for ordinary review with baseline security coverage and hardening-code-paths for fixing confirmed findings.
development
Run iterative multi-reviewer panels over a code diff, verify their findings, apply explicitly authorized fixes, and re-review the updated change until it passes or reaches a stopping condition. Use when the user asks for a panel loop, multi-model code-review consensus, or a review-fix-re-review cycle.