スキル Tutorial Engineer
📦

Tutorial Engineer

安全

Create Step-by-Step Developer Tutorials

Developers struggle to create effective learning materials that transform complex concepts into digestible lessons. This skill applies pedagogical design principles to generate progressive tutorials with hands-on exercises that build confidence.

対応: Claude Codex Code(CC)
🥉 72 ブロンズ
1

スキルZIPをダウンロード

2

Claudeでアップロード

設定 → 機能 → スキル → スキルをアップロードへ移動

3

オンにして利用開始

テストする

「Tutorial Engineer」を使用しています。 Create a quick start for a REST API client library

期待される結果:

A structured tutorial with installation steps, authentication setup, basic GET request example, error handling pattern, and links to advanced topics like rate limiting and webhooks.

「Tutorial Engineer」を使用しています。 Generate exercises for learning async/await patterns

期待される結果:

Progressive exercises starting with callback-to-promise conversion, advancing through async function refactoring, parallel execution patterns, and error handling in async contexts.

「Tutorial Engineer」を使用しています。 Review tutorial for database connection pooling

期待される結果:

Quality assessment identifying missing prerequisite about database connections, suggesting addition of connection lifecycle diagram, and recommending troubleshooting section for common pool exhaustion errors.

セキュリティ監査

安全
v1 • 2/25/2026

This is a prompt-only skill with no executable code. Static analysis scanned 0 files and detected 0 security issues. The skill provides instructional guidance for creating educational tutorials and contains no network access, filesystem operations, or external command execution. No security concerns identified.

0
スキャンされたファイル
0
解析された行数
0
検出結果
1
総監査数
セキュリティ問題は見つかりませんでした
監査者: claude

品質スコア

38
アーキテクチャ
100
保守性
87
コンテンツ
50
コミュニティ
100
セキュリティ
74
仕様準拠

作れるもの

API Onboarding Guide

Generate comprehensive onboarding documentation for new API users with progressive examples from authentication to advanced features.

Feature Tutorial Series

Create multi-part tutorial workshops that teach complex features through incremental, hands-on exercises with built-in checkpoints.

Code Migration Guide

Transform migration documentation into step-by-step tutorials with before/after examples and troubleshooting for common issues.

これらのプロンプトを試す

Quick Start Tutorial
Create a 5-minute quick start tutorial for [TOPIC]. Include: what users will learn, prerequisites, time estimate, a minimal working example, and next steps for deeper learning.
Deep Dive Tutorial
Create a comprehensive 45-minute tutorial for [TOPIC]. Structure with: learning objectives, concept introduction with analogies, minimal example, guided practice steps, variations, challenges, and troubleshooting section.
Exercise Generator
Generate 5 hands-on exercises for [CONCEPT] that progress in difficulty: 1 fill-in-the-blank, 1 debug challenge, 2 extension tasks, and 1 from-scratch build. Include solutions in collapsible sections.
Tutorial Quality Review
Review this tutorial draft against the quality checklist: Can beginners follow without getting stuck? Are concepts introduced before use? Is each example complete and runnable? Are common errors addressed? Suggest specific improvements.

ベストプラクティス

  • Define measurable learning objectives before writing any content
  • Introduce concepts before using them in code examples
  • Include frequent validation checkpoints where readers run and verify their code

回避

  • Assuming knowledge that beginners may not have without stating prerequisites
  • Showing incomplete code snippets that cannot be executed independently
  • Introducing multiple new concepts in a single step without isolation

よくある質問

What makes a good tutorial structure?
A good tutorial opens with clear learning objectives and prerequisites, progresses through concepts in logical order with hands-on examples, includes troubleshooting for common errors, and closes with next steps for continued learning.
How long should a tutorial be?
Tutorial length depends on complexity. Quick starts should take 5 minutes, standard tutorials 15-30 minutes, and comprehensive deep dives 45-60 minutes. Break longer content into a workshop series.
Should I include theory or just code?
Balance both. Introduce theory with real-world analogies before code examples, then demonstrate with minimal working code. Explain the why behind each step, not just the how.
How do I handle prerequisite knowledge?
State prerequisites clearly in the opening section. Link to prerequisite tutorials when possible. Consider creating a learning path that sequences multiple tutorials in dependency order.
What exercise types work best for developers?
Mix exercise types: fill-in-the-blank for syntax patterns, debug challenges for problem-solving, extension tasks for creativity, and from-scratch builds for synthesis. Always provide solutions.
How do I make tutorials accessible to different learning styles?
Support multiple modalities: code examples for textual learners, diagrams for visual learners, hands-on exercises for kinesthetic learners, and explain concepts from multiple angles.

開発者の詳細

ファイル構成

📄 SKILL.md