Your Developer Growth Report【免费下载链接】awesome-codex-skillsA curated list of practical Codex skills for automating workflows across the Codex CLI and API.项目地址: https://gitcode.com/GitHub_Trending/aw/awesome-codex-skillsReport Period: [Yesterday / Today / [Custom Date Range]]Last Updated: [Current Date and Time]Work Summary[2-3 paragraphs summarizing what the user worked on, projects touched, technologies used, and overall focus areas]Example: Over the past 24 hours, you focused primarily on backend development with three distinct projects. Your work involved TypeScript, React, and deployment infrastructure. You tackled a mix of feature implementation, debugging, and architectural decisions, with a particular focus on API design and database optimization.Improvement Areas (Prioritized)1. [Area Name]Why This Matters: [Explanation of why this skill is important for the users work]What I Observed: [Specific evidence from chat history showing this gap]Recommendation: [Concrete step(s) to improve in this area]Time to Skill Up: [Brief estimate of effort required][Repeat for 2-4 additional areas]Strengths Observed[2-3 bullet points highlighting things youre doing well - things to continue doing]Action ItemsPriority order:[Action item derived from highest priority improvement area][Action item from next area][Action item from next area]Learning Resources[Will be populated in next step]模板的每一节都有明确用途Work Summary 用 23 段话概括工作重心Improvement Areas 为每个改进项提供为何重要 / 观察证据 / 建议 / 学习时长四要素Strengths Observed 保留值得坚持的正面行为Action Items 按优先级给出可直接执行的下一步。注意模板中的 Learning Resources 一节标注为 Will be populated in next step即由第五步填充。 ## 学习资源检索基于 HackerNews 的定向精选 第五步使用 **Rube MCP** 在 HackerNews 上为每个改进方向检索高质量文章。技能给出了具体的调用方式 - 针对每个改进方向构造检索查询目标是对准高质量资源 - 使用 RUBE_SEARCH_TOOLS 执行类似下面的查询 - Learn [Technology/Pattern] best practices - [Technology] advanced patterns and techniques - Debugging [specific problem type] in [language] - 优先选择互动度高评论数、点赞数多的帖子 - 每个改进方向精选 23 篇最相关的文章附上 - 文章标题 - 发布日期 - 与改进方向相关性的简要说明 - 文章链接。 检索结果以如下格式并入报告 markdown ## Curated Learning Resources ### For: [Improvement Area] 1. **[Article Title]** - [Date] [Description of what covers and why its relevant to your improvement area] [Link] 2. **[Article Title]** - [Date] [Description] [Link] [Repeat for other improvement areas]关于 Rube MCP 的调用模式仓库中有更细的参考实现composio-skills/hackernews-automation/SKILL.md 与 composio-skills/composio-automation/SKILL.md 都遵循同一套先发现、再连接、后执行的流程工具发现RUBE_SEARCH_TOOLS返回可用的工具 slug、输入 schema、推荐执行计划与已知坑点连接检查RUBE_MANAGE_CONNECTIONS确认目标 toolkit 处于 ACTIVE 状态执行RUBE_MULTI_EXECUTE_TOOL携带 schema 兼容的参数与session_id执行。这些技能还特别强调了几条通用注意事项永远先调用RUBE_SEARCH_TOOLS工具 schema 会变化不要硬编码 slug 与参数、确认连接为 ACTIVE 后再执行、严格遵循 schema 字段名与类型、以及复用同一工作流内的 session ID。报告投递自动发送到 Slack 私信第六步通过 Rube MCP 将完整报告发送到用户自己的 Slack 私信DMSKILL.md 规定了明确的投递流程通过RUBE_SEARCH_TOOLS检查 Slack 连接是否可用若未连接使用RUBE_MANAGE_CONNECTIONS发起 Slack 授权OAuth使用RUBE_MULTI_EXECUTE_TOOL将报告作为格式化消息发送第一条消息发送报告标题与报告周期将报告拆分为逻辑小节Summary、Improvements、Strengths、Actions、Resources每个小节格式化为结构良好的 Slack 消息使用正确的 markdown学习资源必须包含可点击的链接在 CLI 输出中确认投递成功。之所以把报告投递到 Slack 私信技能给出的理由是确保报告落在你日常会查看的地方便于整周随时参考。如果你希望以 CLI 方式管理 Slack 连接仓库中的 connect 技能 提供了另一条路径通过 Composio CLI 执行composio link slack即可在终端里直接驱动 Slack 发送消息。完整示例一次真实的分析输出为直观展示整套流程的产出SKILL.md 附带了一个完整示例。用户输入Analyze my developer growth from my recent chats对应的报告输出如下节选核心部分# Your Developer Growth Report **Report Period**: November 9-10, 2024 **Last Updated**: November 10, 2024, 9:15 PM UTC ## Work Summary Over the past two days, you focused on backend infrastructure and API development. Your primary project was an open-source showcase application, where you made significant progress on connections management, UI improvements, and deployment configuration. You worked with TypeScript, React, and Node.js, tackling challenges ranging from data security to responsive design. Your work shows a balance between implementing features and addressing technical debt. ## Improvement Areas (Prioritized) ### 1. Advanced TypeScript Patterns and Type Safety **Why This Matters**: TypeScript is central to your work, but leveraging its advanced features (generics, utility types, conditional types, type guards) can significantly improve code reliability and reduce runtime errors. Better type safety catches bugs at compile time rather than in production. **What I Observed**: In your recent chats, you were working with connection data structures and struggled a few times with typing auth configurations properly. You also had to iterate on union types for different connection states. Theres an opportunity to use discriminated unions and type guards more effectively. **Recommendation**: Study TypeScripts advanced type system, particularly utility types (Omit, Pick, Record), conditional types, and discriminated unions. Apply these patterns to your connection configuration handling and auth state management. **Time to Skill Up**: 5-8 hours of focused learning and practice ### 2. Secure Data Handling and Information Hiding in UI **Why This Matters**: You identified and fixed a security concern where sensitive connection data was being displayed in your console. Preventing information leakage is critical for applications handling user credentials and API keys. Good practices here prevent security incidents and user trust violations. **What I Observed**: You caught that your Your Apps page was showing full connection data including auth configs. This shows good security instincts, and the next step is building this into your default thinking when handling sensitive information. **Recommendation**: Review security best practices for handling sensitive data in frontend applications. Create reusable patterns for filtering/masking sensitive information before displaying it. Consider implementing a secure data layer that explicitly whitelist what can be shown in the UI. **Time to Skill Up**: 3-4 hours ### 3. Component Architecture and Responsive UI Patterns **Why This Matters**: Youre designing UIs that need to work across different screen sizes and user interactions. Strong component architecture makes it easier to build complex UIs without bugs and improves maintainability. **What I Observed**: You worked on the Marketplace UI (formerly Browse Tools), recreating it from a design image. You also identified and fixed scrolling issues where content was overflowing containers. Theres an opportunity to strengthen your understanding of layout containment and responsive design patterns. **Recommendation**: Study React component composition patterns and CSS layout best practices (especially flexbox and grid). Focus on container queries and responsive patterns that prevent overflow issues. Look into component composition libraries and design system approaches. **Time to Skill Up**: 6-10 hours (depending on depth) ## Strengths Observed - **Security Awareness**: You proactively identified data leakage issues before they became problems - **Iterative Refinement**: You worked through UI requirements methodically, asking clarifying questions and improving designs - **Full-Stack Capability**: You comfortably work across backend APIs, frontend UI, and deployment concerns - **Problem-Solving Approach**: You break down complex tasks into manageable steps ## Action Items Priority order: 1. Spend 1-2 hours learning TypeScript utility types and discriminated unions; apply to your connection data structures 2. Document security patterns for your project (what data is safe to display, filtering/masking functions) 3. Study one article on advanced React patterns and apply one pattern to your current UI work 4. Set up a code review checklist focused on type safety and data security for future PRs ## Curated Learning Resources ### For: Advanced TypeScript Patterns 1. **TypeScripts Advanced Types: Generics, Utility Types, and Conditional Types** - HackerNews, October 2024 Deep dive into TypeScripts type system with practical examples and real-world applications. Covers discriminated unions, type guards, and patterns for ensuring compile-time safety in complex applications. [Link to discussion] 2. **Building Type-Safe APIs in TypeScript** - HackerNews, September 2024 Practical guide to designing APIs with TypeScript that catch errors early. Particularly relevant for your connection configuration work. [Link to discussion] ### For: Secure Data Handling in Frontend 1. **Preventing Information Leakage in Web Applications** - HackerNews, August 2024 Comprehensive guide to data security in frontend applications, including filtering sensitive information, secure logging, and audit trails. [Link to discussion] 2. **OAuth and API Key Management Best Practices** - HackerNews, July 2024 How to safely handle authentication tokens and API keys in applications, with examples for different frameworks. [Link to discussion] ### For: Component Architecture and Responsive Design 1. **Advanced React Patterns: Composition Over Configuration** - HackerNews Explores component composition strategies that scale, with examples using modern React patterns. [Link to discussion] 2. **CSS Layout Mastery: Flexbox, Grid, and Container Queries** - HackerNews, October 2024 Learn responsive design patterns that prevent overflow issues and work across all screen sizes. [Link to discussion]这个示例展示了报告如何把观察到的证据如 struggled a few times with typing auth configurations properly与结构化建议学习工具类型、判别联合等结合并最终落到可执行的动作清单Action Items上。使用建议与最佳实践SKILL.md 的 Tips and Best Practices 部分给出了一套可持续的使用方法论每周运行一次分析追踪跨时间的成长轨迹一次只聚焦一个改进方向专注几天后再切换下一个把学习资源当作学习指南逐一研读推荐材料并练习应用其中模式专注一周后重新查看报告观察工作模式是否发生变化学习资源是针对你的实际工作定制的而非泛泛主题因此与你在做的事情高度相关。质量保障机制SKILL.md 在最后专门说明了该技能如何维持准确度与质量核心在于证据驱动基于带时间戳的聊天历史分析真实工作模式生成扎根于真实项目的、有据可依的建议精选的学习资源直接对准识别出的缺口聚焦可执行的改进而非模糊反馈基于复杂度给出具体的学习时长估算优先排序对开发效率影响最大的方向。如何在 Codex 中安装与启用该技能是 awesome-codex-skills 仓库的一部分安装方式与仓库其他技能一致。推荐使用仓库自带的 skill-installer 提供的安装脚本README.md Quickstart 章节有完整说明git clone 仓库地址 awesome-codex-skills cd awesome-codex-skills python skill-installer/scripts/install-skill-from-github.py --repo owner/awesome-codex-skills --path developer-growth-analysis安装脚本会把技能放入$CODEX_HOME/skills/developer-growth-analysis默认~/.codex/skills重启 Codex 后新技能才会被加载。也可以手动安装将developer-growth-analysis/目录复制到$CODEX_HOME/skills/默认~/.codex/skills/重启 Codex然后在会话中自然描述任务——Codex 会根据 frontmatter 中的description自动触发匹配的技能。安装后可以这样验证README.md 建议使用ls ~/.codex/skills查看已安装的技能列表并用head ~/.codex/skills/developer-growth-analysis/SKILL.md检查元数据是否正确加载。如何触发SKILL.md 的 How to Use 章节给出了两种触发方式。最直接的方式是Analyze my developer growth from my recent chats或者更具体地指定时间范围Analyze my work from today and suggest areas for improvement【免费下载链接】awesome-codex-skillsA curated list of practical Codex skills for automating workflows across the Codex CLI and API.项目地址: https://gitcode.com/GitHub_Trending/aw/awesome-codex-skills创作声明：本文部分内容由AI辅助生成（AIGC），仅供参考