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

60%

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

50%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 content is concrete and well-sequenced but bloated by duplication and a promotional tone, and it lacks the validation feedback loops needed for its batch/send operations while inlining everything into one file.

Suggestions

Collapse the duplicated six-step descriptions ('What This Skill Does' vs 'Instructions') into a single concise procedure and cut the promotional 'How Accuracy and Quality Are Maintained' section.

Move the full worked example report into a separate reference file and link to it one level deep, keeping SKILL.md an overview.

Add explicit validation/feedback checkpoints: handle missing `~/.claude/history.jsonl`, empty HackerNews results, and Slack auth failure with retry guidance.

Dimension	Reasoning	Score
Conciseness	The body is noticeably verbose: the six steps are restated across 'What This Skill Does' and 'Instructions', a ~90-line full example report is inlined, and 'How Accuracy and Quality Are Maintained' is promotional padding rather than instruction.	2 / 5
Actionability	Provides concrete guidance — the exact path `~/.claude/history.jsonl` with its JSONL field schema, named MCP tools (RUBE_SEARCH_TOOLS, RUBE_MANAGE_CONNECTIONS, RUBE_MULTI_EXECUTE_TOOL), a report template, and example search queries — with only minor gaps (actual tool-call syntax is not shown).	4 / 5
Workflow Clarity	The seven-step sequence is clearly ordered, but batch/send operations (HackerNews curation, Slack delivery) lack validation and error-recovery feedback loops (missing history file, empty search results, failed Slack auth), which caps workflow clarity at 3 per the batch-operation rule.	3 / 5
Progressive Disclosure	No bundle files exist and the entire skill is a single monolithic document; the full worked example report and detailed resource section are inlined content that would read better as a one-level-deep reference, though section headers provide some structure.	3 / 5
	Total	12 / 20 Passed

Description

71%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 is specific and action-rich, clearly distinguishing the skill's multi-part workflow, but it omits any explicit 'when to use' trigger guidance, which caps its completeness score.

Suggestions

Append a 'Use when...' clause naming natural triggers (e.g., 'Use when you want feedback on your recent Claude Code work or want a personalized growth report in Slack').

Add common synonyms / file references like 'chat history', 'history.jsonl', or 'developer growth' to broaden trigger-term coverage.

Keep the concrete action list but tighten HackerNews/Slack phrasing to avoid implying capabilities the skill may not always have configured.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — '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' — covering analysis, curation, and delivery comprehensively.	5 / 5
Completeness	The 'what' is clearly and comprehensively stated, but there is no 'when'/'Use when...' clause or equivalent explicit trigger guidance; per the rubric, missing explicit trigger guidance caps completeness at 3.	3 / 5
Trigger Term Quality	Includes several natural terms ('Claude Code chat history', 'coding patterns', 'development gaps', 'HackerNews', 'growth report', 'Slack DMs') but lacks synonyms and a natural 'Use when...' trigger phrase, leaving a few common terms missing.	4 / 5
Distinctiveness Conflict Risk	The combination of Claude Code chat-history analysis plus HackerNews curation plus Slack DM delivery carves a clear niche with minimal overlap risk, though the broad 'analyze your work' framing has minor overlap with general code-review skills.	4 / 5
	Total	16 / 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: e8b2fa0

Reviewed: 1 day 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.