tour
Friendly onboarding tour of Claude Code capabilities for users asking what it can do.
Best use case
tour is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Friendly onboarding tour of Claude Code capabilities for users asking what it can do.
Teams using tour should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/tour/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How tour Compares
| Feature / Agent | tour | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Friendly onboarding tour of Claude Code capabilities for users asking what it can do.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Tour: What Can I Do? Friendly onboarding when users ask about capabilities. ## Triggers Activate when user says things like: - "what can you do?" - "what can I do?" - "help me get started" - "show me around" - "what features are available?" - "how does this work?" ## Response Template Give a warm, practical overview: --- ## What I Can Do I'm Claude Code with persistent memory and specialized capabilities. Here's what makes me useful: ### Code & Development - **Write & edit code** - any language, any framework - **Debug issues** - trace errors, find root causes - **Refactor** - improve structure without breaking things - **Test** - write and run tests, validate changes ### Memory & Context - **Remember across sessions** - learnings persist to SQLite/PostgreSQL - **Recall past work** - search what worked/failed before - **Handoffs** - create snapshots to resume complex work ### Research & Planning - **Explore codebases** - understand unfamiliar projects fast - **Plan implementations** - architect before coding - **Search the web** - find docs, solutions, best practices ### Specialized Agents I can spawn sub-agents for complex tasks: - `explorer` - map codebase structure - `kraken` - implement with TDD workflow - `debug` - investigate issues systematically ### Quick Tips - Ask naturally - I'll figure out which tools to use - Say "create a handoff" before ending sessions - Say "what worked for X before?" to recall past learnings **What would you like to work on?** --- ## Style Notes - Be welcoming, not overwhelming - Focus on practical value, not feature lists - End with an invitation to start working - Don't list every skill - highlight categories
Related Skills
contour-integrals
Problem-solving strategies for contour integrals in complex analysis
workflow-router
Goal-based workflow orchestration - routes tasks to specialist agents based on user goals
wiring
Wiring Verification
websocket-patterns
Connection management, room patterns, reconnection strategies, message buffering, and binary protocol design.
visual-verdict
Screenshot comparison QA for frontend development. Takes a screenshot of the current implementation, scores it across multiple visual dimensions, and returns a structured PASS/REVISE/FAIL verdict with concrete fixes. Use when implementing UI from a design reference or verifying visual correctness.
verification-loop
Comprehensive verification system covering build, types, lint, tests, security, and diff review before a PR.
vector-db-patterns
Embedding strategies, ANN algorithms, hybrid search, RAG chunking strategies, and reranking for semantic search and retrieval.
variant-analysis
Find similar vulnerabilities across a codebase after discovering one instance. Uses pattern matching, AST search, Semgrep/CodeQL queries, and manual tracing to propagate findings. Adapted from Trail of Bits. Use after finding a bug to check if the same pattern exists elsewhere.
validate-agent
Validation agent that validates plan tech choices against current best practices
tracing-patterns
OpenTelemetry setup, span context propagation, sampling strategies, Jaeger queries
tldr-stats
Show full session token usage, costs, TLDR savings, and hook activity
tldr-router
Map code questions to the optimal tldr command by detecting intent and routing to the right analysis layer.