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

57%

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 ./plugins/all-skills/skills/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 delivers genuinely concrete, non-obvious guidance (history file format, report structure, tool names) in a clearly ordered workflow, but it pays for it with heavy redundancy and a monolithic structure that inlines ~90 lines of example output. Cutting the duplicate summary section and moving the example report to a reference file would improve both weakest dimensions at no cost to actionability.

Suggestions

Delete the 'What This Skill Does' section — its six steps restate the 'Instructions' section verbatim in intent — and keep one canonical step list.

Move the full worked example report (~90 lines) into references/example-report.md and link to it with one line, keeping only a short excerpt inline to show format.

Trim 'Tips and Best Practices' and 'How Accuracy and Quality Are Maintained' to a few bullets; both restate claims already implicit in the instructions.

Dimension	Reasoning	Score
Conciseness	The 'What This Skill Does' six-step summary duplicates the 'Instructions' section almost one-to-one, the ~90-line fully worked example report dominates the file, and sections like 'How Accuracy and Quality Are Maintained' and 'Tips and Best Practices' add marketing-style padding. Not 1 because it does not explain concepts Claude already knows — the verbosity is redundancy, not tutorial filler.	2 / 5
Actionability	Provides concrete, non-inferable guidance: the exact history file path with its JSONL field schema ('~/.claude/history.jsonl' with 'display', 'project', 'timestamp', 'pastedContents'), a full report template, example search queries, and named Rube MCP tools. Not 5 because the HackerNews search and Slack send steps stop at tool names and intent without copy-ready invocation details.	4 / 5
Workflow Clarity	Seven numbered steps are clearly sequenced with a conditional checkpoint ('Check if Slack connection is active... If not connected, use RUBE_MANAGE_CONNECTIONS to initiate Slack auth'). Not 5 because there are no validation or error-recovery loops for the analysis quality or the report/delivery steps, and not 3 because the sequence and most checkpoints are explicit.	4 / 5
Progressive Disclosure	Sections are well-labeled, but the skill is a monolithic ~320-line file with no bundle files: the ~90-line example report and the report template are exactly the content that belongs in a separate references/ file and is inlined. Fits anchor 3 (content that should be separate is inline) better than 4 given the size of the inlined example.	3 / 5
	Total	13 / 20 Passed

Description

58%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 communicates a distinctive, concrete capability set with specific named integrations, but it entirely lacks a 'when to use' trigger clause, which both caps completeness and leaves trigger-term coverage thin. Adding an explicit 'Use when...' clause with natural user phrasings would lift the two weakest dimensions.

Suggestions

Add a 'Use when...' clause with natural trigger phrases, e.g. 'Use when the user asks to analyze their coding patterns, find skill gaps in their recent work, or wants a growth report from their Claude Code history.'

Include common synonyms users would actually say, such as 'skill gaps', 'learning resources', 'feedback on my development', or 'improve my coding', to broaden trigger-term coverage.

Trim the overlapping triad 'coding patterns, development gaps, and areas for improvement' into crisper distinct capabilities (e.g., 'identifies recurring struggles and skill gaps').

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') with only minor coverage gaps. Not 5 because 'identify coding patterns, development gaps, and areas for improvement' overlaps rather than enumerating distinct comprehensive capabilities.	4 / 5
Completeness	The 'what' is clear and multi-action, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. Not 2 because the 'what' half is concrete and specific, not vague.	3 / 5
Trigger Term Quality	Some natural keywords are present ('chat history', 'coding patterns', 'growth report'), but common variations users would say ('skill gaps', 'learning plan', 'improve my coding', 'feedback on my work') are missing. Fits anchor 3 better than 4 because keyword coverage is moderate, not good.	3 / 5
Distinctiveness Conflict Risk	The combination of Claude Code chat-history analysis, HackerNews curation, and Slack DM delivery forms a clear niche with minimal conflict risk. Not 5 because generic phrases like 'areas for improvement' could weakly overlap with code-review or feedback skills.	4 / 5
	Total	14 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: davepoon/buildwithclaude
Path: plugins/all-skills/skills/developer-growth-analysis/SKILL.md
Commit: b90e2de

Reviewed: 3 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.