tutorial
Skill84 starsChanged 47 days agoApache-2.0View on GitHub
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.
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 10 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Distinctive: line 13
Research: - read related docs, check existing tutorials for style reference
- Very specific: line 24
Quality check: - run pnpm lint:md and vale before finishing
“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Tutorial creation
Process
- Identify tutorial type - platform tutorial, academy tutorial, or integration tutorial
- Research - read related docs, check existing tutorials for style reference
- Create frontmatter - 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:mdandvalebefore 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.
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- Q00/ouroboros★ 6.3ksame name
- agenticnotetaking/arscontexta★ 3.5ksame name
- bitwize-music-studio/claude-ai-music-skills★ 589same name
- me2resh/apexyard★ 532same name
- egregore-labs/egregore★ 293same name
- renatoworks/strudel-claude★ 61same name
- aayushostwal/nexus★ 19same name
- NoaiRox/specialist-agent★ 2same name
- LilithLabs/lilith★ 1same name
- Ivan-n-Beliaev/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Used alongsideProjects with it also use update and commit.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
AnthropicSkillupdate
Sync tasks and refresh memory from your current activity. Use when pulling new assignments from your project tracker into TASKS.md, triaging stale or overdue tasks, filling memory gaps for unknown people or projects, or running a comprehensive scan to catch todos buried in chat and email.
Also in 3 projects that use this
SentrySkillcommit
Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.
Also in 3 projects that use this
In this repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/api-documentation.mdcCursor rule
- .cursor/rules/content-formatting.mdcCursor rule
- .cursor/rules/documentation-style.mdcCursor rule
- api-docSkill
- doc-writeSkill
- review-docsSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

