developer-growth-analysis
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 with Tessl CLI
npx tessl i github:davepoon/buildwithclaude --skill developer-growth-analysis60
Quality
51%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/all-skills/skills/developer-growth-analysis/SKILL.mdDiscovery
67%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
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...') and could benefit from more natural user-facing keywords that would help Claude recognize when to invoke this skill.
Suggestions
Add a 'Use when...' clause with trigger terms like 'analyze my coding progress', 'learning recommendations', 'skill improvement', or 'development feedback'
Include natural phrases users might say such as 'how am I doing', 'what should I learn', or 'review my recent work'
| 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', 'HackerNews', 'Slack DMs', and 'growth report', but lacks explicit trigger terms users would naturally say (e.g., 'analyze my progress', 'learning recommendations', 'skill assessment'). | 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 |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a comprehensive workflow for developer growth analysis but suffers from significant verbosity and redundancy. The instructions are clear but lack executable code examples for critical operations like JSONL parsing and MCP tool invocation. The massive inline example output and repeated explanations inflate token usage without adding proportional value.
Suggestions
Remove 'When to Use This Skill' and 'What This Skill Does' sections entirely - Claude can infer purpose from the instructions
Add executable code snippets for parsing ~/.claude/history.jsonl and constructing MCP tool calls (RUBE_SEARCH_TOOLS, RUBE_MULTI_EXECUTE_TOOL)
Move the full example report to a separate REPORT_TEMPLATE.md file and reference it
Add error handling steps: what to do if chat history is empty, Slack auth fails, or 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 clear step-by-step instructions and specifies the file path (~/.claude/history.jsonl) and format. However, lacks executable code for parsing JSONL, constructing MCP tool calls, or formatting Slack messages. References 'RUBE_SEARCH_TOOLS' and 'RUBE_MULTI_EXECUTE_TOOL' without showing actual invocation syntax. | 2 / 3 |
Workflow Clarity | The 7-step workflow is clearly sequenced, but lacks validation checkpoints. No error handling for missing chat history, failed Slack auth, or HackerNews search failures. Step 7 mentions checking Slack connection but doesn't specify what to do if it fails beyond 'initiate auth'. | 2 / 3 |
Progressive Disclosure | Content is monolithic with no references to external files. The massive example output could be a separate template file. The report structure template is duplicated (once in step 4, once in full example). Could benefit from splitting into REPORT_TEMPLATE.md and EXAMPLES.md. | 2 / 3 |
Total | 7 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 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.