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

55%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

50%

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

The body is clearly organized into a six-step process and a concrete report template, but it stays at a descriptive level: it lacks the executable technical specifics needed to actually read chat history, fetch HackerNews resources, and post to Slack. Adding concrete implementation steps and a verification checkpoint before delivery would lift the weaker dimensions.

Suggestions

Add concrete implementation details: the path/format of local Claude Code chat history, how to query HackerNews (e.g. the Algolia HN Search API), and how to post to Slack (webhook URL or chat.postMessage with a token).

Insert a validation/confirmation checkpoint before sending the report to Slack DMs (e.g. confirm the recipient and channel, retry on API errors).

Trim the redundant opening paragraph and merge the overlapping 'When to Use' and 'What This Skill Does' sections to tighten conciseness.

Dimension	Reasoning	Score
Conciseness	The opening paragraph restates the description and the 'When to Use' and 'What This Skill Does' sections overlap, so the body is mostly efficient but includes redundant framing that could be tightened.	2 / 3
Actionability	It provides a concrete process outline and a specific report template, but gives no executable mechanism — no chat-history file paths/formats, no HackerNews API call, and no Slack posting command/token — leaving key implementation details unspecified.	2 / 3
Workflow Clarity	The six-step sequence is clearly listed, but there are no validation or verification checkpoints before the outward-facing Slack DM delivery, which per the guidelines caps workflow clarity at 2.	2 / 3
Progressive Disclosure	It is a single self-contained, well-sectioned file with no external references, but at ~76 lines (above the 50-line simple-skill threshold) it keeps everything inline rather than splitting detailed templates into separate files.	2 / 3
	Total	8 / 12 Passed

Description

60%

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 and action-oriented but lacks an explicit 'Use when…' trigger clause, which caps its completeness and trigger-term quality. It describes a clear, fairly distinctive workflow but does not surface natural invocation phrases as strongly as the top-anchor examples.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants a personalized review of their recent coding work or asks for developer growth analysis, improvement areas, or learning resources from their Claude Code chats.'

Surface natural user phrasings such as 'developer growth', 'improve my coding', or 'analyze my recent work' to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions — 'Analyzes your recent Claude Code chat history', 'identify coding patterns, development gaps', 'curates relevant learning resources from HackerNews', 'sends a personalized growth report to your Slack DMs' — matching the top anchor.	3 / 3
Completeness	It clearly answers 'what does this do', but the 'when' is only implied; per the guidelines a missing explicit 'Use when…' trigger clause caps completeness at 2.	2 / 3
Trigger Term Quality	It contains some natural terms a user might say ('coding patterns', 'development gaps', 'learning resources', 'Slack'), but there is no explicit trigger phrasing and common user variations like 'developer growth' or 'improve my coding' are not surfaced.	2 / 3
Distinctiveness Conflict Risk	The HackerNews-curation plus Slack-DM-delivery niche is somewhat specific, yet without explicit trigger guidance it could still overlap with general coding-analysis or learning-resource skills.	2 / 3
	Total	9 / 12 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: composio-community/awesome-claude-plugins
Path: developer-growth-analysis/skills/developer-growth-analysis/SKILL.md
Commit: e521f7a

Reviewed: about 13 hours 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.