marp-slide
Create professional Marp presentation slides with 7 beautiful themes (default, minimal, colorful, dark, gradient, tech, business). Use when users request slide creation, presentations, or Marp documents. Supports custom themes, image layouts, and "make it look good" requests with automatic quality improvements.
- License 许可
- MIT
- 最近更新
- 2026-11-11
- Stars
- ★ 3.3w
- Forks
- 3.9k
01 前言 Front Matter
- name
- marp-slide
- description
- Create professional Marp presentation slides with 7 beautiful themes (default, minimal, colorful, dark, gradient, tech, business). Use when users request slide creation, presentations, or Marp documents. Supports custom themes, image layouts, and "make it look good" requests with automatic quality improvements.
02 资源文件 22
- 资产文件assets/template-basic.md2.1 KB
- 资产文件assets/template-business.md2.8 KB
- 资产文件assets/template-colorful.md2.7 KB
- 资产文件assets/template-dark.md2.3 KB
- 资产文件assets/template-gradient.md2.7 KB
- 资产文件assets/template-minimal.md1.9 KB
- 资产文件assets/template-tech.md2.8 KB
- 资产文件assets/theme-business.css3.6 KB
- 资产文件assets/theme-colorful.css2.9 KB
- 资产文件assets/theme-dark.css2.4 KB
- 资产文件assets/theme-default.css2.5 KB
- 资产文件assets/theme-gradient.css2.9 KB
- 资产文件assets/theme-minimal.css1.7 KB
- 资产文件assets/theme-tech.css3.5 KB
- 参考文档README.md7.5 KB
- 参考文档references/advanced-features.md6.6 KB
- 参考文档references/best-practices.md3.3 KB
- 参考文档references/image-patterns.md4.8 KB
- 参考文档references/marp-syntax.md3.5 KB
- 参考文档references/official-themes.md5.5 KB
- 参考文档references/theme-css-guide.md5.3 KB
- 参考文档references/theme-selection.md3.9 KB
03 SKILL.md 正文
Marp Slide Creator
Create professional, visually appealing Marp presentation slides with 7 pre-designed themes and built-in best practices.
When to Use This Skill
Use this skill when the user:
- Requests to create presentation slides or Marp documents
- Asks to "make slides look good" or "improve slide design"
- Provides vague instructions like "良い感じにして" (make it nice) or "かっこよく" (make it cool)
- Wants to create lecture or seminar materials
- Needs bullet-point focused slides with occasional images
Quick Start
Step 1: Select Theme
First, determine the appropriate theme based on the user's request and content.
Quick theme selection:
- Technical/Developer content → tech theme
- Business/Corporate → business theme
- Creative/Event → colorful or gradient theme
- Academic/Simple → minimal theme
- General/Unsure → default theme
- Dark background preferred → dark or tech theme
For detailed theme selection guidance, read references/theme-selection.md.
Step 2: Create Slides
-
Read relevant references first:
- Always start by reading
references/marp-syntax.mdfor basic syntax - For images:
references/image-patterns.md(official Marpit image syntax) - For advanced features (math, emoji):
references/advanced-features.md - For custom themes:
references/theme-css-guide.md
- Always start by reading
-
Copy content from the appropriate template file:
assets/template-basic.md- Default theme (most common)assets/template-minimal.md- Minimal themeassets/template-colorful.md- Colorful themeassets/template-dark.md- Dark mode themeassets/template-gradient.md- Gradient themeassets/template-tech.md- Tech/code themeassets/template-business.md- Business theme
-
Read
references/best-practices.mdfor quality guidelines -
Structure content following best practices:
- Title slide with
<!-- _class: lead --> - Concise h2 titles (5-7 characters in Japanese)
- 3-5 bullet points per slide
- Adequate whitespace
- Title slide with
-
Add images if needed using patterns from
references/image-patterns.md -
Save to
the project output directorywith.mdextension
Available Themes
1. Default Theme
Colors: Beige background, navy text, blue headings
Style: Clean, sophisticated with decorative lines
Use for: General seminars, lectures, presentations
Template: template-basic.md
2. Minimal Theme
Colors: White background, gray text, black headings
Style: Minimal decoration, wide margins, light fonts
Use for: Content-focused presentations, academic talks
Template: template-minimal.md
3. Colorful & Pop Theme
Colors: Pink gradient background, multi-color accents
Style: Vibrant gradients, bold fonts, rainbow accents
Use for: Youth-oriented events, creative projects
Template: template-colorful.md
4. Dark Mode Theme
Colors: Black background, cyan/purple accents
Style: Dark theme with glow effects, eye-friendly
Use for: Tech presentations, evening talks, modern look
Template: template-dark.md
5. Gradient Background Theme
Colors: Purple/pink/blue/green gradients (varies per slide)
Style: Different gradient per slide, white text, shadows
Use for: Visual-focused, creative presentations
Template: template-gradient.md
6. Tech/Code Theme
Colors: GitHub-style dark background, blue/green accents
Style: Code fonts, Markdown-style headers with # symbols
Use for: Programming tutorials, tech meetups, developer content
Template: template-tech.md
7. Business Theme
Colors: White background, navy headings, blue accents
Style: Corporate presentation style, top border, table support
Use for: Business presentations, proposals, reports
Template: template-business.md
Creating Slides Process
Basic Workflow
-
Understand requirements
- Identify content: title, topics, key points
- Determine target audience
- Assess formality level
-
Select theme
- Use quick selection rules above
- If uncertain, consult
references/theme-selection.md - Default to default theme if still unsure
-
Apply template
- Load appropriate template from
assets/ - CSS is already embedded - no external files needed
- Maintain template structure
- Load appropriate template from
-
Structure content
- Title slide:
<!-- _class: lead -->+ h1 - Content slides: h2 title + bullet points
- Keep titles to 5-7 characters (Japanese)
- Use 3-5 bullet points per slide
- Title slide:
-
Refine quality
- Read
references/best-practices.md - Ensure adequate whitespace
- Maintain consistency
- Keep text concise (15-25 chars per line)
- Read
-
Add images
- If needed, consult
references/image-patterns.md - Common:
for side images - Use proper Marp image syntax
- If needed, consult
-
Output file
- Save to
the project output directory - Use descriptive filename like
presentation.md
- Save to
Handling "Make It Look Good" Requests
When users give vague instructions like "良い感じにして", "かっこよく", or "make it cool":
-
Infer theme from content:
- Business content → business theme
- Technical content → tech or dark theme
- Creative content → gradient or colorful theme
- General → default theme
-
Apply best practices automatically:
- Shorten titles to 5-7 characters
- Limit bullet points to 3-5 items
- Add adequate whitespace
- Use consistent structure
-
Enhance visual hierarchy:
- Use h3 for sub-sections when appropriate
- Break up dense text into multiple slides
- Ensure logical flow (intro → body → conclusion)
-
Maintain professional tone:
- Match formality to content
- Use parallel structure in lists
- Keep technical terms consistent
Image Integration
For slides with images, consult references/image-patterns.md for detailed syntax.
Common patterns:
- Side image:
- Image on right, text on left - Centered:
- Centered with specific width - Full background:
- Full-screen background - Multiple images: Multiple
![bg]declarations
Example lecture pattern:
## Slide Title

