Business & Productivity
Analyzes your recent Claude Code chat history to identify coding patterns, development gaps, and areas for improvement, curates relevant learning resources from HackerNews, and automatically sends a personalized growth report to your Slack DMs.
Skills are markdown files that extend Claude's knowledge. Place them in ~/.claude/skills/ to make them available. Claude reads relevant skills automatically based on context.
Step 1: Create the skill directory
Step 2: Save SKILL.md to
# Developer Growth Analysis
This skill provides personalized feedback on your recent coding work by analyzing your Claude Code chat interactions and identifying patterns that reveal strengths and areas for growth.
Use this skill when you want to:
This skill is ideal for developers who want structured feedback on their growth without waiting for code reviews, and who prefer data-driven insights from their own work history.
This skill performs a six-step analysis of your development work:
Ask Claude to analyze your recent coding work:
Analyze my developer growth from my recent chats
Or be more specific about which time period:
Analyze my work from today and suggest areas for improvement
The skill will generate a formatted report with:
When a user requests analysis of their developer growth or coding patterns from recent work:
Read the chat history from `~/.claude/history.jsonl`. This file is a JSONL format where each line contains:
- `display`: The user's message/request
- `project`: The project being worked on
- `timestamp`: Unix timestamp (in milliseconds)
- `pastedContents`: Any code or content pasted
Filter for entries from the past 24-48 hours based on the current timestamp.
Extract and analyze the following from the filtered chats:
- **Projects and Domains**: What types of projects was the user working on? (e.g., backend, frontend, DevOps, data, etc.)
- **Technologies Used**: What languages, frameworks, and tools appear in the conversations?
- **Problem Types**: What categories of problems are being solved? (e.g., performance optimization, debugging, feature implementation, refactoring, setup/configuration)
- **Challenges Encountered**: What problems did the user struggle with? Look for:
- Repeated questions about similar topics
- Problems that took multiple attempts to solve
- Questions indicating knowledge gaps
- Complex architectural decisions
- **Approach Patterns**: How does the user solve problems? (e.g., methodical, exploratory, experimental)
Based on the analysis, identify 3-5 specific areas where the user could improve. These should be:
- **Specific** (not vague like "improve coding skills")
- **Evidence-based** (grounded in actual chat history)
- **Actionable** (practical improvements that can be made)
- **Prioritized** (most impactful first)
Examples of good improvement areas:
- "Advanced TypeScript patterns (generics, utility types, type guards) - you struggled with type safety in [specific project]"
- "Error handling and validation - I noticed you patched several bugs related to missing null checks"
- "Async/await patterns - your recent work shows some race conditions and timing issues"
- "Database query optimization - you rewrote the same query multiple times"
Create a comprehensive report with this structure:
```markdown
# Your Developer Growth Report
**Report Period**: [Yesterday / Today / [Custom Date Range]]
**Last Updated**: [Current Date and Time]
## Work Summary
[2-3 paragraphs summarizing what the user worked on, projects touched, technologies used, and overall focus areas]
Example:
"Over the past 24 hours, you focused primarily on backend development with three distinct projects. Your work involved TypeScript, React, and deployment infrastructure. You tackled a mix of feature implementation, debugging, and architectural decisions, with a particular focus on API design and database optimization."
## Improvement Areas (Prioritized)
### 1. [Area Name]
**Why This Matters**: [Explanation of why this skill is important for the user's work]
**What I Observed**: [Specific evidence from chat history showing this gap]
**Recommendation**: [Concrete step(s) to improve in this area]
**Time to Skill Up**: [Brief estimate of effort required]
---
[Repeat for 2-4 additional areas]
## Strengths Observed
[2-3 bullet points highlighting things you're doing well - things to continue doing]
## Action Items
Priority order:
1. [Action item derived from highest priority improvement area]
2. [Action item from next area]
3. [Action item from next area]
## Learning Resources
[Will be populated in next step]
```
Use Rube MCP to search HackerNews for articles related to each improvement area:
- For each improvement area, construct a search query targeting high-quality resources
- Search HackerNews using RUBE_SEARCH_TOOLS with queries like:
- "Learn [Technology/Pattern] best practices"
- "[Technology] advanced patterns and techniques"
- "Debugging [specific problem type] in [language]"
- Prioritize posts with high engagement (comments, upvotes)
- For each area, include 2-3 most relevant articles with:
- Article title
- Publication date
- Brief description of why it's relevant
- Link to the article
Add this section to the report:
```markdown
## Curated Learning Resources
### For: [Improvement Area]
1. **[Article Title]** - [Date]
[Description of what it covers and why it's relevant to your improvement area]
[Link]
2. **[Article Title]** - [Date]
[Description]
[Link]
[Repeat for other improvement areas]
```
Deliver the report in a clean, readable format that the user can:
- Quickly scan for key takeaways
- Use for focused learning planning
- Reference over the next week as they work on improvements
- Share with mentors if they want external feedback
Use Rube MCP to send the complete report to the user's own Slack DMs:
- Check if Slack connection is active via RUBE_SEARCH_TOOLS
- If not connected, use RUBE_MANAGE_CONNECTIONS to initiate Slack auth
- Use RUBE_MULTI_EXECUTE_TOOL to send the report as a formatted message:
- Send the report title and period as the first message
- Break the report into logical sections (Summary, Improvements, Strengths, Actions, Resources)
- Format each section as a well-structured Slack message with proper markdown
- Include clickable links for the learning resources
- Confirm delivery in the CLI output
This ensures the user has the report in a place they check regularly and can reference it throughout the week.
Analyze my developer growth from my recent chats
# Your Developer Growth Report
**Report Period**: November 9-10, 2024
**Last Updated**: November 10, 2024, 9:15 PM UTC
Over the past two days, you focused on backend infrastructure and API development. Your primary project was an open-source showcase application, where you made significant progress on connections management, UI improvements, and deployment configuration. You worked with TypeScript, React, and Node.js, tackling challenges ranging from data security to responsive design. Your work shows a balance between implementing features and addressing technical debt.
**Why This Matters**: TypeScript is central to your work, but leveraging its advanced features (generics, utility types, conditional types, type guards) can significantly improve code reliability and reduce runtime errors. Better type safety catches bugs at compile time rather than in production.
**What I Observed**: In your recent chats, you were working with connection data structures and struggled a few times with typing auth configurations properly. You also had to iterate on union types for different connection states. There's an opportunity to use discriminated unions and type guards more effectively.
**Recommendation**: Study TypeScript's advanced type system, particularly utility types (Omit, Pick, Record), conditional types, and discriminated unions. Apply these patterns to your connection configuration handling and auth state management.
**Time to Skill Up**: 5-8 hours of focused learning and practice
**Why This Matters**: You identified and fixed a security concern where sensitive connection data was being displayed in your console. Preventing information leakage is critical for applications handling user credentials and API keys. Good practices here prevent security incidents and user trust violations.
**What I Observed**: You caught that your "Your Apps" page was showing full connection data including auth configs. This shows good security instincts, and the next step is building this into your default thinking when handling sensitive information.
**Recommendation**: Review security best practices for handling sensitive data in frontend applications. Create reusable patterns for filtering/masking sensitive information before displaying it. Consider implementing a secure data layer that explicitly whitelist what can be shown in the UI.
**Time to Skill Up**: 3-4 hours
**Why This Matters**: You're designing UIs that need to work across different screen sizes and user interactions. Strong component architecture makes it easier to build complex UIs without bugs and improves maintainability.
**What I Observed**: You worked on the "Marketplace" UI (formerly Browse Tools), recreating it from a design image. You also identified and fixed scrolling issues where content was overflowing containers. There's an opportunity to strengthen your understanding of layout containment and responsive design patterns.
**Recommendation**: Study React component composition patterns and CSS layout best practices (especially flexbox and grid). Focus on container queries and responsive patterns that prevent overflow issues. Look into component composition libraries and design system approaches.
**Time to Skill Up**: 6-10 hours (depending on depth)
Priority order:
Deep dive into TypeScript's type system with practical examples and real-world applications. Covers discriminated unions, type guards, and patterns for ensuring compile-time safety in complex applications.
[Link to discussion]
Practical guide to designing APIs with TypeScript that catch errors early. Particularly relevant for your connection configuration work.
[Link to discussion]
Comprehensive guide to data security in frontend applications, including filtering sensitive information, secure logging, and audit trails.
[Link to discussion]
How to safely handle authentication tokens and API keys in applications, with examples for different frameworks.
[Link to discussion]
Explores component composition strategies that scale, with examples using modern React patterns.
[Link to discussion]
Learn responsive design patterns that prevent overflow issues and work across all screen sizes.
[Link to discussion]
This skill: