TU

tutorial-engineer

Transforms code and features into structured, educational content and tutorials for developers.

Install

mkdir -p .claude/skills/tutorial-engineer && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/2185" && unzip -o skill.zip -d .claude/skills/tutorial-engineer && rm skill.zip

Installs to .claude/skills/tutorial-engineer

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Creates step-by-step tutorials and educational content from code. Transforms complex concepts into progressive learning experiences with hands-on examples.
155 charsno explicit “when” trigger
Intermediate

Key capabilities

  • →Deconstructs complex logic into learning sequences
  • →Predicts common student errors
  • →Structures hands-on exercises
  • →Adapts content for progressive disclosure

How it works

It applies pedagogical design patterns to organize technical content into progressive stages, emphasizing active practice over passive reading.

Inputs & outputs

You give it
Technical source code or feature documentation
You get back
Step-by-step tutorial modules with exercises

When to use tutorial-engineer

  • →Creating an onboarding guide for new developers
  • →Writing a feature tutorial for a library
  • →Transforming code into a workshop exercise
  • →Documenting concepts with hands-on examples

About this skill

Tutorial Engineer

Turn a specific codebase or feature into a progressive, hands-on tutorial. Preserve the useful teaching sequence: show a worked example, guide practice, then give an independent challenge.

When to Use

  • Explain code through a tutorial, onboarding exercise, workshop or cookbook recipe.
  • Convert a feature into a learning path with measurable outcomes and checkpoints.
  • Improve a tutorial whose setup, pacing or examples prevent readers from finishing.

Use reference-documentation workflows for exhaustive API listings and marketing workflows for promotional copy.

Inputs and Scope

Resolve the topic/source code, audience’s prerequisite knowledge, desired outcome, runtime/version, format and time constraint. Infer available facts from the request; ask only essential unanswered questions. State assumptions. Do not invent exact completion times or performance/retention improvements. Use the project’s actual supported environment, rather than installing the latest release by default.

Procedure

  1. Define an observable objective: “After this tutorial, the reader can build/debug X and verify Y.” Identify what remains outside scope.
  2. Inspect the actual source and primary docs. Record versions and permissions. Prepare an isolated local sandbox with synthetic fixtures; explain any install, credential, cloud-cost or cleanup effect before the reader encounters it.
  3. Map prerequisites into a sequence. Introduce one new idea at a time; link an optional primer for background. Label architecture diagrams and pseudocode as such.
  4. Start with the smallest complete example. Include its filename, imports, run command, expected result and supported versions. Explain non-obvious lines and why the approach works.
  5. Add guided practice with a checkpoint after each material change. Specify observable state, not “it should work.” For deliberate errors, mark them clearly and show the exact recovery path.
  6. Add an independent challenge with requirements, hints, a solution and success criteria. Keep the answer separate so readers can attempt it first.
  7. Verify examples in order from a fresh authorized environment when feasible. Distinguish executed checks from static inspection and untested snippets. Do not claim screenshots, links or code were tested without evidence. A blocked environment is a reported limitation.
  8. Close with the demonstrated outcome, unresolved limitations and concrete next steps. Deliver the tutorial artifact when requested; publishing or sending it is a separate authorized action.

Worked Example

For a beginner learning filtering, use a local file with no dependencies or network access:

# active_users.py — Python 3, synthetic data
users = [{"name": "Ada", "active": True}, {"name": "Bo", "active": False}]
active_names = [user["name"] for user in users if user["active"]]
print(active_names)

Run python3 active_users.py. Expected output: ['Ada'].

Explain that the condition retains only active records and the expression selects their names. Guided practice: add an active user named Cy; checkpoint output is ['Ada', 'Cy']. Challenge: produce the inactive names instead; expected output is ['Bo']. Edge check: an empty input must produce []. This is an illustrative teaching example; actual execution is not asserted by this document.

Output Contract

Produce Markdown with:

  • Title, observable objectives, audience, prerequisites and an estimated time explicitly labeled as an estimate.
  • Setup with versions, filenames, commands and cleanup instructions for the isolated environment.
  • Ordered concept → example → practice sections with expected outputs.
  • An independent challenge, hints and a separate solution.
  • Troubleshooting table mapping error → likely cause → verified recovery.
  • Validation evidence (environment, commands, results), untested items and limitations.
  • Next steps and primary-source links actually consulted.

Use hierarchical headings, meaningful image alt text and text labels alongside color. Keep code readable; split long examples into named files rather than hiding required lines.

Teaching Patterns

