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.
45
47%
Does it follow best practices?
Impact
—
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. However, it lacks an explicit 'Use when...' clause, which caps completeness, and uses second person ('your') which slightly undermines the professional tone. The trigger terms, while descriptive, may not match how users would naturally request this functionality.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks for a coding skills assessment, development progress report, or learning recommendations based on their recent work.'
Include natural trigger term variations users might say, such as 'skill assessment', 'learning report', 'coding improvement', 'weekly developer summary', or 'progress review'.
| 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 these are not necessarily terms a user would naturally say when requesting this skill. Missing common trigger variations like 'learning', 'skill assessment', 'weekly report', or 'developer feedback'. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a very specific niche combining Claude Code chat history analysis, HackerNews resource curation, and Slack DM delivery. Unlikely to conflict with other skills due to this unique combination of triggers. | 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 far too verbose, repeating its process description twice and including large sections (When to Use, What This Skill Does, Tips, How Accuracy Is Maintained) that add no actionable value for Claude. While the workflow steps are logically sequenced and some concrete details are provided (file paths, field names, MCP tool names), the skill lacks executable code, validation checkpoints, and error handling. The entire content could be reduced to roughly 80 lines while improving clarity.
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 — they explain things Claude can infer and duplicate the Instructions section.
Add executable code for parsing ~/.claude/history.jsonl (e.g., a Python or shell snippet that reads and filters by timestamp).
Add concrete MCP tool invocation examples with actual parameters for RUBE_SEARCH_TOOLS and RUBE_MULTI_EXECUTE_TOOL instead of vague descriptions.
Add validation checkpoints: verify chat history file exists and has recent entries, verify MCP search returned results, verify Slack message delivery succeeded, with fallback behavior for each failure case.
| 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 padding that explain things Claude can infer. The example output alone is ~100 lines of filler. The six-step process is described twice (once in 'What This Skill Does' and again in 'Instructions'). The skill could be cut to less than a third of its length. | 1 / 3 |
Actionability | The instructions provide a concrete file path (~/.claude/history.jsonl) and JSONL field names, and reference specific MCP tools (RUBE_SEARCH_TOOLS, RUBE_MANAGE_CONNECTIONS, RUBE_MULTI_EXECUTE_TOOL). However, there's no executable code for parsing the JSONL file, no concrete MCP tool invocation examples with actual parameters, and the HackerNews search queries are vague suggestions rather than specific API calls. | 2 / 3 |
Workflow Clarity | The seven steps are clearly sequenced and logically ordered. However, there are no validation checkpoints — no verification that the chat history was successfully read, no check that the JSONL parsing produced valid results, no validation of Slack delivery success beyond 'confirm delivery.' For a workflow involving external service calls (MCP, Slack), missing error handling and feedback loops is a significant gap. | 2 / 3 |
Progressive Disclosure | The skill is a monolithic wall of text with no references to external files and no bundle files. The massive example output, the duplicated process description, and the tips/best practices sections are all inline content that bloats the file. The report template could be in a separate file, and the example output adds enormous length without proportional value. | 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
364c6b2
- 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.