skills/creating-slide-decks/SKILL.md
Use when creating slide decks with Marp/Marpit Markdown (marp), including authoring slide content, designing slide color schemes, and building SVG diagrams or illustrations for the deck.
npx skillsauth add narumiruna/agent-skills creating-slide-decksInstall 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.
Create professional Marp/Marpit presentations, diagrams, and color systems with a consistent design language.
bg syntax for full-slide or split-layout visuals; keep logos, icons, and other small images inline.This umbrella skill does not own module assets or scripts.
Use the focused skills (authoring-marp-slides, designing-slide-colors, creating-svg-illustrations) for paths and commands.
Entry skills (fast routing):
authoring-marp-slides → Marp/Marpit authoring rules, layouts, themesdesigning-slide-colors → palette workflow and color rolescreating-svg-illustrations → SVG diagram rules, patterns, embeddingPick one task and follow the exact reading path:
designing-slide-colorsauthoring-marp-slidescreating-svg-illustrationsauthoring-marp-slides → creating-svg-illustrationsdesigning-slide-colors → authoring-marp-slides → creating-svg-illustrationsMinimal steps (fast path):
designing-slide-colors.authoring-marp-slides.creating-svg-illustrations.Common commands:
designing-slide-colors → palette scriptsauthoring-marp-slides → Marp validation/previewcreating-svg-illustrations → SVG lintingOutput summary: Use module-specific output examples via the entry skills.
Option 1: Use scripts (automated):
Load authoring-marp-slides, resolve scripts/init_presentation.py against that skill directory, and run it by absolute path:
AUTHORING_MARP_SLIDES_SKILL_DIR="/absolute/path/to/authoring-marp-slides"
uv run "$AUTHORING_MARP_SLIDES_SKILL_DIR/scripts/init_presentation.py" technical-dark my-deck.md "My Title" "Author"
Option 2: Work manually (full control):
authoring-marp-slides → assets/templates/ → customizedesigning-slide-colorsauthoring-marp-slidescreating-svg-illustrationsStudy examples first: Read authoring-marp-slides → assets/examples/ to see working presentations before starting.
Use designing-slide-colors for palette scripts and outputs.
Templates (starting points - copy and fill in your content):
authoring-marp-slides → assets/templates/.Examples (learning references - study patterns and copy techniques):
authoring-marp-slides → assets/examples/ for slide patterns.creating-svg-illustrations → assets/examples/ for diagram examples.designing-slide-colors → assets/examples/ for palette examples.Common icons (ready to use in slides):
authoring-marp-slides → assets/icons/.references/index.mddesigning-slide-colorsauthoring-marp-slidescreating-svg-illustrationsreferences/decision-guide.mdUse the focused skills for module-specific rules and references:
designing-slide-colorsauthoring-marp-slidescreating-svg-illustrationsDraw a diagram:
creating-svg-illustrations for core rules and patterns.designing-slide-colors or existing palette.Design slide colors:
designing-slide-colors for workflow and templates.Write slides:
authoring-marp-slides for syntax and layout patterns.designing-slide-colors.authoring-marp-slides.creating-svg-illustrations.See references/decision-guide.md for a flowchart and loading strategy.
Quick rules:
Slides or deck -> authoring-marp-slides
Slides + colors -> designing-slide-colors -> authoring-marp-slides
Slides + diagrams -> authoring-marp-slides + creating-svg-illustrations
Diagram only -> creating-svg-illustrations
Scale reference loading:
Simple request -> core rules only
Complex request -> add patterns and best-practices
Use the focused skills for module-specific output formats:
designing-slide-colors → references/output-examples.mdauthoring-marp-slides → references/output-examples.mdcreating-svg-illustrations → references/output-examples.mdfill and stroke.Common cross-cutting issues:
references/troubleshooting.mdSee authoring-marp-slides, designing-slide-colors, and creating-svg-illustrations for module-specific mistakes.
Use module-specific quick checks:
authoring-marp-slides → validation/preview workflowcreating-svg-illustrations → SVG lint checksdesigning-slide-colors → contrast checksUse the module-specific validation guides:
authoring-marp-slides → references/preview-workflow.mdcreating-svg-illustrations → references/troubleshooting.mddesigning-slide-colors → references/color-design/workflow.md (validation checklist)Always validate before committing files using the focused skills.
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.