Find why your productivity system keeps failing, then apply the smallest fix — capacity math, bottleneck routing, durable local notes.
Coding
Learning Growth Coach
Try itDiagnose skill bottlenecks and turn practice logs into a targeted next session.
What it does
A structured coach for human skill development. Provide your skill goal, recent practice logs, and constraints; it identifies the bottleneck, proposes a deliberate-practice plan with concrete metrics, and designs the next session. Tracks progress through defined milestones, quality scores, and skill-level estimates on a 1–10 scale, with weekly reviews that flag plateaus and recommend method adjustments.
When to use it
- Setting measurable milestones when starting a new skill
- Diagnosing why progress has stalled on a skill
- Designing a deliberate-practice plan for the coming week
- Comparing your weekly pace against personal benchmarks
The skill document
Self-Improving Skill
Systematic skill development with measurable progress tracking, bottleneck identification, and personalized practice optimization. Transforms vague "practice more" into targeted, evidence-based skill growth.
Quick Reference
| Situation | Action |
|---|---|
| Starting a new skill | Define skill parameters, set milestones, create practice log |
| After practice session | Log duration, quality score, focus areas, difficulties |
| Feeling stuck or plateauing | Analyze progress curve, identify bottlenecks, adjust methods |
| Comparing with benchmarks | Check skill level vs. industry standards or personal goals |
| Preparing for assessment | Review weak areas, targeted practice, mock tests |
Core Concepts
Skill Parameters
- Skill Name: Programming (Python), Design (UI/UX), Language (English), Instrument (Guitar)
- Difficulty Level: Beginner (1-3), Intermediate (4-6), Advanced (7-9), Expert (10)
- Milestones: Concrete, measurable achievements (e.g., "Build a CRUD app", "Design 10 screens")
- Practice Frequency: Daily, 3x/week, Weekly, as needed
Progress Metrics
- Time Investment: Practice hours per week, consistency streak
- Quality Score: 1-10 self-assessment of session quality
- Skill Level: Estimated proficiency (1-10) based on output quality
- Confidence: Self-rated confidence in applying the skill (1-10)
Logging Format
Skill Definition Entry (create once)
Append to .learnings/skills/SKILL_NAME.md:
## [SKL-YYYYMMDD-001] Skill Definition: Python Programming
**Defined**: 2026-03-12T10:00:00Z
**Current Level**: 4/10 (Intermediate)
**Target Level**: 7/10 (Advanced)
**Target Date**: 2026-06-30
**Priority**: high
**Status**: active
### Milestones
1. [ ] Complete Python crash course (by 2026-03-31)
2. [ ] Build 3 small projects (by 2026-04-30)
3. [ ] Contribute to open source (by 2026-05-31)
4. [ ] Land freelance project (by 2026-06-30)
### Resources
- Courses: Python for Everybody, Real Python
- Books: Fluent Python, Python Cookbook
- Practice: LeetCode, Codewars, Project Euler
### Baseline Assessment
- Data structures: 3/10
- Algorithms: 2/10
- Web frameworks: 1/10
- Testing: 1/10
- Debugging: 4/10
---
Practice Session Entry (log after each session)
Append to .learnings/skills/SKILL_NAME.md:
## [PRC-YYYYMMDD-001] Practice Session
**Logged**: 2026-03-12T10:30:00Z
**Duration**: 45 minutes
**Quality Score**: 7/10
**Focus Areas**: list comprehensions, error handling
**Energy Level**: 6/10
**Distractions**: low
### What I Practiced
- List comprehensions vs. for loops
- Try/except blocks for error handling
- Writing cleaner function signatures
### Challenges & Breakthroughs
- Challenge: Understanding when to use list comprehensions
- Breakthrough: Realized they're best for simple transformations
- Still confused: Complex nested comprehensions
### Key Insights
- List comprehensions are 20-30% faster for simple operations
- Specific exceptions (ValueError) better than generic except
- Function should do one thing well (Single Responsibility)
### Next Session Focus
- Nested list comprehensions
- Custom exception classes
- Function decorators basics
### Metrics Update
- Data structures: 3 → 4/10
- Confidence: 5 → 6/10
---
Progress Review Entry (weekly/monthly)
Append to .learnings/skills/SKILL_NAME_REVIEWS.md:
## [REV-YYYYMMDD-001] Weekly Review
**Period**: 2026-03-05 to 2026-03-12
**Total Practice Time**: 5.5 hours
**Average Quality**: 6.8/10
**Consistency**: 6/7 days (86%)
**Milestones Progress**: 1/4 completed
### Progress Analysis
- **Fastest Improving**: Data structures (+1 point/week)
- **Slowest Improving**: Algorithms (+0.2 points/week)
- **Consistency**: Good, but weekend sessions shorter
- **Quality Trend**: Improving from 5.2 to 6.8 over 4 weeks
### Bottlenecks Identified
1. Algorithm complexity theory - need focused study
2. Weekend motivation drop - schedule morning sessions
3. Project application - start building sooner
### Adjustments for Next Week
1. Dedicate 2 hours to algorithm fundamentals
2. Join coding challenge group for accountability
3. Start small project (TODO app) to apply knowledge
### Comparison to Benchmarks
- My progress: 0.8 points/week average
- Typical progress: 0.5 points/week (I'm 60% faster)
- Expert trajectory: Would reach level 7 in 12 weeks at current rate
- Adjust target: From 12 to 10 weeks at current pace
---
Analysis & Insights
Progress Curve Analysis
Skill Level Over Time:
Week 1: 3.0 → Week 2: 3.5 → Week 3: 4.0 → Week 4: 4.5 → Week 5: 5.0
Plateau Detection
- Sign: 2+ weeks with <0.2 point improvement
- Causes: Insufficient challenge, poor practice quality, missing fundamentals
- Solutions: Increase difficulty, change methods, get feedback
Optimal Practice Patterns
- Frequency: 4-5 sessions/week better than 7 (avoids burnout)
- Duration: 45-90 minutes optimal (diminishing returns after)
- Spacing: Mix fundamentals (60%) with application (40%)
- Variety: Rotate between theory, exercises, projects, review
Improvement Strategies
For Beginners (Level 1-3)
- Focus: Fundamentals mastery, not breadth
- Resources: Structured courses with exercises
- Feedback: Regular code reviews or tutor sessions
- Mindset: Embrace struggle as learning signal
For Intermediate (Level 4-6)
- Focus: Application and pattern recognition
- Resources: Real projects, open source contribution
- Feedback: Peer review, user testing
- Mindset: Quality over quantity, deliberate practice
For Advanced (Level 7-9)
- Focus: Specialization and teaching
- Resources: Research papers, advanced courses
- Feedback: Conference talks, expert review
- Mindset: Contribution to field, mentoring others
Integration with Other Self-Improving Skills
With Self-Improving-Habit
- Use habit tracking for practice consistency
- Link skill sessions to daily routines
With Self-Improving-Learning
- Apply optimal learning techniques to skill acquisition
- Use spaced repetition for fundamentals
With Self-Improving-Work
- Connect skill development to career advancement
- Identify high-impact skills for your role
Automation & Tools
Quick Log Script
#!/bin/bash
# Quick skill practice log
echo "## [PRC-$(date +%Y%m%d)-001] Practice Session" >> .learnings/skills/$1.md
echo "**Logged**: $(date -Iseconds)Z" >> .learnings/skills/$1.md
echo "**Duration**: $2 minutes" >> .learnings/skills/$1.md
echo "**Quality Score**: $3/10" >> .learnings/skills/$1.md
echo "" >> .learnings/skills/$1.md
echo "### What I Practiced" >> .learnings/skills/$1.md
echo "- " >> .learnings/skills/$1.md
Progress Dashboard (Concept)
# Simple progress visualizer
import matplotlib.pyplot as plt
weeks = [1, 2, 3, 4, 5]
levels = [3.0, 3.5, 4.0, 4.5, 5.0]
plt.plot(weeks, levels, marker='o')
plt.title('Skill Progress Over Time')
plt.xlabel('Week')
plt.ylabel('Skill Level (1-10)')
plt.grid(True)
plt.show()
Common Pitfalls & Solutions
Pitfall 1: "Practice Without Progress"
- Symptom: Many hours logged, little improvement
- Cause: Comfort zone practice, no deliberate challenge
- Fix: Increase difficulty 10% each week, track specific metrics
Pitfall 2: "Too Many Skills at Once"
- Symptom: Slow progress across multiple skills
- Cause: Divided attention, context switching
- Fix: Focus on 1-2 primary skills, limit to 3 total
Pitfall 3: "No Feedback Loop"
- Symptom: Unaware of mistakes or better approaches
- Cause: Solo practice without external input
- Fix: Weekly review, find mentor, join community
Pitfall 4: "Inconsistent Practice"
- Symptom: Irregular sessions, forget between practices
- Cause: No schedule, low priority
- Fix: Time blocking, accountability partner, streak tracking
Success Metrics
Leading Indicators (Weekly)
- Practice consistency (days/week)
- Average session quality (1-10)
- Challenge level increase (%)
- Feedback received (pieces/week)
Lagging Indicators (Monthly)
- Skill level improvement (points/month)
- Project completion rate
- Assessment scores
- External recognition
Target Benchmarks
- Good: 0.5 points/month improvement
- Excellent: 1.0 points/month improvement
- Exceptional: 2.0+ points/month improvement
Getting Started
Step 1: Skill Definition
- Choose 1-2 skills to focus on
- Create skill definition entry
- Set realistic milestones (3-6 month horizon)
Step 2: First Week Setup
- Schedule practice sessions (calendar)
- Gather learning resources
- Establish baseline assessment
Step 3: Continuous Improvement
- Log every practice session
- Weekly review and adjustment
- Monthly milestone check-in
Source & Inspiration
Based on research into deliberate practice, skill acquisition science, and expert performance. Combines elements from:
- K. Anders Ericsson's "Deliberate Practice"
- Josh Kaufman's "First 20 Hours"
- Barbara Oakley's "Learning How to Learn"
- Dreyfus model of skill acquisition
Integration Note: This skill extends the self-improving-agent framework to skill-specific tracking while maintaining compatibility with the core learning system.
Questions people ask
- How does this differ from a generic learning helper?
- It is built around deliberate practice for a single skill at a time, using defined metrics — quality score, skill level, confidence — and a plateau threshold of under 0.2 points over two weeks.
- Can practice sessions be logged automatically?
- The document includes a bash script template that appends a session entry with date, duration, and quality score to a per-skill markdown file under .learnings/skills/.
- Does it modify the agent's own code?
- No. It targets human skill development — logging, bottleneck analysis, and practice planning — not changes to agent code.
Related skills
Stores durable facts in a categorized, plain-markdown vault on disk, alongside your agent's built-in memory.
Join a video meeting as an AI bot with voice, avatar, and screenshare across four operating modes.
Generate and edit Draw.io, Mermaid, and Excalidraw diagrams from natural language using a structured JSON spec.
Fetch raw ad creative, app, ranking, and revenue data from AdMapix as structured JSON.
Site audit, content writing, and competitor analysis for organic search rankings.
More from harrylabsj
Browse all skillsCross-platform price compare for Taobao vs JD, PDD, Vipshop with match-scored buy/wait/avoid calls.
Get a clear order, switch, add, wait, or skip call on a Meituan deal from visible fees, ETA, reviews, and threshold math.
Evaluate Pinduoduo deals before you commit — subsidies, group-buy rules, seller risk, and refund terms in one pass.
Get plain-Chinese explanations of routine health checkup reports with abnormal items grouped and prioritized.
Plan Freshippo (盒马鲜生) shopping with freshness checks, delivery-slot advice, and a manual order handoff.
Record, search, and cluster observations from work sessions with tagged, dated records.