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

68%

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

65%

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

The content is concrete and actionable with named tools and a clear data schema, but it is verbose and redundant, lacks validation/feedback loops for the riskier Slack-send step, and is a monolithic file that would benefit from splitting out the large example and templates.

Suggestions

Collapse the redundant 'What This Skill Does' and 'Instructions' sections into one sequenced procedure, and cut the motivational prose and the 'How Accuracy and Quality Are Maintained' section.

Add validation checkpoints: handle a missing or empty ~/.claude/history.jsonl, retry/fallback when HackerNews search returns nothing, and confirm with the user before sending the report to Slack.

Move the full ~90-line example report into a separate references/ file (e.g., EXAMPLE_REPORT.md) and link to it one level deep, keeping SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is actionable rather than explaining basic concepts, but it is padded with redundancy — 'What This Skill Does' and 'Instructions' describe the same six/seven-step process twice — plus motivational prose ('This skill is ideal for developers who want structured feedback...') and a self-justifying 'How Accuracy and Quality Are Maintained' section that restate rather than instruct.	2 / 3
Actionability	It gives concrete, executable specifics — the data path '~/.claude/history.jsonl', the JSONL field schema (display/project/timestamp/pastedContents), named MCP tools (RUBE_SEARCH_TOOLS, RUBE_MANAGE_CONNECTIONS, RUBE_MULTI_EXECUTE_TOOL), and ready-to-use search-query templates — which is highly actionable for an instruction-only skill.	3 / 3
Workflow Clarity	The seven steps are clearly numbered and sequenced, but validation/checkpoint guidance is largely missing: there is no handling for a missing history file, empty search results, or failed Slack delivery, and no confirm-before-send gate for the outward-facing Slack step, so workflow clarity is capped at 2.	2 / 3
Progressive Disclosure	The single ~315-line SKILL.md is monolithic with no bundle files, and inline content like the ~90-line full example report and the detailed report template could be split into reference files; sections are well-organized, but at this size it should offload detail to one-level-deep references.	2 / 3
	Total	9 / 12 Passed

Description

72%

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 is specific, distinct, and rich in natural trigger terms, but it is written in second-person voice and omits an explicit 'Use when...' trigger clause, capping completeness at 2.

Suggestions

Rewrite in third person to match the good examples (e.g., 'Analyzes recent Claude Code chat history...' without 'your').

Add an explicit trigger clause such as 'Use when the user asks for feedback on their coding patterns, wants a growth report, or mentions developer growth or skill gaps from recent work.'

Include common trigger phrasings like 'developer growth' and 'improvement areas from recent chats' that mirror how a user would phrase the request.

Dimension	Reasoning	Score
Specificity	It lists multiple concrete actions ('identify coding patterns, development gaps, and areas for improvement', 'curates relevant learning resources from HackerNews', 'sends a personalized growth report to your Slack DMs'), which is level-3 specificity, but it uses second-person voice ('Analyzes your recent Claude Code chat history') so the specificity score is reduced by one per the voice guideline.	2 / 3
Completeness	It clearly answers 'what' the skill does but lacks any explicit 'Use when...' trigger clause or equivalent 'when' guidance, which per the guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	It surfaces natural terms a developer would actually say — 'Claude Code chat history', 'coding patterns', 'development gaps', 'learning resources', 'HackerNews', 'Slack DMs' — giving good coverage of plausible trigger phrases.	3 / 3
Distinctiveness Conflict Risk	The combination of analyzing local Claude Code chat history, curating HackerNews resources, and delivering a report to Slack DMs is a distinct niche unlikely to collide with other skills.	3 / 3
	Total	10 / 12 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: b79ed72

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