agentleFS
Sign inStart free
Cor-IncorporatedCor-Incorporated/claude-code-skills/skills/developer-growth-analysis/SKILL.md

developer-growth-analysis

Skill5 starsChanged 2 months agoMITView on GitHub

Analyze Claude Code chat history to identify coding patterns, skill gaps, and growth areas. Generates a personalized report with curated HackerNews learning resources and sends it to Slack DMs. Triggers: 'analyze my growth', 'review my coding patterns', 'developer growth report', 'what should I learn', 'analyze my recent work'. Do NOT use for code review, project analysis, or team performance evaluation.

37 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use twitter-algorithm-optimizer, agent-deep-links and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • trendinuxSkill

    twitter-algorithm-optimizer

    Analyze and optimize tweets for maximum reach using Twitter's open-source algorithm insights. Rewrite and edit user tweets to improve engagement and visibility based on how the recommendation system ranks content.

    Also in 14 projects that use this

  • ComposioHQSkill

    agent-deep-links

    Build, validate, and troubleshoot deep links for Codex, Cursor, VS Code, Visual Studio, and similar tools. Use when users ask for clickable links (especially in Slack) that open threads, files, folders, or app settings.

    Also in 3 projects that use this

  • ComposioHQSkill

    helium-mcp

    Search real-time news with bias scoring, get live stock/ETF/crypto data with AI analysis, ML options pricing, balanced news synthesis, and meme search via the Helium MCP server.

    Also in 3 projects that use this

  • petestewartSkill

    datadog-logs

    Query Datadog logs via the Logs Search API v2. Use when the user asks to "check the logs", "search logs", "find errors in Datadog", "look up logs for", "show me production logs", "check for errors", "search Datadog", or any request involving log search, error investigation, or production debugging that requires Datadog log data.

    Also in 3 projects that use this

  • ammosuSkill

    video-downloader

    Downloads videos from YouTube and other platforms for offline viewing, editing, or archival. Handles various formats and quality options.

    Also in 7 projects that use this

  • +7 more from ComposioHQ

The file

We split this skill into the rules it gives an agent

8 rules. 0 are common, 4 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 35 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read ~/.claude/history.jsonl (JSONL format).

    line 16
  2. Distinctive:

    Use HackerNews search for each improvement area:

    line 84
  3. Very specific:

    Check Slack connection via RUBE_SEARCH_TOOLS.

    line 93
  4. Very specific:

    If not connected, use RUBE_MANAGE_CONNECTIONS to initiate auth.

    line 94
  5. Very specific:

    If ~/.claude/history.jsonl does not exist or is empty, inform the user and suggest running some Claude Code sessions first.

    line 102
  6. Distinctive:

    If no entries found in 24-48 hours, expand the window to 7 days.

    line 103
  7. Distinctive:

    If Slack connection fails, output the report directly in the terminal as fallback.

    line 104
  8. Distinctive:

    If HackerNews search returns no results for an area, note it and suggest alternative search terms.

    line 105

“Common” is measured: kept by at least 6 in 10 of the 35 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Developer Growth Analysis

Analyze recent Claude Code chat history, identify improvement areas, curate learning resources, and deliver a growth report to Slack DMs.

Steps

<important if="reading and parsing Claude Code chat history for growth analysis"> ### 1. Read Chat History

Read ~/.claude/history.jsonl (JSONL format). Each line contains:

  • display: User's message
  • project: Project name
  • timestamp: Unix timestamp (ms)
  • pastedContents: Pasted code/content

Filter for entries from the past 24-48 hours. </important>

<important if="analyzing developer work patterns from chat history"> ### 2. Analyze Work Patterns

Extract from filtered chats:

  • Projects/Domains: backend, frontend, DevOps, data, etc.
  • Technologies: languages, frameworks, tools used
  • Problem Types: debugging, feature implementation, refactoring, optimization
  • Challenges: repeated questions, multi-attempt problems, knowledge gaps
  • Approach Patterns: methodical, exploratory, experimental</important>
<important if="identifying skill gaps and improvement areas from coding patterns"> ### 3. Identify 3-5 Improvement Areas

Each area must be:

  • Specific: not "improve coding skills" but "Advanced TypeScript generics for type-safe API responses"
  • Evidence-based: grounded in actual chat history
  • Actionable: practical steps to improve
  • Prioritized: most impactful first</important>
<important if="generating the developer growth report document"> ### 4. Generate Report

Structure the report as:

# Your Developer Growth Report
**Report Period**: [Date Range]
**Last Updated**: [Current Date]

## Work Summary
[2-3 paragraphs: projects, technologies, focus areas]

## Improvement Areas (Prioritized)
### 1. [Area Name]
**Why This Matters**: [Importance]
**What I Observed**: [Evidence from chat history]
**Recommendation**: [Concrete steps]
**Time to Skill Up**: [Effort estimate]
---
[Repeat for 2-4 more areas]

## Strengths Observed
[2-3 bullet points of things to continue]

## Action Items
1. [Highest priority action]
2. [Next action]
3. [Next action]

## Curated Learning Resources
[Populated in next step]
</important><important if="searching HackerNews for curated learning resources"> ### 5. Search Learning Resources

Use HackerNews search for each improvement area:

  • Query: "[Technology/Pattern] best practices", "[Topic] advanced techniques"
  • Select 2-3 high-engagement articles per area
  • Include: title, date, relevance description, link</important>
<important if="sending growth report to Slack DMs"> ### 6. Send to Slack DMs
  • Check Slack connection via RUBE_SEARCH_TOOLS.
  • If not connected, use RUBE_MANAGE_CONNECTIONS to initiate auth.
  • Send report in logical sections using RUBE_MULTI_EXECUTE_TOOL.
  • Confirm delivery.</important>
<important if="handling errors during growth analysis execution"> ## Error Handling
  • If ~/.claude/history.jsonl does not exist or is empty, inform the user and suggest running some Claude Code sessions first.
  • If no entries found in 24-48 hours, expand the window to 7 days.
  • If Slack connection fails, output the report directly in the terminal as fallback.
  • If HackerNews search returns no results for an area, note it and suggest alternative search terms.</important>

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free