[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71AXZPDX9W8CG60SN23ZMPT":3,"skill-same:01M71AXZPDX9W8CG60SN23ZMPT":80},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":56,"commitSha":57,"skillDirectory":58,"forksCount":59,"repositoryHtmlUrl":60,"repositoryHomepageUrl":61,"ownerHtmlUrl":62,"ownerBlogUrl":63,"ownerDescription":64,"updatedAt":65,"install":66,"resources":79},"01M71AXZPDX9W8CG60SN23ZMPT","perf-profile",null,"Performance profiling — measures code execution time, DB call time, and\nidentifies bottlenecks at both the application and database layer.\nUse when asked to \"profile performance\", \"measure execution time\",\n\"find bottlenecks\", \"check response times\", or \"why is this slow\".","ariadoss\u002Fsuperskills","ariadoss","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F414341?v=4","01M71AC7383PT6JCRZSQJ4AVTM","Danilo Stern-Sapad","01M71AC73Y7NTBTJ9KQYNENRRE",12,"MIT","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fperf-profile\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"perf profile","profile","perf","at","why","find","profiling","check","code","performance profiling","Bash","when","database","use","execution","call","time","performance","db","code execution","2026-11-10 10:12:30",false,"---\nname: perf-profile\nversion: 1.0.0\ndescription: |\n  Performance profiling — measures code execution time, DB call time, and\n  identifies bottlenecks at both the application and database layer.\n  Use when asked to \"profile performance\", \"measure execution time\",\n  \"find bottlenecks\", \"check response times\", or \"why is this slow\".\ntriggers:\n  - profile performance\n  - measure execution time\n  - find bottlenecks\n  - why is this slow\n  - check response times\n  - performance profiling\nallowed-tools:\n  - Bash\n  - Read\n  - Grep\n  - Glob\n---\n\n# \u002Fperf-profile\n\nProfile application performance: code execution time, DB call time, and bottleneck identification at both the application and database layer.\n\n## Step 1: Identify the target\n\nAsk the user (or infer from context): what are we profiling?\n- A specific endpoint \u002F route\n- A background job \u002F worker\n- A specific function or module\n- The whole application (general audit)\n\n## Step 2: DB call time profiling\n\n### PostgreSQL\n```bash\n# Enable timing in psql\npsql \"$DATABASE_URL\" -c \"\\timing on\"\n\n# Check pg_stat_statements for query timing (if available)\npsql \"$DATABASE_URL\" -c \"\n  SELECT\n    LEFT(query, 80) AS query,\n    calls,\n    ROUND(mean_exec_time::numeric, 2) AS mean_ms,\n    ROUND(total_exec_time::numeric, 2) AS total_ms,\n    ROUND((total_exec_time \u002F SUM(total_exec_time) OVER ()) * 100, 1) AS pct_total\n  FROM pg_stat_statements\n  ORDER BY mean_exec_time DESC\n  LIMIT 20;\n\" 2>\u002Fdev\u002Fnull || echo \"pg_stat_statements not available — enable with: CREATE EXTENSION pg_stat_statements;\"\n```\n\n### MySQL \u002F MariaDB\n```bash\nmysql -e \"\n  SELECT\n    LEFT(DIGEST_TEXT, 80) AS query,\n    COUNT_STAR AS calls,\n    ROUND(AVG_TIMER_WAIT\u002F1e9, 2) AS mean_ms,\n    ROUND(SUM_TIMER_WAIT\u002F1e9, 2) AS total_ms\n  FROM performance_schema.events_statements_summary_by_digest\n  ORDER BY AVG_TIMER_WAIT DESC\n  LIMIT 20;\n\" 2>\u002Fdev\u002Fnull || echo \"MySQL performance_schema unavailable\"\n```\n\nReport: table of top 20 queries by mean execution time, with call count and % of total DB time.\n\n## Step 3: Application-level profiling\n\n### Detect the runtime and suggest the right profiler:\n\n```bash\n# Detect language\u002Fframework\n[ -f package.json ] && echo \"RUNTIME=node\"\n[ -f Gemfile ] && echo \"RUNTIME=ruby\"\n[ -f requirements.txt ] || [ -f pyproject.toml ] && echo \"RUNTIME=python\"\n[ -f go.mod ] && echo \"RUNTIME=go\"\n[ -f pom.xml ] || [ -f build.gradle ] && echo \"RUNTIME=java\"\n```\n\n**Node.js:**\n- Built-in: `node --prof app.js` + `node --prof-process isolate-*.log`\n- For web: add `--inspect` and use Chrome DevTools profiler\n- Suggest: `clinic.js` (`npx clinic doctor -- node app.js`) for flame graphs\n\n**Ruby:**\n- Suggest: `stackprof` or `rack-mini-profiler` for Rails\n- For a specific method: wrap with `Benchmark.measure { ... }`\n\n**Python:**\n- Built-in: `python -m cProfile -s cumulative script.py`\n- For web: `py-spy top --pid \u003Cpid>` for live profiling\n- Suggest: `snakeviz` for visualization\n\n**Go:**\n- Built-in: `go tool pprof http:\u002F\u002Flocalhost:6060\u002Fdebug\u002Fpprof\u002Fprofile`\n- Add `import _ \"net\u002Fhttp\u002Fpprof\"` to enable the endpoint\n\n### Scan for existing timing instrumentation:\n```bash\ngrep -rn \"benchmark\\|timing\\|elapsed\\|duration\\|stopwatch\\|time\\.now\\|Time\\.now\\|perf_hook\\|performance\\.now\" \\\n  --include=\"*.rb\" --include=\"*.py\" --include=\"*.js\" --include=\"*.ts\" --include=\"*.go\" \\\n  . 2>\u002Fdev\u002Fnull | head -20\n```\n\n## Step 4: Code-level bottleneck scan\n\nScan for common performance anti-patterns in the codebase:\n\n**Synchronous blocking in async contexts:**\n```bash\ngrep -rn \"fs\\.readFileSync\\|execSync\\|spawnSync\\|sleep\\|time\\.Sleep\" \\\n  --include=\"*.js\" --include=\"*.ts\" --include=\"*.go\" . 2>\u002Fdev\u002Fnull | head -10\n```\n\n**Missing pagination (unbounded queries):**\n```bash\ngrep -rn \"\\.all\\b\\|find_all\\|SELECT \\*\\b\" \\\n  --include=\"*.rb\" --include=\"*.py\" --include=\"*.js\" --include=\"*.ts\" . 2>\u002Fdev\u002Fnull | head -10\n```\n\n**Repeated expensive calls in loops:**\n```bash\ngrep -rn \"each\\|forEach\\|for \" \\\n  --include=\"*.rb\" --include=\"*.py\" --include=\"*.js\" --include=\"*.ts\" . 2>\u002Fdev\u002Fnull | head -20\n```\n\nFor each flagged file, read the context and assess impact.\n\n## Step 5: Response time targets\n\nEvaluate findings against these thresholds:\n\n| Metric | Good | Acceptable | Needs Fix |\n|--------|------|-----------|-----------|\n| DB query mean time | \u003C10ms | \u003C100ms | >100ms |\n| DB calls per request | ≤3 | ≤10 | >10 |\n| Endpoint response time | \u003C100ms | \u003C500ms | >500ms |\n| Background job duration | \u003C1s | \u003C30s | >30s |\n\n## Step 6: Bottleneck report\n\n```\n## Performance Profile Report\n\n### DB Layer\n- Slowest query: \u003Cquery> — Xms mean (Y calls\u002Fmin)\n- Total DB time as % of request: Z%\n- Queries over 100ms: N\n\n### Application Layer\n- Blocking calls found: X\n- Unbounded queries (no LIMIT): Y\n- Loops with expensive operations: Z\n\n### Top 3 Bottlenecks (by estimated impact)\n1. \u003Cbottleneck> — estimated Xms saved per request\n2. \u003Cbottleneck> — estimated Yms saved per request\n3. \u003Cbottleneck> — estimated Zms saved per request\n\n### Recommended profiling tools for this stack\n- \u003Ctool 1>\n- \u003Ctool 2>\n```\n\nAsk: \"Want me to implement fixes for the top bottlenecks, or set up profiling instrumentation so you can measure before\u002Fafter?\"\n","# \u002Fperf-profile\n\nProfile application performance: code execution time, DB call time, and bottleneck identification at both the application and database layer.\n\n## Step 1: Identify the target\n\nAsk the user (or infer from context): what are we profiling?\n- A specific endpoint \u002F route\n- A background job \u002F worker\n- A specific function or module\n- The whole application (general audit)\n\n## Step 2: DB call time profiling\n\n### PostgreSQL\n```bash\n# Enable timing in psql\npsql \"$DATABASE_URL\" -c \"\\timing on\"\n\n# Check pg_stat_statements for query timing (if available)\npsql \"$DATABASE_URL\" -c \"\n  SELECT\n    LEFT(query, 80) AS query,\n    calls,\n    ROUND(mean_exec_time::numeric, 2) AS mean_ms,\n    ROUND(total_exec_time::numeric, 2) AS total_ms,\n    ROUND((total_exec_time \u002F SUM(total_exec_time) OVER ()) * 100, 1) AS pct_total\n  FROM pg_stat_statements\n  ORDER BY mean_exec_time DESC\n  LIMIT 20;\n\" 2>\u002Fdev\u002Fnull || echo \"pg_stat_statements not available — enable with: CREATE EXTENSION pg_stat_statements;\"\n```\n\n### MySQL \u002F MariaDB\n```bash\nmysql -e \"\n  SELECT\n    LEFT(DIGEST_TEXT, 80) AS query,\n    COUNT_STAR AS calls,\n    ROUND(AVG_TIMER_WAIT\u002F1e9, 2) AS mean_ms,\n    ROUND(SUM_TIMER_WAIT\u002F1e9, 2) AS total_ms\n  FROM performance_schema.events_statements_summary_by_digest\n  ORDER BY AVG_TIMER_WAIT DESC\n  LIMIT 20;\n\" 2>\u002Fdev\u002Fnull || echo \"MySQL performance_schema unavailable\"\n```\n\nReport: table of top 20 queries by mean execution time, with call count and % of total DB time.\n\n## Step 3: Application-level profiling\n\n### Detect the runtime and suggest the right profiler:\n\n```bash\n# Detect language\u002Fframework\n[ -f package.json ] && echo \"RUNTIME=node\"\n[ -f Gemfile ] && echo \"RUNTIME=ruby\"\n[ -f requirements.txt ] || [ -f pyproject.toml ] && echo \"RUNTIME=python\"\n[ -f go.mod ] && echo \"RUNTIME=go\"\n[ -f pom.xml ] || [ -f build.gradle ] && echo \"RUNTIME=java\"\n```\n\n**Node.js:**\n- Built-in: `node --prof app.js` + `node --prof-process isolate-*.log`\n- For web: add `--inspect` and use Chrome DevTools profiler\n- Suggest: `clinic.js` (`npx clinic doctor -- node app.js`) for flame graphs\n\n**Ruby:**\n- Suggest: `stackprof` or `rack-mini-profiler` for Rails\n- For a specific method: wrap with `Benchmark.measure { ... }`\n\n**Python:**\n- Built-in: `python -m cProfile -s cumulative script.py`\n- For web: `py-spy top --pid \u003Cpid>` for live profiling\n- Suggest: `snakeviz` for visualization\n\n**Go:**\n- Built-in: `go tool pprof http:\u002F\u002Flocalhost:6060\u002Fdebug\u002Fpprof\u002Fprofile`\n- Add `import _ \"net\u002Fhttp\u002Fpprof\"` to enable the endpoint\n\n### Scan for existing timing instrumentation:\n```bash\ngrep -rn \"benchmark\\|timing\\|elapsed\\|duration\\|stopwatch\\|time\\.now\\|Time\\.now\\|perf_hook\\|performance\\.now\" \\\n  --include=\"*.rb\" --include=\"*.py\" --include=\"*.js\" --include=\"*.ts\" --include=\"*.go\" \\\n  . 2>\u002Fdev\u002Fnull | head -20\n```\n\n## Step 4: Code-level bottleneck scan\n\nScan for common performance anti-patterns in the codebase:\n\n**Synchronous blocking in async contexts:**\n```bash\ngrep -rn \"fs\\.readFileSync\\|execSync\\|spawnSync\\|sleep\\|time\\.Sleep\" \\\n  --include=\"*.js\" --include=\"*.ts\" --include=\"*.go\" . 2>\u002Fdev\u002Fnull | head -10\n```\n\n**Missing pagination (unbounded queries):**\n```bash\ngrep -rn \"\\.all\\b\\|find_all\\|SELECT \\*\\b\" \\\n  --include=\"*.rb\" --include=\"*.py\" --include=\"*.js\" --include=\"*.ts\" . 2>\u002Fdev\u002Fnull | head -10\n```\n\n**Repeated expensive calls in loops:**\n```bash\ngrep -rn \"each\\|forEach\\|for \" \\\n  --include=\"*.rb\" --include=\"*.py\" --include=\"*.js\" --include=\"*.ts\" . 2>\u002Fdev\u002Fnull | head -20\n```\n\nFor each flagged file, read the context and assess impact.\n\n## Step 5: Response time targets\n\nEvaluate findings against these thresholds:\n\n| Metric | Good | Acceptable | Needs Fix |\n|--------|------|-----------|-----------|\n| DB query mean time | \u003C10ms | \u003C100ms | >100ms |\n| DB calls per request | ≤3 | ≤10 | >10 |\n| Endpoint response time | \u003C100ms | \u003C500ms | >500ms |\n| Background job duration | \u003C1s | \u003C30s | >30s |\n\n## Step 6: Bottleneck report\n\n```\n## Performance Profile Report\n\n### DB Layer\n- Slowest query: \u003Cquery> — Xms mean (Y calls\u002Fmin)\n- Total DB time as % of request: Z%\n- Queries over 100ms: N\n\n### Application Layer\n- Blocking calls found: X\n- Unbounded queries (no LIMIT): Y\n- Loops with expensive operations: Z\n\n### Top 3 Bottlenecks (by estimated impact)\n1. \u003Cbottleneck> — estimated Xms saved per request\n2. \u003Cbottleneck> — estimated Yms saved per request\n3. \u003Cbottleneck> — estimated Zms saved per request\n\n### Recommended profiling tools for this stack\n- \u003Ctool 1>\n- \u003Ctool 2>\n```\n\nAsk: \"Want me to implement fixes for the top bottlenecks, or set up profiling instrumentation so you can measure before\u002Fafter?\"\n",{"name":5,"version":44,"triggers":45,"description":51,"allowed-tools":52},"1.0.0",[46,47,48,49,50,28],"profile performance","measure execution time","find bottlenecks","why is this slow","check response times","Performance profiling — measures code execution time, DB call time, and\nidentifies bottlenecks at both the application and database layer.\nUse when asked to \"profile performance\", \"measure execution time\",\n\"find bottlenecks\", \"check response times\", or \"why is this slow\".\n",[29,53,54,55],"Read","Grep","Glob","main","c7ec8d78e5dc37484c2cfe90ab04de163d97dd41","skills\u002Fperf-profile",0,"https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills","https:\u002F\u002Fhyperion360.com\u002Fblog\u002Fparallel-ai-agents-engineering-workflow\u002F","https:\u002F\u002Fgithub.com\u002Fariadoss","https:\u002F\u002Fdanilosapad.com\u002F","CEO & Founder of @Hyperion360","2026-11-01 12:36:50",{"source":8,"skillName":5,"commands":67,"prompt":77,"zipAvailable":78},[68,71,74],{"tool":69,"command":70},"npx","npx skills add ariadoss\u002Fsuperskills --skill perf-profile",{"tool":72,"command":73},"bunx","bunx skills add ariadoss\u002Fsuperskills --skill perf-profile",{"tool":75,"command":76},"pnpm","pnpm dlx skills add ariadoss\u002Fsuperskills --skill perf-profile","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fperf-profile\u002FSKILL.md",true,[],[81,107,131,150,177,193],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":92,"publishedAt":39},"01M71AZE3MPF891RM354EMRYA1","youtube","Download YouTube video transcripts when user provides a YouTube URL or asks to download\u002Fget\u002Ffetch a transcript from YouTube. Also use when user wants to transcribe or get captions\u002Fsubtitles from a YouTube video.","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube\u002FSKILL.md",[87],{"categoryNo":88,"categoryName":89,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",[83,93,94,95,96,97,98,29,99,30,100,101,102,103,104,32,105,106],"user","download","transcribe","write","transcript","video transcripts","URL","Captions","get","fetch","Video","read","subtitles","transcripts",{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":39},"01M71AZAYR85PW6BJGSQXS4BN2","write-plan","Use when you have a spec or requirements for a multi-step task, before touching code. Produces an engineering plan complete with TDD tasks, DRY\u002FSOLID\u002FYAGNI principles, a required Test Plan & Verification section, and a coverage target — then auto-runs \u002Fplan-eng-review as an independent double-check before execution.","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-plan\u002FSKILL.md",[],[114,115,96,116,117,118,119,27,120,30,121,122,123,124,125,126,127,128,129,130],"write plan","plan","dry","verification","review","tasks","you","auto","eng","coverage","complete","section","for","test plan","target","as","yagni",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":137,"publishedAt":39},"01M71AZ8NDDP5ZMGEE6FSC4FKR","worktrees","Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fworktrees\u002FSKILL.md",[],[133,138,139,140,32,141,142,143,144,145,146,117,147,30,148,149],"implementation","workspace","with","plans","feature","isolation","git","directory","work","git worktrees","selection","Safety",{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":159,"publishedAt":39},"01M71AZ4ZQHTNWFRZVYHKQFP08","web-perf","Analyzes web performance using Chrome DevTools MCP. Measures Core Web Vitals (LCP, INP, CLS) and supplementary metrics (FCP, TBT, Speed Index), identifies render-blocking resources, network dependency chains, layout shifts, caching issues, and accessibility gaps. Use when asked to audit, profile, debug, or optimize page load performance, Lighthouse scores, or site speed. Biases towards retrieval from current documentation over pre-trained knowledge.","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fweb-perf\u002FSKILL.md",[156],{"categoryNo":157,"categoryName":158,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000023","Skill与智能体开发",[160,21,161,162,163,164,165,166,167,30,168,169,170,171,172,173,36,174,175,176],"web","web perf","resources","MCP","layout","optimize","documentation","caching","qa","knowledge","devtools","issues","render","re","chrome devtools","vitals","never",{"skillNo":178,"name":179,"nameZh":6,"description":180,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":181,"categories":182,"keywords":183,"publishedAt":39},"01M71AZ2KZNWYEGKKRMJH8PYG2","verify","Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fverify\u002FSKILL.md",[],[179,124,184,185,146,117,186,187,30,188,32,189,190,191,192],"commands","about","claims","output","assertions","claim","prs","evidence","running",{"skillNo":194,"name":195,"nameZh":6,"description":196,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":197,"categories":198,"keywords":199,"publishedAt":39},"01M71AZ0ACCK7N1QMWQK1FV2HJ","validate-idea","Validate a business idea using the minimalist entrepreneur framework. Use when someone has a business idea and wants to test if it's worth pursuing before building anything.","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fvalidate-idea\u002FSKILL.md",[],[200,201,202,203,204,205,206,30,207,32,208],"validate","idea","validate idea","framework","it","minimalist","test","business","before building"]