Developer Growth Analytics
Mines local Claude Code chat history for recurring technical gaps, drafts a growth report, curates Hacker News reading, and can deliver the digest to Slack.
Overview
Developer Growth Analytics (MCP Market) acts as an automated mentor: it evaluates recent coding sessions — tech choices, debugging hurdles, architecture decisions — then produces a structured progress report with prioritized improvements and HN articles matched to your gaps. Use for self-directed professional development when peer review is sparse, or as a weekly engineering growth ritual.
Work with LimeDock
Using this skill? LimeDock can wire it into a durable automation you own.
Skills show what's possible. LimeDock builds and runs the owned marketing, sales, and ops automations around them.
We sell owned automations for SaaS teams — live workflows that plug into Slack, CRM, and your internal platform — not just a skill list.
Link
Installation guide
Install from the MCP Market Developer Growth Analytics card (follow the listed `npx skills add …` / marketplace command), then restart the agent session. Slack delivery needs a configured Slack connector/MCP if you want DMs.
How to use it
Run after a week of sessions. Point it at Claude Code history (or export). Ask for strengths/gaps, a priority list, and reading links. Optionally pipe the report to Slack.
Example prompts
- “Run Developer Growth Analytics on my last 14 days of Claude Code sessions.”
- “What architecture mistakes do I keep repeating? Prioritize fixes.”
- “Send this week’s growth report to my Slack DM with 5 HN links.”
Use cases and examples
- Weekly personal engineering growth report
- Identify recurring debugging bottlenecks on a new stack
- Get high-signal HN reading matched to real struggles
- Prep for 1:1s with evidence from recent agent sessions
Prerequisites
- Local Claude Code (or compatible) session history access
- Optional: Slack MCP/connector for DM delivery
- Comfort sharing chat logs with the skill’s scripts — audit first
Tips
- Treat outputs as coaching signals, not performance reviews.
- Pair with self-improving knowledge systems so lessons become durable files.