presentation-outline
について
このスキルはGoogleドキュメントを、タイトル、サブタイトル、箇条書きを含む構造化された10スライドのプレゼンテーションアウトラインに変換します。既存の技術文書から迅速にプレゼンテーションの草案を作成する必要がある開発者に最適です。出力はチャットに直接提供され、即座にレビューとさらなる編集が可能です。
クイックインストール
Claude Code
推奨/plugin add https://github.com/christopheryeo/claude-skillsgit clone https://github.com/christopheryeo/claude-skills.git ~/.claude/skills/presentation-outlineこのコマンドをClaude Codeにコピー＆ペーストしてスキルをインストールします
ドキュメント
Presentation Outline
Generate a structured presentation outline from a Google Doc to quickly transform topic documentation into a presentation-ready format.
How It Works
This skill takes a Google Doc containing information about a topic and transforms it into a presentation outline with the following structure per slide:
- Slide Title - The main topic or concept
- Slide Subtitle - Context or focus area (can be optional)
- Bullet Points - Supporting details (one subject per slide, 3-5 bullets)
The output is limited to a maximum of 10 slides for an optimal presentation length.
Process
- Provide a Google Doc - Share the URL or ID of a Google Doc containing the topic information
- Outline Generation - Claude extracts key concepts and organizes them into distinct slides
- Chat Display - The outline is displayed in the chat window for you to review and edit
- Refinement - Adjust titles, subtitles, or bullets as needed
Guidelines for Best Results
For detailed best practices on what makes an effective presentation outline, see references/guide.md. Key principles include:
- One topic per slide - Each slide focuses on a single main concept
- Concise titles - 3-8 words that clearly identify the slide topic
- Supporting bullets - 3-5 bullet points per slide that support the main topic
- Optimal length - 8-10 slides provides balanced pacing for a 20-30 minute presentation
- Logical flow - Clear progression from opening to conclusion
Output Format
The outline is displayed in markdown format in the chat with clear delineation between slides:
# Slide 1: [Title]
**Subtitle**: [Subtitle if applicable]
- Bullet point 1
- Bullet point 2
- Bullet point 3
# Slide 2: [Title]
**Subtitle**: [Subtitle if applicable]
- Bullet point 1
- Bullet point 2
- Bullet point 3
Tips
- Longer, more detailed source documents produce better outlines
- Ensure your Google Doc clearly separates different topics and concepts
- Review the generated outline and edit slide titles/bullets for your specific audience
- If the outline exceeds 10 slides, consider combining related slides or removing less critical content
GitHub リポジトリ
関連スキル
content-collections
メタThis skill provides a production-tested setup for Content Collections, a TypeScript-first tool that transforms Markdown/MDX files into type-safe data collections with Zod validation. Use it when building blogs, documentation sites, or content-heavy Vite + React applications to ensure type safety and automatic content validation. It covers everything from Vite plugin configuration and MDX compilation to deployment optimization and schema validation.
evaluating-llms-harness
テストThis Claude Skill runs the lm-evaluation-harness to benchmark LLMs across 60+ standardized academic tasks like MMLU and GSM8K. It's designed for developers to compare model quality, track training progress, or report academic results. The tool supports various backends including HuggingFace and vLLM models.
sglang
メタSGLang is a high-performance LLM serving framework that specializes in fast, structured generation for JSON, regex, and agentic workflows using its RadixAttention prefix caching. It delivers significantly faster inference, especially for tasks with repeated prefixes, making it ideal for complex, structured outputs and multi-turn conversations. Choose SGLang over alternatives like vLLM when you need constrained decoding or are building applications with extensive prefix sharing.
cloudflare-turnstile
メタThis skill provides comprehensive guidance for implementing Cloudflare Turnstile as a CAPTCHA-alternative bot protection system. It covers integration for forms, login pages, API endpoints, and frameworks like React/Next.js/Hono, while handling invisible challenges that maintain user experience. Use it when migrating from reCAPTCHA, debugging error codes, or implementing token validation and E2E tests.