生成AIで書いた記事・スライド・文書の「AI臭」を徹底除去するスキル。 「なんかAIっぽい」「無機質」「整いすぎ」と感じる文章を人間の体温が宿る文体へ変換する。 記事・スライドのリライト依頼、AI臭チェック、「もっと人間らしく書いて」という要求で積極的に使用する。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
shinobi-coder701/zenn-docs62026년 9월 17일 업데이트
무료GitHub에 공개
marp-slides
Create professional, visually excellent presentation slides in Marp Markdown format. Use this skill when the user asks to: - Create a presentation, slides, deck, slideshow, or プレゼン / スライド - Write or generate slides about a specific topic - Make a Marp .md file for presenting Produces complete, ready-to-render .md files with embedded custom CSS theme, narrative structure, and polished visual design. Supports Japanese and English content.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
설치 방법 보기포함된 파일(4)
- SKILL.md4.0 KB
- assets/excel-theme.css8.8 KB
- references/design-principles.md4.0 KB
- references/layout-patterns.md6.3 KB
SKILL.md(원문)
설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
Marp Slides — Excellence Workflow
Step 1 — Gather Requirements
Clarify before generating (infer from context when obvious):
| Field | Default if unspecified |
|---|---|
| Topic / title | Ask |
| Audience | General business |
| Purpose | Inform / present findings |
| Slide count | 12–15 |
| Language | Match user's language |
| Output path | ./slides.md |
Ask concisely. For simple requests ("make slides about X"), infer and proceed.
Step 2 — Plan the Narrative Arc
Before writing, sketch the arc:
Title → Agenda → Problem/Context → Body (3–5 slides) → Evidence → Summary → CTA → Ending
See references/design-principles.md for purpose-specific arc patterns and slide count guidelines.
Step 3 — Generate the Marp File
Required Frontmatter
---
marp: true
theme: excel
paginate: true
size: 16:9
html: true
style: |
/* [PASTE FULL CONTENTS OF assets/excel-theme.css HERE] */
---
Always embed the full CSS from assets/excel-theme.css in the style: block.
This makes the file self-contained and immediately renderable without external setup.
Slide Class Usage
Apply per-slide with <!-- _class: CLASS --> immediately before the slide separator:
| Class | Use for |
|---|---|
title | Cover slide — dark gradient, large H1 |
section | Chapter break — blue background |
lead | Key message — centered, large text |
dark | Code showcase, dramatic emphasis |
ending | Final slide — dark gradient, centered |
| (none) | Standard content slides |
Layout Components
Use HTML <div> elements with these classes (requires html: true):
| Component | Class | Use for |
|---|---|---|
| Two columns | .columns | Side-by-side comparison |
| Three columns | .columns.col-3 | Three options/features |
| Asymmetric cols | .columns.col-6-4 or .col-4-6 | Text + image/stat |
| Info card | .card .card.accent/.warn/.success/.danger | Categorized items |
| Key message box | .highlight | Single most important takeaway |
| Large metric | .number (or .number.warm) | KPI display |
| Tag / badge | .tag .tag.warm/.success/.outline | Tech stack, labels |
| Step list | .steps + .step | Numbered process |
| Icon row | .icons + .icon-item | Feature overview |
| Progress bar | .progress + .progress-bar | Status/roadmap |
See references/layout-patterns.md for copy-paste code examples of each.
Content Quality Rules
- 1 idea per slide — if a slide has two topics, split it
- Max 5–6 bullets per slide, each ≤12 words
**Bold**the key phrase in each bullet (exactly one per bullet)- Vary visual types — never 3+ consecutive all-bullet slides
- Use
.highlightfor the single most important message per section - Write real content, not placeholders like "ここに説明を入れる"
See references/design-principles.md for full design guidance.
Step 4 — Output
- Write the complete
.mdfile to the specified path (default:./slides.md) - Tell the user:
- How to render:
npx @marp-team/marp-cli slides.md --html(PDF/HTML) - VS Code: Install "Marp for VS Code", enable HTML in settings (
markdown.marp.enableHtml: true)
- How to render:
- Offer to adjust: slide count, language, style, or add specific sections
Technical Notes
html: trueis required for layout components (.columns,.card, etc.)- Without it, the HTML divs render as literal text — always include it
- For Tailwind CSS (advanced): add CDN script after frontmatter with
preflight: false - Mermaid diagrams: enable HTML and use
<div class="mermaid">...</div>
리뷰
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
댓글
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
같은 저장소의 스킬
Optimize and convert Zenn Flavored Markdown (ZFM) articles to Dev.to (Forem) compatible Markdown. Use this skill whenever the user wants to post a Zenn article to Dev.to, needs to convert markdown for cross-posting, or asks to "optimize for dev.to". It handles front matter conversion, Liquid tag embeds, KaTeX math blocks, callout transformations, and general formatting adjustments required by Dev.to.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
shinobi-coder701/zenn-docs62026년 9월 17일 업데이트
AI生成UIの没個性的パターン（AIスロップ美学）を検出・回避し、文脈に根ざした意図あるデザインを生成するためのガード。フロントエンドのUI実装、デザイン生成、コンポーネント設計、CSSスタイリング、カラーパレット選定、フォント選択、レイアウト構築を行う際に自動的に適用する。「UIを作って」「画面を実装して」「デザインして」「スタイルを当てて」「ランディングページを作って」「Webサイトを作成して」「ダッシュボードを構築して」「コンポーネントを実装して」等のUI生成タスク全般で使用する。Claude Code、Codex、GitHub Copilot、Cursor、その他AIエージェント共通で適用可能。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
shinobi-coder701/zenn-docs62026년 9월 17일 업데이트
Marp形式プレゼンテーションの専門レビュー・評価・改善スキル。 10軸スコアリング（100点満点）で品質を定量評価し、具体的な改善コード付きで提案する。 Use when the user asks to: - Review, evaluate, or critique a Marp presentation / プレゼンをレビュー / 評価 / 添削 - Improve, polish, or upgrade existing slides / スライドを改善 / ブラッシュアップ - Check slide quality, score slides, or audit a deck / スライドの品質チェック / 採点 - "このプレゼンどう？" "スライドを見てほしい" "プレゼン資料のフィードバック" Reads .md files with Marp frontmatter, scores across 10 dimensions, and outputs a detailed review report with concrete before/after code improvements. Works as a companion to the marp-slides skill (generation → review → improvement cycle).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
shinobi-coder701/zenn-docs62026년 9월 17일 업데이트
リポジトリの構造・技術スタック・機能一覧・セットアップ手順を動的に解析し、 包括的なドキュメントを自動生成するスキル。言語・フレームワーク問わず汎用的に動作する。 Use this skill whenever the user asks to: - Explain a repository / リポジトリの説明 / リポジトリの概要 - Generate a README / README生成 / README作成 - Understand project structure / プロジェクト構成を教えて / 構造を説明して - Learn how to run a project / 使い方を教えて / 動かし方 / セットアップ方法 - Get a repo overview / repo overview / explain this repo / what does this repo do - List features / 機能一覧 / このプロジェクトは何ができる？ - Onboard to a new codebase / コードベースのキャッチアップ / 新しいリポジトリに入った - "このリポジトリ何？" "プロジェクトの全体像" "how to run this project" - "コードの全体を把握したい" "ドキュメントを整備して" "技術スタックを知りたい" This skill is especially useful when joining a new project, onboarding team members, or when a repository lacks proper documentation. It works with ANY repository regardless of programming language, framework, or project type.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
shinobi-coder701/zenn-docs62026년 9월 17일 업데이트
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
shinobi-coder701/zenn-docs62026년 9월 17일 업데이트