Developer Growth Analysis Skill for Claude
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.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/composio-community/awesome-claude-plugins --skill developer-growth-analysisThe instruction itself
12 sections, as written by the authorDeveloper 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.
When to Use This Skill
Use this skill when you want to:
- Understand your development patterns and habits from recent work
- Identify specific technical gaps or recurring challenges
- Discover which topics would benefit from deeper study
- Get curated learning resources tailored to your actual work patterns
- Track improvement areas across your recent projects
What This Skill Does
This skill performs a six-step analysis of your development work:
- Reads Your Chat History: Accesses your local Claude Code chat history from the past 24-48 hours
- Identifies Development Patterns: Analyzes the types of problems you're solving, technologies you're using, and challenges you encounter
- Detects Improvement Areas: Recognizes patterns that suggest skill gaps or areas where you might benefit from deeper knowledge
- Generates a Personalized Report: Creates a comprehensive report showing your work summary, identified improvement areas, and specific recommendations
- Finds Learning Resources: Curates high-quality articles and discussions directly relevant to your improvement areas
- Delivers the Report: Sends the complete report to your Slack DMs for easy reference
How to Use
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
Report Structure
The skill generates a formatted report with:
Work Summary
2-3 paragraphs summarizing what you worked on, projects touched, technologies used, and overall focus areas.
Improvement Areas (Prioritized)
For each improvement area:
- Why This Matters: Explanation of why this skill is important
- What Was Observed: Specific evidence from chat history
- Recommendation: Concrete steps to improve
- Time to Skill Up: Brief estimate of effort required
Strengths Observed
Bullet points highlighting things you're doing well
Action Items
Priority-ordered list of actionable improvements
Learning Resources
Curated articles from HackerNews relevant to each improvement area
Example 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"
Tips and Best Practices
- Run this analysis once a week to track your improvement trajectory over time
- Pick one improvement area at a time and focus on it for a few days
- Use the learning resources as a study guide
- Revisit this report after focusing on an area to see how your work patterns change
- The learning resources are curated for your actual work, not generic topics
Other skills for the same job
different authors, same section of the catalogue
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.
Automate Brevo (Sendinblue) tasks via Rube MCP (Composio): manage email campaigns, create/edit templates, track senders, and monitor campaign performance. Always search tools first for current schemas.
Automate Klaviyo tasks via Rube MCP (Composio): manage email/SMS campaigns, inspect campaign messages, track tags, and monitor send jobs. Always search tools first for current schemas.
Research a prospect then draft personalized outreach. Uses web research by default, supercharged with enrichment and CRM. Trigger with "draft outreach to [person/company]", "write cold email to [prospect]", "reach out to [name]".
You are an expert in email marketing and automation. Your goal is to create email sequences that nurture relationships, drive action, and move people toward conversion.
Email has the highest ROI of any marketing channel. $36 for every $1 spent. Yet most startups treat it as an afterthought - bulk blasts, no personalization, landing in spam folders.
Write personalized trade show booth invitation emails, pre-show outreach sequences, and exhibition meeting requests. Use this skill when the user needs to invite prospects, customers, partners, or VIPs to visit their booth at a trade show or exhibition, write pre-show emails, create multi-touch invitation sequences, draft meeting requests for an upcoming event, or write any outreach related to an exhibition or expo they're attending. Triggers on requests like 'write an email inviting people to our booth', 'I need a pre-show outreach sequence for MEDICA', 'draft an invitation for our CES booth', 'help me get meetings before the trade show', 'booth traffic email', 'pre-show marketing email', 'trade show outreach template', 'exhibition invitation letter', or casual phrasing like 'we're exhibiting next month, need to get people to come by'. If the user mentions an upcoming show and wants to write emails to drive booth traffic or schedule meetings, this is the right skill.
Email has the highest ROI of any marketing channel. $36 for every $1 spent. Yet most startups treat it as an afterthought - bulk blasts, no personalization, landing in spam folders. This skill covers transactional email that works, marketing automation that converts, deliverability that reaches inboxes, and the infrastructure decisions that scale. Use when: keywords, file_patterns, code_patterns.
How to use it
Take composio-community/developer-growth-analysis from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.