developer-growth-analysis
Analyze Your Developer Growth
Developers can miss recurring gaps hidden across daily AI-assisted work. This skill analyzes recent Claude Code history, recommends focused learning, and delivers a report through Slack.
Stop for confirmation before installing.
Review the plan and obtain explicit user consent before changing files.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "developer-growth-analysis" from https://skillstore.io/skills/davila7-developer-growth-analysis.md and its manifest at https://skillstore.io/api/skills/davila7-developer-growth-analysis/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "developer-growth-analysis". Analyze today's Claude Code chats and show my top learning priority.
Expected outcome:
Top priority: strengthen TypeScript error handling. Your recent chats show repeated null-state fixes. Practice typed result patterns and add validation at API boundaries.
Using "developer-growth-analysis". Compare my backend and frontend work from the last two days.
Expected outcome:
- Strength: you break backend failures into clear diagnostic steps.
- Growth area: frontend layout fixes required repeated overflow adjustments.
- Next action: practice one responsive layout exercise and document the pattern.
Security Audit
High RiskAll 16 shell backtick findings are false positives caused by Markdown fences or inline code, and the reconnaissance finding describes analysis categories. Home-directory access is confirmed because the skill reads private Claude Code history, including pasted content. Automatic Slack delivery creates an additional disclosure risk because the skill lacks explicit consent, preview, and redaction steps.
Confirmed security concerns (1)
Capability review items (2)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Risk Factors
⚙️ External commands (16)
📁 Filesystem access (2)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/davila7-developer-growth-analysis/audits/9?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/davila7-developer-growth-analysis?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/davila7-developer-growth-analysis?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/davila7-developer-growth-analysis/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/davila7-developer-growth-analysis.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
davila7. (2026). developer-growth-analysis security audit report (audit version 9) [Author version unspecified]. Skillstore. https://skillstore.io/skills/davila7-developer-growth-analysis/audits/9BibTeX citation
@techreport{davila7-davila7-developer-growth-analysis-2026,
author = {davila7},
title = {developer-growth-analysis security audit report (audit version 9)},
institution = {Skillstore},
year = {2026},
number = {9},
url = {https://skillstore.io/skills/davila7-developer-growth-analysis/audits/9},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "developer-growth-analysis security audit report (audit version 9)"
version: "unspecified"
type: report
authors:
- name: "davila7"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/davila7-developer-growth-analysis/audits/9"
identifiers:
- type: other
value: "skillstore:davila7-developer-growth-analysis:audit:9"
description: "Skillstore immutable audit report identifier"
Compare variants
4 installable variantsEach author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.
Why this variant is first
89jobrien-developer-growth-analysis
2026-08-21
davila7-developer-growth-analysis
2026-08-21
dyai2025-developer-growth-analysis
2026-08-21
composiohq-developer-growth-analysis
2026-08-21
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Find Early-Career Learning Priorities
Identify repeated technical questions and convert them into a focused study plan.
Review Work Across Projects
Summarize technologies, challenges, and habits across recent client or product work.
Prepare for Mentoring Sessions
Create an evidence-based report that supports a focused discussion with a mentor.
Try These Prompts
Analyze my Claude Code chats from the last 24 hours. Show my strengths, three improvement areas, and clear next actions.
Review my last 48 hours of chats and assess my work with [technology]. Prioritize repeated problems and recommend targeted learning.
Compare my recent work on [project one] and [project two]. Identify shared weaknesses, distinct strengths, and transferable practices.
Analyze my recent chats, rank development gaps by impact, estimate learning effort, find relevant Hacker News resources, and create a one-week plan.
Best Practices
- Limit each analysis to a clear date range and relevant projects.
- Review the report evidence before sharing it through Slack or with a mentor.
- Focus on one priority area for a week before measuring progress again.
Avoid
- Do not analyze history containing secrets or private client data without review and redaction.
- Do not treat chat history as a complete measure of engineering performance.
- Do not send a report externally without confirming its content and destination.