Write a getting-started tutorial that takes a new user from install to a first working result
Scanned 9/3/2026
Install to Claude Code
npx -y skills add black141312/ada --skill tutorial --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Tutorial?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/black141312-tutorial)More formats (shields.io, HTML) on the badges page.
---
name: tutorial
description: Write a getting-started tutorial that takes a new user from install to a first working result
category: docs
---
# Tutorial
Use this to create a guided, linear walkthrough that gets a newcomer to a small success quickly. Unlike reference docs, a tutorial is a single happy path the reader follows top to bottom.
1. Pick one concrete end goal a beginner can reach in 10-15 minutes ("send your first request", "render a page").
2. State prerequisites up front: tools, accounts, versions the reader must have.
3. Break the path into numbered steps; each step is one action with the exact command or code to paste.
4. After each step, show the expected output so the reader can confirm they're on track.
5. End with a working result, then a short "next steps" pointing to deeper docs.
6. Add a brief troubleshooting note for the one or two failures beginners actually hit.
7. Run the whole tutorial from a clean environment yourself and fix anything that doesn't work verbatim.
## Rules
- One linear happy path — defer options, edge cases, and theory to reference docs.
- Every code block must be copy-pasteable and produce the shown output.
- Show expected output after steps so readers can self-correct.
- Test it end to end from a fresh setup; a tutorial that fails at step 3 is worse than none.
- Keep prerequisites honest and minimal; don't assume tools the reader hasn't installed.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Recovers prior coding-agent session context by running `catchup <agent> --since-compact`, which extracts a clean summary of a previous Codex, Claude Code, Antigravity, OpenCode, or Pi Agent session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", or asks to recover/summarize a previous session before continuing. Do NOT use for the current conversation, git history, or any non-agent log.