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 ./.trae/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, resource curation, and Slack delivery. However, it lacks an explicit 'Use when...' clause which caps completeness, and it uses second-person voice ('your') which slightly detracts. Trigger terms could better anticipate natural user phrasing.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks for a coding progress review, skill assessment, learning recommendations, or development feedback.'
Include natural trigger terms users might say, such as 'review my progress', 'what should I learn', 'coding improvement', or 'development report'.
| 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 by the nature of the actions described. | 2 / 3 |
Trigger Term Quality | Contains some relevant keywords like 'chat history', 'coding patterns', 'HackerNews', 'Slack DMs', and 'growth report', but these are somewhat niche and may not match what users would naturally say. Users might say things like 'review my progress', 'learning recommendations', or 'skill assessment' which aren't covered. | 2 / 3 |
Distinctiveness Conflict Risk | This is a highly distinctive skill combining Claude Code chat history analysis, HackerNews resource curation, and Slack DM delivery — a very specific niche that 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 has a well-defined workflow concept but suffers severely from verbosity — it explains what it does multiple times (intro, 'What This Skill Does', 'How Accuracy and Quality Are Maintained'), includes a massive example output that largely duplicates the template, and adds unnecessary sections like 'Tips and Best Practices' that don't help Claude execute the task. The actionable content (file path, JSONL format, step sequence) is solid but buried in padding, and MCP tool invocations lack concrete parameter examples.
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 describe the skill to a human reader but don't help Claude execute it.
Move the large example output to a separate EXAMPLE.md file and reference it with a link, keeping only the report template structure inline.
Add concrete MCP tool call examples with actual parameters (e.g., specific RUBE_SEARCH_TOOLS invocation syntax with sample query and expected response format).
Add validation checkpoints: verify history.jsonl exists and has recent entries before proceeding, verify search results are non-empty, and verify Slack delivery succeeded with error recovery steps.
| 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 unnecessary padding that explain things Claude doesn't need. The massive example output (~100 lines of sample report) is largely redundant given the detailed report template already in the instructions. The skill could be cut to less than a third of its length. | 1 / 3 |
Actionability | The instructions provide a clear step-by-step process with specific file paths (~/.claude/history.jsonl) and JSONL field names, which is good. However, the MCP tool usage (RUBE_SEARCH_TOOLS, RUBE_MANAGE_CONNECTIONS, RUBE_MULTI_EXECUTE_TOOL) lacks concrete executable examples of actual tool calls with parameters. The HackerNews search queries are vague templates rather than specific invocations. | 2 / 3 |
Workflow Clarity | The 7-step workflow is clearly sequenced and logically ordered. However, there are no validation checkpoints — no verification that the JSONL file exists or is readable, no check that search results are relevant before including them, no confirmation that the Slack message was actually delivered successfully before reporting success. The Slack auth step mentions checking connection but lacks error recovery if auth fails. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of text with no references to external files. The massive example output, the report template, the tips section, and the quality assurance section are all inline, making the skill extremely long. The example output alone could be a separate file. Content that should be split (report template, example output) is all crammed into one document. | 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
- Lingjie-chen/MT5
- Commit
3069d33
- 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.