learning-path-builder
Creates personalized learning paths for technologies, frameworks, or concepts. Use for user-interactive session only for onboarding new technologies, hackathon skill-building, or personal development planning. Not for use in automated development or investigation. Sequences resources (docs, tutorials, exercises) based on current skill level and learning goals. Adapts to learning style: hands-on, theory-first, project-based.
What this skill does
# Learning Path Builder Skill ## Purpose This skill creates personalized, structured learning paths that guide users through mastering new technologies, frameworks, or concepts. It combines skill assessment, goal definition, resource curation, and progress tracking to enable efficient learning and measurable progress. ## When to Use This Skill - **New Technology Adoption**: Learning a new framework, language, or tool - **Onboarding**: Bringing team members up to speed on project technologies - **Hackathon Preparation**: Building required skills before a competition - **Career Development**: Structured path for advancing in a particular domain - **Knowledge Gaps**: Filling specific skill gaps in your technical stack - **Upskilling**: Transitioning from one technology to another - **Learning Optimization**: Creating efficient paths tailored to your learning style ## Core Philosophy: Personalized Progressive Learning **Assessment** → **Goal Setting** → **Path Sequencing** → **Resource Curation** → **Progress Tracking** → **Adaptation** A good learning path: - Matches current skill level (beginner, intermediate, advanced) - Aligns with learning goals and timeline - Sequences concepts from simple to complex - Mixes multiple resource types (docs, tutorials, exercises, projects) - Provides checkpoints and milestones - Adapts to learning style and feedback ## Learning Path Components Every personalized learning path includes: ### 1. Skills Assessment - Current skill level (beginner/intermediate/advanced) - Relevant prior knowledge - Learning experience preference - Time availability - Career/project goals ### 2. Goal Definition - Primary learning objective - Target proficiency level - Timeline and milestones - Success metrics - Constraints and dependencies ### 3. Concept Sequence - Prerequisite concepts - Progressive complexity levels - Learning foundations first - Builds practical understanding over time ### 4. Resource Curation - Official documentation - High-quality tutorials - Interactive exercises - Real-world projects - Community resources ### 5. Learning Checkpoints - Milestone assessments - Practical exercises - Mini-projects - Reflection points - Progress validation ### 6. Progress Tracking - Completed modules - Assessed skill gains - Time investment - Confidence levels - Feedback integration ## Step-by-Step Assessment Process ### Step 1: Assess Current Skill Level Ask targeted questions to understand: 1. **Technical Background** - Languages/frameworks you already know - Similar technologies you've used - Years of programming experience - Relevant professional experience 2. **Learning Style Preference** - Hands-on (learn by doing) - Theory-first (understand concepts) - Project-based (learn via real problems) - Visual (diagrams, videos) - Reading (documentation, blogs) 3. **Time Availability** - Hours per week available - Preferred learning schedule - Commitment timeline - Flexibility (can vary per week) 4. **Current Knowledge Gaps** - What specifically needs to be learned - Existing knowledge in adjacent areas - Misconceptions to address - Prior learning attempts ### Step 2: Define Clear Learning Goals Establish SMART goals: 1. **Specific**: What exactly will you be able to do? 2. **Measurable**: How will you know you've succeeded? 3. **Achievable**: Is this realistic given your timeline? 4. **Relevant**: How does this align with career/project needs? 5. **Time-bound**: When do you want to achieve this? ### Step 3: Sequence Concepts Progressively Create learning sequence from foundations to advanced: 1. **Foundation Concepts** (Week 1-2) - Core terminology - Basic architecture - Key principles - Simple examples 2. **Core Functionality** (Week 2-4) - Main features - Common patterns - Practical exercises - Real examples 3. **Advanced Topics** (Week 4+) - Complex scenarios - Performance optimization - Best practices - Production deployment 4. **Specialization** (As needed) - Domain-specific knowledge - Integration patterns - Advanced debugging - Expert techniques ### Step 4: Curate High-Quality Resources For each concept, provide: 1. **Official Documentation** - Links to relevant docs - Specific sections to focus on - Time estimates - Difficulty level 2. **Tutorials and Guides** - Author/source credibility - Format (text, video, interactive) - Hands-on vs theoretical - Time to complete 3. **Interactive Exercises** - Practice problems - Coding exercises - Interactive sandboxes - Difficulty progression 4. **Real-World Projects** - Beginner projects (1-2 days) - Intermediate projects (1-2 weeks) - Advanced projects (2+ weeks) - Open-source contributions 5. **Community Resources** - Forums and Q&A sites - Blogs and articles - Videos and screencasts - Podcasts and talks ### Step 5: Define Checkpoints and Milestones Establish clear progress markers: 1. **Knowledge Checkpoints** - Quiz or self-assessment - Concept understanding verification - Time to complete 2. **Practical Exercises** - Hands-on coding tasks - Expected time - Success criteria - Difficulty level 3. **Mini-Projects** - Build something meaningful - Combine multiple concepts - Realistic scenario - Review guidelines 4. **Milestone Assessments** - Comprehensive projects - Demonstrate proficiency - Clear success criteria - Feedback mechanism ### Step 6: Plan Progress Tracking Setup mechanism for tracking: 1. **Weekly Check-ins** - Resources completed - Concepts mastered - Challenges encountered - Time spent 2. **Skill Validation** - Self-assessment - Quiz scores - Project quality - Peer review 3. **Timeline Adjustment** - Accelerate if on track - Extend if needed - Adapt based on feedback - Celebrate milestones ## Learning Path Template ```markdown # [Technology] Learning Path ## Assessment ### Your Profile - **Current Skill Level**: [Beginner/Intermediate/Advanced] - **Learning Style**: [Hands-on/Theory/Project-based/Mix] - **Time Available**: [X hours/week] - **Prior Experience**: [Relevant technologies] ### Goals - **Primary Objective**: [What you'll be able to do] - **Target Level**: [Beginner/Intermediate/Advanced proficiency] - **Timeline**: [X weeks] - **Success Criteria**: [Measurable outcomes] ## Concept Sequence ### Foundation (Week 1) **Concepts**: Core terminology, basic architecture, key principles **Resources**: 1. [Resource Title](link) - X hour read/watch 2. [Interactive Exercise](link) - X hours hands-on 3. **Checkpoint**: Take quiz or build minimal example ### Core Functionality (Week 2-3) **Concepts**: Main features, common patterns, real-world usage **Resources**: 1. [Tutorial](link) - X hours 2. [Project](link) - Build working application 3. **Checkpoint**: Code review or project demo ### Advanced Topics (Week 4+) **Concepts**: Complex scenarios, optimization, production patterns **Resources**: 1. [Advanced Guide](link) - X hours 2. [Real Project](link) - Tackle open-source or real problem 3. **Checkpoint**: Implement advanced feature or optimization ## Progress Tracking | Week | Topic | Resource | Status | Time | Notes | | ---- | -------------- | ------------------ | ----------- | ---- | -------------------- | | 1 | Foundations | Docs + Tutorial | In Progress | 5h | Good grasp of basics | | 2 | Core Feature A | Exercise + Project | Pending | 0h | Not started | ## Next Steps - Start Week 1 resources - Join community (Discord/Forums) - Set up development environment ``` ## Learning Path Examples ### Example 1: React Learning Path (Beginner to Intermediate) ``` # React Learning Path - 4 Weeks ## Assessment - **Current Level**: Intermediate JavaScript - **Learning Style**: Hands-on with theory
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.