[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73A4E720GYZWJES378AXW23":3,"skill-same:01M73A4E720GYZWJES378AXW23":58},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M73A4E720GYZWJES378AXW23","performance-profiler",null,"Performance Profiler","kalash33\u002Fkstack","kalash33","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F90259149?v=4","01M7365X8Q0B73NYHA730SMZWN","Kalash Poddar","01M7365X9D0JK47C3Q0YCCK9Z2",0,"MIT","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fnginity-engineering\u002Fperformance-profiler\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: \"performance-profiler\"\ndescription: \"Performance Profiler\"\n---\n\n# Performance Profiler\n\n**Tier:** POWERFUL  \n**Category:** Engineering  \n**Domain:** Performance Engineering  \n\n---\n\n## Overview\n\nSystematic performance profiling for Node.js, Python, and Go applications. Identifies CPU, memory, and I\u002FO bottlenecks; generates flamegraphs; analyzes bundle sizes; optimizes database queries; detects memory leaks; and runs load tests with k6 and Artillery. Always measures before and after.\n\n## Core Capabilities\n\n- **CPU profiling** — flamegraphs for Node.js, py-spy for Python, pprof for Go\n- **Memory profiling** — heap snapshots, leak detection, GC pressure\n- **Bundle analysis** — webpack-bundle-analyzer, Next.js bundle analyzer\n- **Database optimization** — EXPLAIN ANALYZE, slow query log, N+1 detection\n- **Load testing** — k6 scripts, Artillery scenarios, ramp-up patterns\n- **Before\u002Fafter measurement** — establish baseline, profile, optimize, verify\n\n---\n\n## When to Use\n\n- App is slow and you don't know where the bottleneck is\n- P99 latency exceeds SLA before a release\n- Memory usage grows over time (suspected leak)\n- Bundle size increased after adding dependencies\n- Preparing for a traffic spike (load test before launch)\n- Database queries taking >100ms\n\n---\n\n## Quick Start\n\n```bash\n# Analyze a project for performance risk indicators\npython3 scripts\u002Fperformance_profiler.py \u002Fpath\u002Fto\u002Fproject\n\n# JSON output for CI integration\npython3 scripts\u002Fperformance_profiler.py \u002Fpath\u002Fto\u002Fproject --json\n\n# Custom large-file threshold\npython3 scripts\u002Fperformance_profiler.py \u002Fpath\u002Fto\u002Fproject --large-file-threshold-kb 256\n```\n\n---\n\n## Golden Rule: Measure First\n\n```bash\n# Establish baseline BEFORE any optimization\n# Record: P50, P95, P99 latency | RPS | error rate | memory usage\n\n# Wrong: \"I think the N+1 query is slow, let me fix it\"\n# Right: Profile → confirm bottleneck → fix → measure again → verify improvement\n```\n\n---\n\n## Node.js Profiling\n→ See references\u002Fprofiling-recipes.md for details\n\n## Before\u002FAfter Measurement Template\n\n```markdown\n## Performance Optimization: [What You Fixed]\n\n**Date:** 2026-03-01  \n**Engineer:** @username  \n**Ticket:** PROJ-123  \n\n### Problem\n[1-2 sentences: what was slow, how was it observed]\n\n### Root Cause\n[What the profiler revealed]\n\n### Baseline (Before)\n| Metric | Value |\n|--------|-------|\n| P50 latency | 480ms |\n| P95 latency | 1,240ms |\n| P99 latency | 3,100ms |\n| RPS @ 50 VUs | 42 |\n| Error rate | 0.8% |\n| DB queries\u002Freq | 23 (N+1) |\n\nProfiler evidence: [link to flamegraph or screenshot]\n\n### Fix Applied\n[What changed — code diff or description]\n\n### After\n| Metric | Before | After | Delta |\n|--------|--------|-------|-------|\n| P50 latency | 480ms | 48ms | -90% |\n| P95 latency | 1,240ms | 120ms | -90% |\n| P99 latency | 3,100ms | 280ms | -91% |\n| RPS @ 50 VUs | 42 | 380 | +804% |\n| Error rate | 0.8% | 0% | -100% |\n| DB queries\u002Freq | 23 | 1 | -96% |\n\n### Verification\nLoad test run: [link to k6 output]\n```\n\n---\n\n## Optimization Checklist\n\n### Quick wins (check these first)\n\n```\nDatabase\n□ Missing indexes on WHERE\u002FORDER BY columns\n□ N+1 queries (check query count per request)\n□ Loading all columns when only 2-3 needed (SELECT *)\n□ No LIMIT on unbounded queries\n□ Missing connection pool (creating new connection per request)\n\nNode.js\n□ Sync I\u002FO (fs.readFileSync) in hot path\n□ JSON.parse\u002Fstringify of large objects in hot loop\n□ Missing caching for expensive computations\n□ No compression (gzip\u002Fbrotli) on responses\n□ Dependencies loaded in request handler (move to module level)\n\nBundle\n□ Moment.js → dayjs\u002Fdate-fns\n□ Lodash (full) → lodash\u002Ffunction imports\n□ Static imports of heavy components → dynamic imports\n□ Images not optimized \u002F not using next\u002Fimage\n□ No code splitting on routes\n\nAPI\n□ No pagination on list endpoints\n□ No response caching (Cache-Control headers)\n□ Serial awaits that could be parallel (Promise.all)\n□ Fetching related data in a loop instead of JOIN\n```\n\n---\n\n## Common Pitfalls\n\n- **Optimizing without measuring** — you'll optimize the wrong thing\n- **Testing in development** — profile against production-like data volumes\n- **Ignoring P99** — P50 can look fine while P99 is catastrophic\n- **Premature optimization** — fix correctness first, then performance\n- **Not re-measuring** — always verify the fix actually improved things\n- **Load testing production** — use staging with production-size data\n\n---\n\n## Best Practices\n\n1. **Baseline first, always** — record metrics before touching anything\n2. **One change at a time** — isolate the variable to confirm causation\n3. **Profile with realistic data** — 10 rows in dev, millions in prod — different bottlenecks\n4. **Set performance budgets** — `p(95) \u003C 200ms` in CI thresholds with k6\n5. **Monitor continuously** — add Datadog\u002FPrometheus metrics for key paths\n6. **Cache invalidation strategy** — cache aggressively, invalidate precisely\n7. **Document the win** — before\u002Fafter in the PR description motivates the team\n","# Performance Profiler\n\n**Tier:** POWERFUL  \n**Category:** Engineering  \n**Domain:** Performance Engineering  \n\n---\n\n## Overview\n\nSystematic performance profiling for Node.js, Python, and Go applications. Identifies CPU, memory, and I\u002FO bottlenecks; generates flamegraphs; analyzes bundle sizes; optimizes database queries; detects memory leaks; and runs load tests with k6 and Artillery. Always measures before and after.\n\n## Core Capabilities\n\n- **CPU profiling** — flamegraphs for Node.js, py-spy for Python, pprof for Go\n- **Memory profiling** — heap snapshots, leak detection, GC pressure\n- **Bundle analysis** — webpack-bundle-analyzer, Next.js bundle analyzer\n- **Database optimization** — EXPLAIN ANALYZE, slow query log, N+1 detection\n- **Load testing** — k6 scripts, Artillery scenarios, ramp-up patterns\n- **Before\u002Fafter measurement** — establish baseline, profile, optimize, verify\n\n---\n\n## When to Use\n\n- App is slow and you don't know where the bottleneck is\n- P99 latency exceeds SLA before a release\n- Memory usage grows over time (suspected leak)\n- Bundle size increased after adding dependencies\n- Preparing for a traffic spike (load test before launch)\n- Database queries taking >100ms\n\n---\n\n## Quick Start\n\n```bash\n# Analyze a project for performance risk indicators\npython3 scripts\u002Fperformance_profiler.py \u002Fpath\u002Fto\u002Fproject\n\n# JSON output for CI integration\npython3 scripts\u002Fperformance_profiler.py \u002Fpath\u002Fto\u002Fproject --json\n\n# Custom large-file threshold\npython3 scripts\u002Fperformance_profiler.py \u002Fpath\u002Fto\u002Fproject --large-file-threshold-kb 256\n```\n\n---\n\n## Golden Rule: Measure First\n\n```bash\n# Establish baseline BEFORE any optimization\n# Record: P50, P95, P99 latency | RPS | error rate | memory usage\n\n# Wrong: \"I think the N+1 query is slow, let me fix it\"\n# Right: Profile → confirm bottleneck → fix → measure again → verify improvement\n```\n\n---\n\n## Node.js Profiling\n→ See references\u002Fprofiling-recipes.md for details\n\n## Before\u002FAfter Measurement Template\n\n```markdown\n## Performance Optimization: [What You Fixed]\n\n**Date:** 2026-03-01  \n**Engineer:** @username  \n**Ticket:** PROJ-123  \n\n### Problem\n[1-2 sentences: what was slow, how was it observed]\n\n### Root Cause\n[What the profiler revealed]\n\n### Baseline (Before)\n| Metric | Value |\n|--------|-------|\n| P50 latency | 480ms |\n| P95 latency | 1,240ms |\n| P99 latency | 3,100ms |\n| RPS @ 50 VUs | 42 |\n| Error rate | 0.8% |\n| DB queries\u002Freq | 23 (N+1) |\n\nProfiler evidence: [link to flamegraph or screenshot]\n\n### Fix Applied\n[What changed — code diff or description]\n\n### After\n| Metric | Before | After | Delta |\n|--------|--------|-------|-------|\n| P50 latency | 480ms | 48ms | -90% |\n| P95 latency | 1,240ms | 120ms | -90% |\n| P99 latency | 3,100ms | 280ms | -91% |\n| RPS @ 50 VUs | 42 | 380 | +804% |\n| Error rate | 0.8% | 0% | -100% |\n| DB queries\u002Freq | 23 | 1 | -96% |\n\n### Verification\nLoad test run: [link to k6 output]\n```\n\n---\n\n## Optimization Checklist\n\n### Quick wins (check these first)\n\n```\nDatabase\n□ Missing indexes on WHERE\u002FORDER BY columns\n□ N+1 queries (check query count per request)\n□ Loading all columns when only 2-3 needed (SELECT *)\n□ No LIMIT on unbounded queries\n□ Missing connection pool (creating new connection per request)\n\nNode.js\n□ Sync I\u002FO (fs.readFileSync) in hot path\n□ JSON.parse\u002Fstringify of large objects in hot loop\n□ Missing caching for expensive computations\n□ No compression (gzip\u002Fbrotli) on responses\n□ Dependencies loaded in request handler (move to module level)\n\nBundle\n□ Moment.js → dayjs\u002Fdate-fns\n□ Lodash (full) → lodash\u002Ffunction imports\n□ Static imports of heavy components → dynamic imports\n□ Images not optimized \u002F not using next\u002Fimage\n□ No code splitting on routes\n\nAPI\n□ No pagination on list endpoints\n□ No response caching (Cache-Control headers)\n□ Serial awaits that could be parallel (Promise.all)\n□ Fetching related data in a loop instead of JOIN\n```\n\n---\n\n## Common Pitfalls\n\n- **Optimizing without measuring** — you'll optimize the wrong thing\n- **Testing in development** — profile against production-like data volumes\n- **Ignoring P99** — P50 can look fine while P99 is catastrophic\n- **Premature optimization** — fix correctness first, then performance\n- **Not re-measuring** — always verify the fix actually improved things\n- **Load testing production** — use staging with production-size data\n\n---\n\n## Best Practices\n\n1. **Baseline first, always** — record metrics before touching anything\n2. **One change at a time** — isolate the variable to confirm causation\n3. **Profile with realistic data** — 10 rows in dev, millions in prod — different bottlenecks\n4. **Set performance budgets** — `p(95) \u003C 200ms` in CI thresholds with k6\n5. **Monitor continuously** — add Datadog\u002FPrometheus metrics for key paths\n6. **Cache invalidation strategy** — cache aggressively, invalidate precisely\n7. **Document the win** — before\u002Fafter in the PR description motivates the team\n",{"name":5,"description":7},"main","b30820b3248f6676d5389f0ccabd4e5250c9c536","skills\u002Fnginity-engineering\u002Fperformance-profiler","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack","https:\u002F\u002Fgithub.com\u002Fkalash33","kalashpoddar.me","Tech-savvy Full Stack Developer 🚀 | Cybersecurity enthusiast 🔒 | Passionate about innovation and securing the digital world 🌐 | Let's code securely! 💻🔐","2026-05-20 04:11:22",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add kalash33\u002Fkstack --skill performance-profiler",{"tool":38,"command":39},"bunx","bunx skills add kalash33\u002Fkstack --skill performance-profiler",{"tool":41,"command":42},"pnpm","pnpm dlx skills add kalash33\u002Fkstack --skill performance-profiler","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fnginity-engineering\u002Fperformance-profiler\u002FSKILL.md",true,[46,52],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"references\u002Fprofiling-recipes.md","REFERENCE","参考文档",11531,"https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fnginity-engineering\u002Fperformance-profiler\u002Freferences\u002Fprofiling-recipes.md",{"path":53,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":56,"sourceHtmlUrl":57},"scripts\u002Fperformance_profiler.py","SCRIPT","脚本",6137,"https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fnginity-engineering\u002Fperformance-profiler\u002Fscripts\u002Fperformance_profiler.py",[59,66,73,80,87,94],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M73CFERCR43JCAP606E41EFB","zustand-store-ts","Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state\u002Faction separation. Use when building React state management, creating global stores, or implementing reacti...","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzustand-store-ts\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M73CFCMFVTAQEMTZ5HR10X8V","zoom-automation","Automate Zoom meeting creation, management, recordings, webinars, and participant tracking via Rube MCP (Composio). Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-automation\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M73CFAA7EBWXJVXDQ1X555MB","zoho-crm-automation","Automate Zoho CRM tasks via Rube MCP (Composio): create\u002Fupdate records, search contacts, manage leads, and convert leads. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzoho-crm-automation\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M73CF80XCM9K81567MJ8QZFW","zod-validation-expert","Expert in Zod — TypeScript-first schema validation. Covers parsing, custom errors, refinements, type inference, and integration with React Hook Form, Next.js, and tRPC.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzod-validation-expert\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M73CF4YPMF3RA8ZJDXZSMD93","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"01M73CF2S25EN3XNAMKY47XHPS","zendesk-automation","Automate Zendesk tasks via Rube MCP (Composio): tickets, users, organizations, replies. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzendesk-automation\u002FSKILL.md",[],[]]