Use worked examples, practice, feedback, revisiting earlier concepts and familiar analogies as design choices. Their effects depend on the audience and task; do not attach unsupported retention percentages or promise a fixed speed improvement. Time estimates should come from a pilot or be labeled provisional. Avoid presenting fixed “learning styles” as a diagnosis of an individual learner.

Quality Checks

  • Each objective maps to a checkpoint or exercise.
  • No required setup appears only halfway through.
  • Required examples are complete; fragments and pseudocode are labeled.
  • Deliberate errors cannot modify production data, publish content or expose secrets.
  • Expected output matches the synthetic fixture and stated version.
  • Install and API examples come from current trusted sources; secrets stay outside tutorial files and recordings.
  • A novice can follow the sequence without missing concepts. If no audience pilot occurred, state that limitation.

Limitations

  • A tutorial is not exhaustive API reference or evidence of production readiness.
  • Static review does not establish runtime correctness, pedagogy outcomes or accessibility conformance.
  • Exact tool behavior and setup depend on the user’s environment; report unresolved dependencies and checks honestly.

When not to use it

  • →API reference documentation
  • →Marketing or promotional copy

Limitations

  • →Cannot generate creative visual assets
  • →Requires clear source material to function well

How it compares

It focuses on the learner's journey and error prevention rather than just technical accuracy.

Compared to similar skills

tutorial-engineer side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
tutorial-engineer (this skill)57moNo flagsIntermediate
docs-write229moNo flagsBeginner
content-research-writer151yNo flagsBeginner
doc-coauthoring1611moNo flagsBeginner

Try saying

Example prompts that trigger this skill in your AI assistant.

mobile-design

sickn33

Mobile-first design and engineering doctrine for iOS and Android apps. Covers touch interaction, performance, platform conventions, offline behavior, and mobile-specific decision-making. Teaches principles and constraints, not fixed layouts. Use for React Native, Flutter, or native mobile apps.

149231

unity-developer

sickn33

Build Unity games with optimized C# scripts, efficient rendering, and proper asset management. Masters Unity 6 LTS, URP/HDRP pipelines, and cross-platform deployment. Handles gameplay systems, UI implementation, and platform optimization. Use PROACTIVELY for Unity performance issues, game mechanics, or cross-platform builds.

142357

architect-review

sickn33

Master software architect specializing in modern architecture patterns, clean architecture, microservices, event-driven systems, and DDD. Reviews system designs and code changes for architectural integrity, scalability, and maintainability. Use PROACTIVELY for architectural decisions.

109320

angular

sickn33

Modern Angular (v20+) expert with deep knowledge of Signals, Standalone Components, Zoneless applications, SSR/Hydration, and reactive patterns. Use PROACTIVELY for Angular development, component architecture, state management, performance optimization, and migration to modern patterns.

100129

frontend-slides

sickn33

Create stunning, animation-rich HTML presentations from scratch or by converting PowerPoint files. Use when the user wants to build a presentation, convert a PPT/PPTX to web, or create slides for a talk/pitch. Helps non-designers discover their aesthetic through visual exploration rather than abstract choices.

95195

minecraft-bukkit-pro

sickn33

Master Minecraft server plugin development with Bukkit, Spigot, and Paper APIs. Specializes in event-driven architecture, command systems, world manipulation, player management, and performance optimization. Use PROACTIVELY for plugin architecture, gameplay mechanics, server-side features, or cross-version compatibility.

9078

You might also like

docs-write

metabase

Write documentation following Metabase's conversational, clear, and user-focused style. Use when creating or editing documentation files (markdown, MDX, etc.).

22139

content-research-writer

ComposioHQ

Assists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section. Transforms your writing process from solo effort to collaborative partnership.

15111

doc-coauthoring

anthropics

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

1686

research-grants

davila7

Write competitive research proposals for NSF, NIH, DOE, and DARPA. Agency-specific formatting, review criteria, budget preparation, broader impacts, significance statements, innovation narratives, and compliance with submission requirements.

694

teams-channel-post-writer

daymade

Creates educational Teams channel posts for internal knowledge sharing about Claude Code features, tools, and best practices. Applies when writing posts, announcements, or documentation to teach colleagues effective Claude Code usage, announce new features, share productivity tips, or document lessons learned. Provides templates, writing guidelines, and structured approaches emphasizing concrete examples, underlying principles, and connections to best practices like context engineering. Activates for content involving Teams posts, channel announcements, feature documentation, or tip sharing.

591

write-docs

tldraw

Writing SDK documentation for tldraw. Use when creating new documentation articles, updating existing docs, or when documentation writing guidance is needed. Applies to docs in apps/docs/content/.

665

Search skills

Search the agent skills registry