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.
56
47%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Risky
Do not use without reviewing
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/all-skills/skills/developer-growth-analysis/SKILL.mdQuality
Discovery
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 history analysis, HackerNews curation, and Slack delivery. However, it lacks an explicit 'Use when...' clause, which caps completeness, and uses second-person voice ('your') which slightly detracts from the expected third-person convention. The trigger terms, while descriptive, could better anticipate how users would naturally request this functionality.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks for a coding growth report, development feedback, learning recommendations, or skill assessment.'
Switch from second-person ('your') to third-person voice, e.g., 'Analyzes the user's recent Claude Code chat history...' or 'Analyzes recent Claude Code chat history...'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: analyzes chat history, identifies coding patterns/development gaps/areas for improvement, curates learning resources from HackerNews, and sends a personalized growth report to Slack DMs. | 3 / 3 |
Completeness | The 'what' is well-covered with specific actions, but there is no explicit 'Use when...' clause or equivalent trigger guidance explaining when Claude should select this skill. The 'when' is only implied. | 2 / 3 |
Trigger Term Quality | Contains some relevant keywords like 'chat history', 'coding patterns', 'HackerNews', 'Slack DMs', and 'growth report', but uses second-person 'your' and lacks explicit natural trigger terms a user would say (e.g., 'learning', 'skill gaps', 'weekly report'). The terms are more descriptive than trigger-oriented. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a very specific niche: analyzing Claude Code chat history, curating from HackerNews, and sending to Slack DMs. This combination is unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
27%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is extremely verbose, repeating its process description twice and including a massive fabricated example output that inflates the token count without proportional value. While the core workflow is logically sequenced and provides some useful specifics (file path, field names, report structure), it lacks validation checkpoints, concrete tool invocation examples, and any progressive disclosure structure. The content would benefit enormously from being cut to roughly one-third its current size.
Suggestions
Remove the 'When to Use This Skill', 'What This Skill Does', 'Tips and Best Practices', and 'How Accuracy and Quality Are Maintained' sections entirely — these are redundant or explain things Claude already knows.
Cut the example output to a brief skeleton (10-15 lines) showing just the report structure, not a fully fabricated multi-page report.
Add concrete MCP tool invocation examples with actual parameters (e.g., exact RUBE_SEARCH_TOOLS call syntax with a sample query) instead of just naming the tools.
Add validation checkpoints: verify history.jsonl exists and has recent entries before proceeding, handle empty search results, and specify fallback behavior if Slack auth fails.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose. The 'When to Use This Skill', 'What This Skill Does', 'Tips and Best Practices', and 'How Accuracy and Quality Are Maintained' sections are all unnecessary fluff that Claude doesn't need. The massive example output (~100 lines of fabricated report) bloats the skill enormously. The six-step process is described twice (once in 'What This Skill Does' and again in 'Instructions'). Much of this content explains things Claude already knows how to do. | 1 / 3 |
Actionability | The instructions provide a concrete file path (~/.claude/history.jsonl) and JSONL field names, which is useful. However, the MCP tool references (RUBE_SEARCH_TOOLS, RUBE_MANAGE_CONNECTIONS, RUBE_MULTI_EXECUTE_TOOL) are mentioned by name but lack concrete invocation examples with actual parameters. The Slack integration steps are vague about exact tool calls. No executable code is provided for parsing the JSONL file. | 2 / 3 |
Workflow Clarity | The seven steps are clearly sequenced and logically ordered. However, there are no validation checkpoints — no verification that the history file exists or has recent entries, no check that HackerNews searches returned useful results, no error handling if Slack auth fails. The Slack step mentions checking connection status but doesn't specify what to do if it fails beyond 'initiate auth'. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of text with no bundle files and no references to external documents. The massive example output, the duplicated process description, and the tips/quality sections are all inline when they could be separated or omitted entirely. The skill is well over 200 lines with no structural decomposition. | 1 / 3 |
Total | 6 / 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 | |
- Repository
- davepoon/buildwithclaude
- Commit
d065ead
- 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.