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.

Quality

58%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./developer-growth-analysis/SKILL.md

Quality

Content

56%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body gives a clear, well-sequenced workflow with a useful validation loop for Slack delivery, but it is verbose, inlines a large example that could be split out, and describes MCP tool calls without exact executable syntax. Tightening redundancy and externalizing the example would lift conciseness and progressive disclosure.

Suggestions

Remove redundancy between 'What This Skill Does' and 'Instructions' and cut the marketing-style 'How Accuracy and Quality Are Maintained' section to improve conciseness.

Move the full example report into a separate referenced file (e.g., references/example-report.md) and link to it, leaving only a short excerpt inline.

Provide exact Rube MCP tool invocation examples (argument shapes/JSON) so the actionability reaches copy-paste-ready level, and add a validation checkpoint after reading chat history to confirm entries were found before analyzing.

Dimension	Reasoning	Score
Conciseness	Mostly efficient but padded: 'What This Skill Does' overlaps with 'Instructions', the full example report is very long, and 'How Accuracy and Quality Are Maintained' is largely marketing prose that Claude does not need.	3 / 5
Actionability	Concrete details are present (file path ~/.claude/history.jsonl, JSONL fields, Rube MCP tool names, query templates, report template), but the Rube tool usage is described at a high level without exact invocation syntax/parameters, leaving execution incomplete.	3 / 5
Workflow Clarity	Seven steps are clearly sequenced, and the Slack step includes an explicit connection-check conditional ('Check if Slack connection is active... If not connected, use RUBE_MANAGE_CONNECTIONS'), with only minor validation gaps elsewhere.	4 / 5
Progressive Disclosure	Section headers give some structure, but the skill is a single ~600-line monolithic file with no external references, and the large example output and report template are inlined rather than split into separate files.	3 / 5
	Total	13 / 20 Passed

Description

61%Weight 40%Scale 1-5

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 conveys a clear, multi-action capability but omits an explicit 'Use when' trigger and uses second-person voice, which respectively cap completeness and reduce specificity. It is otherwise specific and reasonably distinctive.

Suggestions

Add an explicit 'Use when...' clause naming natural trigger phrases (e.g., 'Use when the user asks to analyze their recent coding work, find development gaps, or get a growth report from their Claude Code history').

Rewrite in third person ('Analyzes the user's recent Claude Code chat history...') to avoid the second-person specificity penalty.

Include a few more natural synonyms/file references a user might say ('developer growth', 'learning resources', 'study plan') to push trigger-term coverage toward 5.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('Analyzes your recent Claude Code chat history', 'curates relevant learning resources from HackerNews', 'sends a personalized growth report to your Slack DMs'), but uses second-person voice ('your', 'your Slack DMs'), triggering the -1 specificity penalty from a base of 4.	3 / 5
Completeness	It clearly states 'what' the skill does but contains no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	Natural terms like 'Claude Code chat history', 'coding patterns', 'growth report', 'HackerNews', and 'Slack DMs' map well to what a user would say, with only a few synonyms/variations missing.	4 / 5
Distinctiveness Conflict Risk	The niche (analyze Claude Code chat history -> growth report -> Slack DMs) is mostly distinct with only minor overlap risk against general analysis skills.	4 / 5
	Total	14 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: ComposioHQ/awesome-claude-skills
Path: developer-growth-analysis/SKILL.md
Commit: be2a406

Reviewed: 7 days ago

Table of Contents

Discovery Implementation Validation

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.