- Explanation point 1
- Explanation point 2
- Explanation point 3
File Output
Always save the final Marp file to the project output directory with .md extension:
presentation.mdseminar-slides.mdlecture-materials.md
Quality Checklist
Before delivering slides, verify:
- [ ] Theme selected appropriately for content
- [ ] CSS theme is embedded in the file
- [ ] Title slide uses
<!-- _class: lead --> - [ ] All h2 titles are concise (5-7 chars)
- [ ] Bullet points are 3-5 items per slide
- [ ] Images use proper Marp syntax
- [ ] File saved to outputs directory
- [ ] Content follows best practices
References
Core Documentation
- Marp syntax:
references/marp-syntax.md- Basic Marp/Marpit syntax (directives, frontmatter, pagination, etc.) - Image patterns:
references/image-patterns.md- Official image syntax (bg, filters, split backgrounds) - Theme CSS guide:
references/theme-css-guide.md- How to create custom themes based on Marpit specification - Advanced features:
references/advanced-features.md- Math, emoji, fragmented lists, Marp CLI, VS Code - Official themes:
references/official-themes.md- default, gaia, uncover themes documentation
Quality & Selection Guides
- Theme selection:
references/theme-selection.md- How to choose the right theme for content - Best practices:
references/best-practices.md- Quality guidelines for "cool" slides
Templates & Assets
- Templates:
assets/template-*.md- Starting points with embedded CSS for each theme (7 themes) - Standalone CSS:
assets/theme-*.css- CSS files for reference (already embedded in templates)
Official External Links
- Marp Official Site: https://marp.app/
- Marpit Directives: https://marpit.marp.app/directives
- Marpit Image Syntax: https://marpit.marp.app/image-syntax
- Marpit Theme CSS: https://marpit.marp.app/theme-css
- Marp Core GitHub: https://github.com/marp-team/marp-core
- Marp CLI GitHub: https://github.com/marp-team/marp-cli
04 同仓库更多 Skills
wealthville-pool-scoring
Score DeFi liquidity pools before providing liquidity. Returns a 0-100 pool score and an Enter/Hold/Exit/Reduce/Avoid verdict with calibrated confidence for ~68,800 Solana pools and 575 EVM pools, plus a public miss-inclusive track record. Use when asked whether a pool is worth LPing into, which pools look best right now, or how accurate the scores have actually been.
technical-debt-auditor
Scans a codebase and produces a quantified technical debt report with a prioritized remediation plan. Analyzes dead code, TODO/FIXME/HACK markers, dependency staleness, complexity hotspots, code duplication signals, test coverage gaps, unused exports, and outdated patterns. Use this skill when the user asks to audit their codebase for tech debt, wants a health check of their code quality, says things like "where should I focus refactoring", "find code smells", "audit my codebase", "what technical debt do we have", "prioritize cleanup work", or asks about code quality metrics. Also trigger when the user mentions "code rot", "legacy cleanup", "refactoring priorities", or wants to understand the overall health of a project before a major effort. Trigger even if the user doesn't say "technical debt" explicitly — any request to systematically assess code quality and identify improvement priorities belongs here.
readonly-sql-guard
Make an agent's database access provably read-only. Use when an agent runs caller-supplied SQL against a production/ERP/analytics database (a "query" MCP tool, text-to-SQL, an admin console), or when reviewing DB-access code for write/DDL/side-effect/transaction-escape risks. Checks what a statement CALLS, not just its shape.
web-artifacts-builder
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
discernment-nudge
After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.