developer-growth-analysis
tessl i github:ComposioHQ/awesome-claude-skills --skill developer-growth-analysisAnalyzes 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.
Validation
75%| Criteria | Description | Result |
|---|---|---|
description_voice | 'description' should use third person voice; found second person: 'your ' | Warning |
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
Total | 12 / 16 Passed | |
Implementation
27%This skill is significantly over-documented with excessive verbosity that explains concepts Claude already understands. While the workflow is reasonably clear, it lacks executable code examples and proper error handling. The content would benefit greatly from being split into multiple files with a concise overview in the main SKILL.md.
Suggestions
Reduce the main SKILL.md to ~50 lines with a quick start section, moving the detailed report template and example output to separate files (e.g., REPORT_TEMPLATE.md, EXAMPLES.md)
Add executable Python/JavaScript code for parsing ~/.claude/history.jsonl instead of just describing the format
Include actual MCP tool invocation syntax (e.g., specific RUBE_SEARCH_TOOLS and RUBE_MULTI_EXECUTE_TOOL call formats)
Add validation checkpoints: what to do if history file is empty/missing, if Slack auth fails, or if HackerNews returns no results
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive explanations Claude doesn't need. The 'When to Use This Skill' and 'What This Skill Does' sections explain obvious concepts. The example output alone is ~150 lines when a brief template would suffice. Multiple sections repeat the same information. | 1 / 3 |
Actionability | Provides some concrete guidance (file path, JSONL structure, report template) but lacks executable code for parsing the history file, actual MCP tool invocation syntax, and specific Slack API calls. The instructions describe what to do rather than showing how. | 2 / 3 |
Workflow Clarity | Steps are clearly numbered and sequenced, but lacks validation checkpoints. No error handling for missing history file, failed Slack auth, or empty search results. The 'Check if Slack connection is active' step doesn't specify what to do if it fails beyond initiating auth. | 2 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files. The massive example output should be in a separate EXAMPLES.md. The report template is duplicated (once in instructions, once in example). Everything is inline when much could be split out. | 1 / 3 |
Total | 6 / 12 Passed |
Activation
68%The description excels at specificity and distinctiveness, clearly articulating a unique multi-step workflow involving chat analysis, resource curation, and Slack delivery. However, it lacks explicit trigger guidance ('Use when...') which is critical for Claude to know when to select this skill, and uses second person voice ('your') which should be avoided.
Suggestions
Add a 'Use when...' clause with trigger terms like 'analyze my coding', 'learning report', 'development feedback', 'skill improvement', or 'growth analysis'
Convert from second person ('your recent Claude Code chat history', 'your Slack DMs') to third person voice ('the user's chat history', 'the user's Slack DMs')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'analyzes recent Claude Code chat history', 'identify coding patterns, development gaps, and areas for improvement', 'curates relevant learning resources from HackerNews', and 'sends a personalized growth report to your Slack DMs'. | 3 / 3 |
Completeness | Clearly answers 'what does this do' with detailed capabilities, but lacks an explicit 'Use when...' clause or equivalent trigger guidance explaining when Claude should select this skill. | 2 / 3 |
Trigger Term Quality | Contains some relevant keywords like 'chat history', 'coding patterns', 'learning resources', 'HackerNews', 'Slack DMs', and 'growth report', but lacks a 'Use when...' clause with natural trigger terms users would actually say when needing this skill. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche combining Claude Code chat analysis, HackerNews curation, and Slack delivery - unlikely to conflict with other skills due to this unique combination of integrations. | 3 / 3 |
Total | 10 / 12 Passed |
Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.