Teach me
Delivers structured, paced VergeOS training modules (agent, fundamentals, vms, networking) grounded in official docs, as preparation before /quiz-me. Use when someone wants to learn or study a VergeOS topic. Applies to "teach me VergeOS networking", "I want to learn about tenants", "train me on VM management", "help me study fundamentals", "onboard me to the support agent". Returns topic-by-topic lessons with key points, support context, quick references, and cited sources.From its SKILL.md
npx -y skills add verge-io/agent-skills-vergeos --skill teach-meAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
6.2 KB, as published. Nobody here has run it
VergeOS Training: $ARGUMENTS
This skill provides structured learning content for VergeOS support engineers. Use this to learn concepts before testing your knowledge with /quiz-me.
Step 1: Module Selection
Based on the argument "$ARGUMENTS", route to the appropriate training module:
| Module | Description |
|---|---|
agent | How to use this support agent, skills, and workflows |
fundamentals | Platform architecture, tenants, nodes, clusters |
vms | VM creation, VirtIO, imports, snapshots, migration |
networking | VLANs, internal/external networks, firewall, routing |
If no argument or invalid argument: Use AskUserQuestion to present available modules:
- Header: "Module"
- Question: "Which training module would you like to learn?"
- Options: agent, fundamentals, vms, networking
Step 2: Fetch Current Documentation
Use VergeOS Docs MCP to gather authoritative content for the selected module. For the agent module, read local repository files instead.
For agent (read local files, not VergeOS Docs):
- Read:
CLAUDE.md(main agent configuration and guidelines) - Read:
.claude/skills/*/SKILL.md(all available skills) - Read:
agents/*/README.mdoragents/*/*.md(specialist agent documentation) - Read:
templates/directory contents (response templates)
For fundamentals:
- Query:
mcp__vergeos-docs__searchDocumentationwith "VergeOS architecture overview" - Query:
mcp__vergeos-docs__searchDocumentationwith "VergeOS tenant" - Query:
mcp__vergeos-docs__searchDocumentationwith "VergeOS cluster nodes" - Query:
mcp__vergeos-docs__searchDocumentationwith "VergeOS multi-tier"
For vms:
- Query:
mcp__vergeos-docs__searchDocumentationwith "VergeOS create virtual machine" - Query:
mcp__vergeos-docs__searchDocumentationwith "VergeOS VirtIO drivers" - Query:
mcp__vergeos-docs__searchDocumentationwith "VergeOS import VM" - Query:
mcp__vergeos-docs__searchDocumentationwith "VergeOS VM snapshots"
For networking:
- Query:
mcp__vergeos-docs__searchDocumentationwith "VergeOS network configuration" - Query:
mcp__vergeos-docs__searchDocumentationwith "VergeOS VLAN" - Query:
mcp__vergeos-docs__searchDocumentationwith "VergeOS firewall rules" - Query:
mcp__vergeos-docs__searchDocumentationwith "VergeOS network troubleshooting"
Step 3: Present Learning Content
For each topic in the module, provide structured educational content:
agent - 5 topics:
- Agent overview and purpose
- Available skills and when to use them
- Using VergeOS Docs MCP effectively
- Specialist agents for domain-specific tasks
- Best practices and workflow tips
fundamentals - 5 topics:
- VergeOS architecture and hyperconvergence
- Tenant concepts and isolation
- Node roles (controller vs compute)
- Cluster configuration
- Multi-tier environments
vms - 5 topics:
- VM creation process
- VirtIO drivers and guest agent
- VM import methods (P2V, V2V, VMware)
- Snapshots and cloning
- VM migration and HA
networking - 5 topics:
- Network types (internal, external, VLAN)
- VXLAN transport
- VLAN configuration
- Firewall rules and NAT
- Network troubleshooting
Step 4: Content Format for Each Topic
Present each topic using this structure:
---
## Topic [N] of 5: [Topic Name]
### What It Is
[1-2 sentence definition of the concept]
### Key Points
- [Important fact 1 from documentation]
- [Important fact 2 from documentation]
- [Important fact 3 from documentation]
- [Important fact 4 from documentation]
### How It Works
[Brief technical explanation - 2-3 sentences]
### In Support Context
[When you'll encounter this, common customer questions]
### Quick Reference
- **UI Path** or **Command**: [Where to find in UI, or skill/command to use]
- **Related Concepts**: [Connected features to understand]
**Source**: [Documentation URL or repository file path]
---
Step 5: Interactive Pacing
After presenting each topic:
-
Pause for comprehension - Use AskUserQuestion:
- Header: "Continue?"
- Question: "Ready for the next topic, or would you like me to expand on anything?"
- Options:
- "Next topic" (default)
- "Expand on this"
- "Skip to summary"
-
If "Expand on this": Provide additional detail from VergeOS Docs documentation, including:
- Step-by-step procedures
- Common pitfalls
- Real support scenarios
-
If "Skip to summary": Jump to Step 6
Step 6: Module Summary
After all 5 topics, provide:
-
Key Takeaways: 5 bullet points summarizing the most critical information
-
Common Support Scenarios: 3 realistic situations where this knowledge applies
-
Test Your Knowledge (for VergeOS modules only):
Ready to test what you've learned? Run `/quiz-me [module]` to take a 5-question quiz.Note: The agent module does not have a quiz - practice by using the skills!
-
Documentation References: List all documentation URLs used
-
Suggested Next Module:
- After agent: "Now learn VergeOS concepts with
/teach-me fundamentals" - After fundamentals: "Continue your learning with
/teach-me vms" - After vms: "Continue your learning with
/teach-me networking" - After networking: "You've completed the core training modules!"
- After agent: "Now learn VergeOS concepts with
Important Guidelines
- Base all content on authoritative sources - Use VergeOS Docs for VergeOS modules, local repository files for the agent module. Never invent features or behaviors
- Keep explanations practical - Focus on what support engineers need to know
- Include specific UI paths and commands where available
- Highlight common customer issues related to each topic
- Always cite documentation sources with URLs
- Connect concepts to support scenarios and ticket resolution