neomatrix369/learning-opportunity
Progressive concept teaching through three depth levels (Core → Mechanics → Deep Dive). Creates diagrams, provides annotated code walkthroughs from the current codebase, and builds explanations from fundamentals to production internals. Triggers: "teach me about [pattern/concept]", "how does [architecture/pattern] work", "walk me through [this implementation]", "tutorial on [concept]", "deep dive into [system/pattern]", "help me understand [this design]" Use when: user requests multi-level learning about code patterns, architecture, or implementation mechanics with checkpoint-based progression. Not for: quick answers, single-sentence explanations, code fixes, or "what does this line do" questions—those are standard assistance.
98
Quality
100%
Does it follow best practices?
Impact
97%
1.44xAverage score across 5 eval scenarios
task.mdevals/scenario-5/
Task: Visualization Selection
Context
You need to choose appropriate diagram types for different teaching scenarios.
Guidelines from skill documentation:
- ASCII: Default for simple flows, call stacks, basic sequences
- Mermaid: For static structures, multi-component relationships, architecture diagrams
- Animated SVG: For temporal/causal flows, sequences with time dimension, data transformations over time
Test Cases
Test Case A: Simple Function Call Flow
User message: "walk me through how this authentication function works"
Context: The function is a simple 5-step process: validate input → hash password → query database → generate token → return response.
Provide Level 1 response. What visualization type do you choose and why?
Test Case B: Microservices Architecture
User message: "explain our microservices architecture"
Context: The system has 6 services (API Gateway, Auth, Users, Orders, Payments, Notifications) with various dependencies between them.
Provide Level 1 response. What visualization type do you choose and why?
Test Case C: Request Pipeline with Transformations
User message: "how does our data pipeline process events?"
Context: Events go through: Ingestion → Validation → Enrichment → Transformation → Storage → Notification. Each stage modifies the data structure and timing matters.
Provide Level 1 response. What visualization type do you choose and why?
Test Case D: Visualization Upgrade Decision
Previous context: You showed a simple ASCII diagram of a single service's request flow.
User follow-up: "now show me how this works when we have 5 microservices calling each other"
Provide your follow-up response. Do you upgrade the visualization? To what?
Install with Tessl CLI
npx tessl i neomatrix369/learning-opportunity@0.1.0evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5