[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6R3E33FFRNCPFBQHH44FMRM":3,"skill-same:01M6R3E33FFRNCPFBQHH44FMRM":78},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":13,"repositoryHtmlUrl":51,"repositoryHomepageUrl":6,"ownerHtmlUrl":52,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":53,"install":54,"resources":67},"01M6R3E33FFRNCPFBQHH44FMRM","performance-test-k6",null,"Run and analyze local API\u002FUI performance tests with k6, produce reproducible evidence files, and publish summary results to Jira stories.","ThawedBuffalo\u002Fai-sandbox-mobile-app","ThawedBuffalo","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F7117975?v=4","01M6R3B2VWTABB6Y9EZX0WVFHP","01M6R3B30GCVSPKSM929RGARY0",0,"MIT","https:\u002F\u002Fgithub.com\u002FThawedBuffalo\u002Fai-sandbox-mobile-app\u002Fblob\u002Fmain\u002F skills\u002Fperformance-test-k6\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"test","performance test k6","performance test","k6","performance","produce","publish","Reproducible","run","api","analyze","results","evidence","files","summary","local","tests","with","jira","stories","2026-11-10 10:12:30",false,"---\nname: performance-test-k6\ndescription: 'Run and analyze local API\u002FUI performance tests with k6, produce reproducible evidence files, and publish summary results to Jira stories.'\nlicense: MIT\n---\n\n## Role\nYou are a performance test engineer focused on repeatable, local performance validation using k6.\n\n## Use When\n- User asks for performance or load test execution on local environments\n- User needs evidence for latency\u002Fthroughput\u002Ferror rates attached to Jira stories\n- User asks to validate performance NFRs (for example p95 thresholds)\n\n## Inputs Required\n- Jira story key (example: `CXINIT2-2732`)\n- Target URL (default: `http:\u002F\u002F127.0.0.1:8080`)\n- Scenario file path (default: `70-implementation\u002Ffrontend\u002Ftests\u002Fperformance\u002Fk6.local.js`)\n- Threshold goals (default from k6 scenario if not provided)\n\n## Workflow\n1. Verify prerequisites once:\n   - `k6` CLI installed and available\n   - target app reachable at configured base URL\n2. Run k6 scenario:\n   - `cd 70-implementation\u002Ffrontend`\n   - `TARGET_BASE_URL=\u003Curl> npm run perf:test`\n3. Generate markdown evidence:\n   - `npm run perf:report`\n4. If Jira key is provided, publish to Jira (primary: Jira MCP):\n   - Load `.github\u002Fskills\u002Fjira-mcp-server\u002FSKILL.md`\n   - Use Jira MCP `add_comment` to publish summary to the story\n   - Use Jira MCP `add_remote_link` when a stable evidence URL exists\n   - Fallback only when MCP is unavailable: `npm run perf:jira -- --issue-key \u003Cjira-key>`\n5. Summarize pass\u002Ffail against thresholds and identify bottlenecks.\n\n## Output Artifacts\n- `70-implementation\u002Ftest-results\u002Fperformance\u002Fk6-summary.json`\n- `70-implementation\u002Ftest-results\u002Fperformance\u002Fperf-latest.md`\n\n## Jira Publication Rules\n- If story key is missing, ask once, then proceed with local evidence.\n- Prefer Jira MCP tools over direct REST scripts.\n- If Jira post fails, keep local evidence and report exact failure.\n- Jira comment must include: request volume, p95 latency, failed request rate, and evidence path.\n\n## Constraints\n- Do not claim threshold pass without k6 output.\n- Do not modify production settings for load tests.\n- Keep scenarios deterministic and lightweight for local runs.\n- Always persist evidence before posting Jira updates.\n","## Role\nYou are a performance test engineer focused on repeatable, local performance validation using k6.\n\n## Use When\n- User asks for performance or load test execution on local environments\n- User needs evidence for latency\u002Fthroughput\u002Ferror rates attached to Jira stories\n- User asks to validate performance NFRs (for example p95 thresholds)\n\n## Inputs Required\n- Jira story key (example: `CXINIT2-2732`)\n- Target URL (default: `http:\u002F\u002F127.0.0.1:8080`)\n- Scenario file path (default: `70-implementation\u002Ffrontend\u002Ftests\u002Fperformance\u002Fk6.local.js`)\n- Threshold goals (default from k6 scenario if not provided)\n\n## Workflow\n1. Verify prerequisites once:\n   - `k6` CLI installed and available\n   - target app reachable at configured base URL\n2. Run k6 scenario:\n   - `cd 70-implementation\u002Ffrontend`\n   - `TARGET_BASE_URL=\u003Curl> npm run perf:test`\n3. Generate markdown evidence:\n   - `npm run perf:report`\n4. If Jira key is provided, publish to Jira (primary: Jira MCP):\n   - Load `.github\u002Fskills\u002Fjira-mcp-server\u002FSKILL.md`\n   - Use Jira MCP `add_comment` to publish summary to the story\n   - Use Jira MCP `add_remote_link` when a stable evidence URL exists\n   - Fallback only when MCP is unavailable: `npm run perf:jira -- --issue-key \u003Cjira-key>`\n5. Summarize pass\u002Ffail against thresholds and identify bottlenecks.\n\n## Output Artifacts\n- `70-implementation\u002Ftest-results\u002Fperformance\u002Fk6-summary.json`\n- `70-implementation\u002Ftest-results\u002Fperformance\u002Fperf-latest.md`\n\n## Jira Publication Rules\n- If story key is missing, ask once, then proceed with local evidence.\n- Prefer Jira MCP tools over direct REST scripts.\n- If Jira post fails, keep local evidence and report exact failure.\n- Jira comment must include: request volume, p95 latency, failed request rate, and evidence path.\n\n## Constraints\n- Do not claim threshold pass without k6 output.\n- Do not modify production settings for load tests.\n- Keep scenarios deterministic and lightweight for local runs.\n- Always persist evidence before posting Jira updates.\n",{"name":5,"license":14,"description":7},"main","7122beb16228a5c0e61c112954427dcff880f570"," skills\u002Fperformance-test-k6","https:\u002F\u002Fgithub.com\u002FThawedBuffalo\u002Fai-sandbox-mobile-app","https:\u002F\u002Fgithub.com\u002FThawedBuffalo","2026-04-15 18:08:21",{"source":8,"skillName":5,"commands":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add ThawedBuffalo\u002Fai-sandbox-mobile-app --skill performance-test-k6",{"tool":60,"command":61},"bunx","bunx skills add ThawedBuffalo\u002Fai-sandbox-mobile-app --skill performance-test-k6",{"tool":63,"command":64},"pnpm","pnpm dlx skills add ThawedBuffalo\u002Fai-sandbox-mobile-app --skill performance-test-k6","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FThawedBuffalo\u002Fai-sandbox-mobile-app\u002Fblob\u002Fmain\u002F skills\u002Fperformance-test-k6\u002FSKILL.md",true,[68,74],{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Fk6-quickstart.md","REFERENCE","参考文档",414,"https:\u002F\u002Fgithub.com\u002FThawedBuffalo\u002Fai-sandbox-mobile-app\u002Fblob\u002Fmain\u002F skills\u002Fperformance-test-k6\u002Freferences\u002Fk6-quickstart.md",{"path":75,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":76,"sourceHtmlUrl":77},"templates\u002Fperf-comment-template.md",354,"https:\u002F\u002Fgithub.com\u002FThawedBuffalo\u002Fai-sandbox-mobile-app\u002Fblob\u002Fmain\u002F skills\u002Fperformance-test-k6\u002Ftemplates\u002Fperf-comment-template.md",[79,100,119,145,167,189],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":43},"01M6R3EVDKPZJEHC8QAEAFH5HE","scrum-story-estimation","Estimate stories for sprint planning using relative sizing, confidence, assumptions, dependency flags, and capacity-fit recommendations.","https:\u002F\u002Fgithub.com\u002FThawedBuffalo\u002Fai-sandbox-mobile-app\u002Fblob\u002Fmain\u002F skills\u002Fscrum-story-estimation\u002FSKILL.md",[],[86,87,88,89,90,91,92,93,94,95,96,97,98,99,42],"scrum","Story","estimation","scrum story estimation","capacity","planning","dependency","flags","recommendations","sprint planning","fit","sprint","for","estimate",{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":43},"01M6R3ENKGC4PB0W4YCDK68H5P","scrum-jira-sprint-planning","Create Jira board and sprint planning outputs from a backlog: board readiness checks, optional board\u002Fsprint creation steps, sprint goal, sprint backlog, dependencies, risks, DoR\u002FDoD checks, and standup prompts.","https:\u002F\u002Fgithub.com\u002FThawedBuffalo\u002Fai-sandbox-mobile-app\u002Fblob\u002Fmain\u002F skills\u002Fscrum-jira-sprint-planning\u002FSKILL.md",[],[41,91,86,95,97,107,108,109,110,111,112,113,114,115,116,117,118],"scrum jira sprint planning","create","standup","board","goal","prompts","backlog","dependencies","creation","readiness","dod","outputs",{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":126,"publishedAt":43},"01M6R3ED2GK2V3V5V6S68GNQNN","quality-engineer-playwright","Explore a web app, identify critical user flows, generate Playwright tests, execute and stabilize them, and report production-ready quality evidence.","https:\u002F\u002Fgithub.com\u002FThawedBuffalo\u002Fai-sandbox-mobile-app\u002Fblob\u002Fmain\u002F skills\u002Fquality-engineer-playwright\u002FSKILL.md",[125],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[127,128,129,130,131,132,133,134,135,136,137,35,138,39,139,140,141,142,143,144],"playwright","quality","engineer","quality engineer playwright","web","generate","report","Production","explore","user","execute","ready","app","critical","web app","quality evidence","flows","production-ready",{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":156,"publishedAt":43},"01M6R3E8YVS9B3PYRHJ46NYJQQ","prd-authoring","Create a Product Requirements Document (PRD) by synthesizing transcripts, emails, documents, PDFs, and web inputs.","https:\u002F\u002Fgithub.com\u002FThawedBuffalo\u002Fai-sandbox-mobile-app\u002Fblob\u002Fmain\u002F skills\u002Fprd-authoring\u002FSKILL.md",[151],{"categoryNo":152,"categoryName":153,"taxonomyType":154,"taxonomyTypeDesc":155},"01JBSEEDCAT000000000000031","产品经理","PROFESSION","适用职业",[157,158,159,131,160,108,161,162,163,164,165,166],"prd","prd authoring","authoring","documents","product","document","requirements","emails","Product Requirements","transcripts",{"skillNo":168,"name":169,"nameZh":6,"description":170,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":171,"categories":172,"keywords":173,"publishedAt":43},"01M6R3DH11PYCXA77ERBXTW8JJ","jira-backlog-generation","Turn a PRD, business ask, or feature brief into a Jira-ready backlog: one Epic, supporting Stories, NFR tasks, and Gherkin acceptance criteria. Optionally creates issues in Jira Cloud via REST API.","https:\u002F\u002Fgithub.com\u002FThawedBuffalo\u002Fai-sandbox-mobile-app\u002Fblob\u002Fmain\u002F skills\u002Fjira-backlog-generation\u002FSKILL.md",[],[41,113,174,175,176,177,178,179,180,181,32,182,183,138,184,185,186,187,188,42],"generation","jira backlog generation","tasks","issues","acceptance","cloud","brief","REST","ask","business","acceptance criteria","rest api","feature","via","EPIC",{"skillNo":190,"name":191,"nameZh":6,"description":192,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":193,"categories":194,"keywords":204,"publishedAt":43},"01M6R3D63H2Q30V48G7SZEJ9AA","figma-ux-design","Turn product requirements into Figma-ready UX design outputs using Figma MCP when available: UX brief, information architecture, user flows, wireframes, component guidance, and handoff notes.","https:\u002F\u002Fgithub.com\u002FThawedBuffalo\u002Fai-sandbox-mobile-app\u002Fblob\u002Fmain\u002F skills\u002Ffigma-ux-design\u002FSKILL.md",[195,198,201],{"categoryNo":196,"categoryName":197,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":199,"categoryName":200,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":202,"categoryName":203,"taxonomyType":154,"taxonomyTypeDesc":155},"01JBSEEDCAT000000000000032","设计师",[205,206,207,208,209,210,211,212,213,161,180,138,163,214,215,143,216,217,118,218],"design","ux","figma","ux design","figma ux design","MCP","component","architecture","notes","wireframes","information","information architecture","figma mcp","when"]