mcpbeat

Tutorial

apify/tutorial

Create structured tutorials for Apify Academy or Platform documentation. Use when user says "create a tutorial", "write a tutorial", "build a step-by-step guide", "convert this guide into a tutorial", or "tutorial for [topic]". Handles tutorial structure, learning objectives, prerequisites, step-by-step instructions, code examples, and troubleshooting sections.

2k tokens
context cost
the whole folder, loaded on every use
3
files
instructions only
0
copies elsewhere
how many repositories repackaged it
74
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/apify/apify-docs --skill tutorial

What comes with it

5 568 bytes besides the instruction
references/process.md
references/tutorial-template.md

The instruction itself

2 sections, as written by the author

Tutorial creation

Process

  • Identify tutorial type - platform tutorial, academy tutorial, or integration tutorial
  • Research - read related docs, check existing tutorials for style reference
  • Create front matter - title (sentence case), description (140-160 chars), sidebar_position, slug
  • Write 8-section structure:
  • Introduction with learning objectives
  • Prerequisites (tools, accounts, knowledge)
  • Step-by-step instructions (numbered, action verbs)
  • Code examples (complete, runnable, tested)
  • Testing and verification (expected results)
  • Troubleshooting (common issues + fixes)
  • Summary (what was learned)
  • Next steps (links to related content)
  • Quality check - run pnpm lint:md and vale before finishing

Each step should have a clear action verb, expected result, and verification. Code examples must be complete - no pseudocode.

For the detailed 8-section template, see .agents/skills/tutorial/references/tutorial-template.md.

For edge cases and process notes, see .agents/skills/tutorial/references/process.md.

How to use it

Copy the folder

Take apify/tutorial from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.