[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CFEBGABS4K9W7BEBTJWMKF":3,"skill-same:01M6CFEBGABS4K9W7BEBTJWMKF":74},{"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":23,"publishedAt":35,"linkOnly":36,"markdownContent":37,"markdownBody":38,"frontMatter":39,"refName":40,"commitSha":41,"skillDirectory":42,"forksCount":43,"repositoryHtmlUrl":44,"repositoryHomepageUrl":45,"ownerHtmlUrl":46,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":47,"install":48,"resources":61},"01M6CFEBGABS4K9W7BEBTJWMKF","debug",null,"Use this skill to locate a runtime bug. Add targeted instrumentation, collect reproduction evidence, and confirm the root cause before changing code.","openBitFun\u002FOpenBitFun","openBitFun","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F272396808?v=4","01M70PGYVNDWCH7MV3FRCZWGVA","OpenBitFun","01M6CFDJ2B5TESE4PW4Y04PPY4",4016,"MIT","https:\u002F\u002Fgithub.com\u002FopenBitFun\u002FOpenBitFun\u002Fblob\u002Fmain\u002Fsrc\u002Fcrates\u002Fassembly\u002Fcore\u002Fbuiltin_skills\u002Fdebug\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[5,24,25,26,27,28,29,30,31,32,33,34],"code","collect","use","evidence","bug","instrumentation","runtime","add","locate","root","root cause","2026-11-10 10:12:30",false,"---\r\nname: debug\ndescription: Use this skill to locate a runtime bug. Add targeted instrumentation, collect reproduction evidence, and confirm the root cause before changing code.\r\n---\r\n\r\n# Evidence-driven debugging\r\n\r\nEvidence-driven debugging mode activated. Follow the workflow below:\r\n\r\n1. Generate multiple hypotheses based on the problem described by the user.\r\n\r\n2. Insert narrow, hypothesis-specific instrumentation for each hypothesis.\r\n\r\n3. Provide reproduction steps and ask the user to reproduce the issue.\r\n\r\n4. Read the captured runtime data and identify the confirmed root cause.\r\n\r\n5. Implement fix based on the confirmed root cause.\r\n\r\n6. If the user confirms the issue has been resolved, clean up all inserted log \r\n   statements; otherwise, add more logs or generate new hypotheses\r\n\r\nIMPORTANT: Do not implement a fix until it is supported by runtime evidence.\r\nIMPORTANT: Do not clean up instrumentation until the user confirms the issue\r\nhas been fixed.\r\n\r\n## Rules\r\n\r\n- Before reading `debug-agent.log`, check its size and approximate entry count.\r\n  Do not read a large log end-to-end in one pass; filter by hypothesis ID,\r\n  location, time range, or other relevant keywords, and write a small analysis\r\n  script when aggregation or correlation is needed.\r\n\r\n- Before each new request for the user to reproduce the issue, clear the\r\n  existing `debug-agent.log` so that the next capture is attributable to that\r\n  reproduction. If the historical entries may be needed, create a separate\r\n  backup first (for example, with a timestamp or reproduction-batch suffix),\r\n  then clear the active log.\r\n\r\n- Separate diagnosis from repair selection. Assess whether the confirmed cause\r\n  calls for a root-cause fix, a smaller mitigation, or both. A mitigation that\r\n  merely masks the symptom must not be presented as the root-cause fix.\r\n\r\n- If there are multiple viable fixes, or the root-cause fix has a materially\r\n  larger change surface, present the options, trade-offs, and verification\r\n  implications to the user and ask them to choose before editing production\r\n  code. If one proportionate root-cause fix is clearly preferred, explain why\r\n  and proceed only after the runtime evidence supports it.\r\n\r\n## How to Write to Log Files\r\n\r\n1. All logs must be written to `{project_root}\u002Fdebug-agent.log`. Note: absolute paths must be used.\r\n\r\n2. Inserted log statements should be wrapped with appropriate comment statements for location and cleanup\r\n\r\n3. Log content should include: hypothesis ID (A\u002FB\u002FC\u002F...), log location (e.g., api-get_weather), and specific information\r\n\r\n4. Backend: write via file IO\r\n```rust\r\n\u002F\u002F #region agent log\r\n{\r\n    use std::io::Write;\r\n    if let Ok(mut f) = std::fs::OpenOptions::new().create(true).append(true).open(r\"absolute\\path\\to\\debug-agent.log\") {\r\n        let _ = writeln!(f, \"log_content\");\r\n    }\r\n}\r\n\u002F\u002F #endregion\r\n```\r\n\r\n5. Frontend: start the bundled receiver script, then write via `fetch`.\r\n\r\n```bash\r\nnode \u003Cthis-skill-directory>\u002Fscripts\u002Fdebug-log-server.mjs --root \u003Cproject-root>\r\n```\r\n\r\nThis uses the default local port (7469) and writes to `debug-agent.log` in the\r\nproject root. Run the script with `--help` to see options for a different\r\nproject root, port, log path, or startup behavior.\r\n\r\nInserted frontend logs should use this pattern:\r\n\r\n```ts\r\n\u002F\u002F #region agent log\r\nvoid fetch('http:\u002F\u002F127.0.0.1:7469\u002Flog', {\r\n  method: 'POST',\r\n  headers: { 'Content-Type': 'application\u002Fjson' },\r\n  body: JSON.stringify({\r\n    id: 'A',\r\n    loc: 'ComponentName.eventName',\r\n    msg: 'specific observation',\r\n    data: { value },\r\n  }),\r\n}).catch(() => {});\r\n\u002F\u002F #endregion\r\n```\r\n\r\nThe receiver exposes:\r\n- `POST \u002Fclear` to clear the log file\r\n- `GET \u002Fhealth` to confirm the server and log path\r\n\r\nKeep frontend instrumentation project-agnostic: avoid importing app-specific debug utilities unless the project already has a logging adapter that can POST to this receiver cleanly.\r\n","# Evidence-driven debugging\r\n\r\nEvidence-driven debugging mode activated. Follow the workflow below:\r\n\r\n1. Generate multiple hypotheses based on the problem described by the user.\r\n\r\n2. Insert narrow, hypothesis-specific instrumentation for each hypothesis.\r\n\r\n3. Provide reproduction steps and ask the user to reproduce the issue.\r\n\r\n4. Read the captured runtime data and identify the confirmed root cause.\r\n\r\n5. Implement fix based on the confirmed root cause.\r\n\r\n6. If the user confirms the issue has been resolved, clean up all inserted log \r\n   statements; otherwise, add more logs or generate new hypotheses\r\n\r\nIMPORTANT: Do not implement a fix until it is supported by runtime evidence.\r\nIMPORTANT: Do not clean up instrumentation until the user confirms the issue\r\nhas been fixed.\r\n\r\n## Rules\r\n\r\n- Before reading `debug-agent.log`, check its size and approximate entry count.\r\n  Do not read a large log end-to-end in one pass; filter by hypothesis ID,\r\n  location, time range, or other relevant keywords, and write a small analysis\r\n  script when aggregation or correlation is needed.\r\n\r\n- Before each new request for the user to reproduce the issue, clear the\r\n  existing `debug-agent.log` so that the next capture is attributable to that\r\n  reproduction. If the historical entries may be needed, create a separate\r\n  backup first (for example, with a timestamp or reproduction-batch suffix),\r\n  then clear the active log.\r\n\r\n- Separate diagnosis from repair selection. Assess whether the confirmed cause\r\n  calls for a root-cause fix, a smaller mitigation, or both. A mitigation that\r\n  merely masks the symptom must not be presented as the root-cause fix.\r\n\r\n- If there are multiple viable fixes, or the root-cause fix has a materially\r\n  larger change surface, present the options, trade-offs, and verification\r\n  implications to the user and ask them to choose before editing production\r\n  code. If one proportionate root-cause fix is clearly preferred, explain why\r\n  and proceed only after the runtime evidence supports it.\r\n\r\n## How to Write to Log Files\r\n\r\n1. All logs must be written to `{project_root}\u002Fdebug-agent.log`. Note: absolute paths must be used.\r\n\r\n2. Inserted log statements should be wrapped with appropriate comment statements for location and cleanup\r\n\r\n3. Log content should include: hypothesis ID (A\u002FB\u002FC\u002F...), log location (e.g., api-get_weather), and specific information\r\n\r\n4. Backend: write via file IO\r\n```rust\r\n\u002F\u002F #region agent log\r\n{\r\n    use std::io::Write;\r\n    if let Ok(mut f) = std::fs::OpenOptions::new().create(true).append(true).open(r\"absolute\\path\\to\\debug-agent.log\") {\r\n        let _ = writeln!(f, \"log_content\");\r\n    }\r\n}\r\n\u002F\u002F #endregion\r\n```\r\n\r\n5. Frontend: start the bundled receiver script, then write via `fetch`.\r\n\r\n```bash\r\nnode \u003Cthis-skill-directory>\u002Fscripts\u002Fdebug-log-server.mjs --root \u003Cproject-root>\r\n```\r\n\r\nThis uses the default local port (7469) and writes to `debug-agent.log` in the\r\nproject root. Run the script with `--help` to see options for a different\r\nproject root, port, log path, or startup behavior.\r\n\r\nInserted frontend logs should use this pattern:\r\n\r\n```ts\r\n\u002F\u002F #region agent log\r\nvoid fetch('http:\u002F\u002F127.0.0.1:7469\u002Flog', {\r\n  method: 'POST',\r\n  headers: { 'Content-Type': 'application\u002Fjson' },\r\n  body: JSON.stringify({\r\n    id: 'A',\r\n    loc: 'ComponentName.eventName',\r\n    msg: 'specific observation',\r\n    data: { value },\r\n  }),\r\n}).catch(() => {});\r\n\u002F\u002F #endregion\r\n```\r\n\r\nThe receiver exposes:\r\n- `POST \u002Fclear` to clear the log file\r\n- `GET \u002Fhealth` to confirm the server and log path\r\n\r\nKeep frontend instrumentation project-agnostic: avoid importing app-specific debug utilities unless the project already has a logging adapter that can POST to this receiver cleanly.\r\n",{"name":5,"description":7},"main","3b649c6a86d5ada26f67391412fd0aee90b95652","src\u002Fcrates\u002Fassembly\u002Fcore\u002Fbuiltin_skills\u002Fdebug",305,"https:\u002F\u002Fgithub.com\u002FopenBitFun\u002FOpenBitFun","openbitfun.com","https:\u002F\u002Fgithub.com\u002FopenBitFun","2026-11-13 18:13:20",{"source":8,"skillName":5,"commands":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add openBitFun\u002FOpenBitFun --skill debug",{"tool":54,"command":55},"bunx","bunx skills add openBitFun\u002FOpenBitFun --skill debug",{"tool":57,"command":58},"pnpm","pnpm dlx skills add openBitFun\u002FOpenBitFun --skill debug","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FopenBitFun\u002FOpenBitFun\u002Fblob\u002Fmain\u002Fsrc\u002Fcrates\u002Fassembly\u002Fcore\u002Fbuiltin_skills\u002Fdebug\u002FSKILL.md",true,[62,68],{"path":63,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Fscanning-methodology.md","REFERENCE","参考文档",3723,"https:\u002F\u002Fgithub.com\u002Fngocsangyem\u002FMeowKit\u002Fblob\u002Fmain\u002Fpackages\u002Fmewkit\u002Fsrc\u002Fmigrate\u002Fmodules\u002Fcursor\u002Froot\u002F.cursor\u002Fskills\u002Fmk-vulnerability-scanner\u002Freferences\u002Fscanning-methodology.md",{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"scripts\u002Fdebug-log-server.mjs","SCRIPT","脚本",5430,"https:\u002F\u002Fgithub.com\u002FGCWing\u002FOpenBitFun\u002Fblob\u002Fmain\u002Fsrc\u002Fcrates\u002Fassembly\u002Fcore\u002Fbuiltin_skills\u002Fdebug\u002Fscripts\u002Fdebug-log-server.mjs",[75,95,123,159,187,206],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":35},"01M6CFEP4X1GN4X24VH42JWHQ2","miniapp-dev","Generate, operate, and refine OpenBitFun MiniApps. Use when the user wants a new MiniApp, asks the Agent to inspect or operate a running MiniApp, or wants an existing MiniApp redesigned or extended. Typical triggers: \"做一个小应用\", \"操作这个 MiniApp\", \"查看小应用当前状态\", \"改造 mini app\".","https:\u002F\u002Fgithub.com\u002FopenBitFun\u002FOpenBitFun\u002Fblob\u002Fmain\u002Fsrc\u002Fcrates\u002Fassembly\u002Fcore\u002Fbuiltin_skills\u002Fminiapp-dev\u002FSKILL.md",[],[82,83,26,84,85,86,87,88,89,90,91,92,93,94],"dev","miniapp dev","generate","user","running","app","operate","inspect","triggers","new","Existing","when","refine",{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":106,"publishedAt":35},"01M6CFF33T7RM4A44X3X0K6YXN","openbitfun-frontend-dev","Safely customize the running packaged OpenBitFun desktop frontend through a draft, a provisional hot apply, and a 15-second user-confirmed rollback window. Use only in OpenBitFun Creative mode when the user asks to change OpenBitFun's own client UI.","https:\u002F\u002Fgithub.com\u002FopenBitFun\u002FOpenBitFun\u002Fblob\u002Fmain\u002Fsrc\u002Fcrates\u002Fassembly\u002Fcore\u002Fbuiltin_skills\u002Fopenbitfun-frontend-dev\u002FSKILL.md",[101],{"categoryNo":102,"categoryName":103,"taxonomyType":104,"taxonomyTypeDesc":105},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",[107,82,108,109,110,26,111,112,113,114,115,116,85,86,117,118,93,119,120,121,122],"frontend","openbitfun frontend dev","frontend dev","only","customize","change","desktop","rollback","creative","ui","second","mode","apply","draft","window","client",{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":127,"sourceHtmlUrl":128,"categories":129,"keywords":142,"publishedAt":35},"01M6CFF99YP8CWRVWG5C6S06YS","ppt-design","使用 HTML 设计与生成高质量演讲幻灯片（PPT\u002FDeck）。当用户希望生成、设计、修改幻灯片、deck、slides、presentation、汇报、提案、pitch、课件时触发。主干：1280×720px 可编辑 HTML 幻灯片 + 唯一 editable HTML→EditableSlideScene→OOXML 管线 + 数据\u002F信息可视化意识 + 5 种设计哲学 + 反 AI slop + 单页自包含 `slide-XX.html`。不生图；缺图用可编辑原语或占位并标注建议补图。","https:\u002F\u002Fgithub.com\u002FopenBitFun\u002FOpenBitFun\u002Fblob\u002Fmain\u002Fsrc\u002Fcrates\u002Fassembly\u002Fcore\u002Fbuiltin_skills\u002Fppt-design\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FopenBitFun\u002FOpenBitFun\u002Fblob\u002Fmain\u002Fsrc\u002Fcrates\u002Fassembly\u002Fcore\u002Fbuiltin_skills\u002Fppt-design\u002FSKILL.md",[130,133,136,139],{"categoryNo":131,"categoryName":132,"taxonomyType":104,"taxonomyTypeDesc":105},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":134,"categoryName":135,"taxonomyType":104,"taxonomyTypeDesc":105},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":137,"categoryName":138,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000032","设计师",{"categoryNo":140,"categoryName":141,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000033","数据分析师",[143,144,145,146,147,148,149,150,151,152,153,154,155,156,157,158],"pptx","design","ppt design","slides","deck","生成","提案","html","演讲","slop","pitch","可视化","ai slop","presentation","editable","数据",{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":163,"categories":164,"keywords":168,"publishedAt":35},"01M6CFE1RT1YFKD6RCDE6KRY0T","create-agent","Create or update OpenBitFun custom modes and subagents. Turn the user's needs into a role prompt and a suitable tool selection, then save an agent definition. Use for reusable roles, not ordinary delegation to an existing subagent.","https:\u002F\u002Fgithub.com\u002FopenBitFun\u002FOpenBitFun\u002Fblob\u002Fmain\u002Fsrc\u002Fcrates\u002Fassembly\u002Fcore\u002Fbuiltin_skills\u002Fcreate-agent\u002FSKILL.md",[165],{"categoryNo":166,"categoryName":167,"taxonomyType":104,"taxonomyTypeDesc":105},"01JBSEEDCAT000000000000023","Skill与智能体开发",[169,170,171,172,173,26,174,175,176,177,85,178,179,180,181,182,183,184,92,185,186],"create","create agent","tool","selection","delegation","prompt","reusable","subagent","update","subagents","save","definition","agent definition","for","modes","custom","roles","role",{"skillNo":188,"name":189,"nameZh":6,"description":190,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":191,"categories":192,"keywords":193,"publishedAt":35},"01M6CFF5WX7MT7KVVQ9HTH6EYK","plan","Research and write an actionable implementation plan without implementing it. Use when the user asks to plan, design an approach, or inspect a change before coding; stop applying the planning restriction once the user explicitly asks to implement.","https:\u002F\u002Fgithub.com\u002FopenBitFun\u002FOpenBitFun\u002Fblob\u002Fmain\u002Fsrc\u002Fcrates\u002Fassembly\u002Fcore\u002Fbuiltin_skills\u002Fplan\u002FSKILL.md",[],[189,194,144,26,195,112,196,197,198,199,200,85,201,89,202,203,93,204,205],"planning","implement","research","write","implementation","coding","stop","actionable","implementing","implementation plan","to plan","it",{"skillNo":207,"name":208,"nameZh":6,"description":209,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":210,"categories":211,"keywords":213,"publishedAt":35},"01M6CFEGQAWVPVJ1DPTHG6VG62","find-skills","Discover and install reusable agent skills when users ask for capabilities, workflows, or domain-specific help that may already exist as an installable skill.","https:\u002F\u002Fgithub.com\u002FopenBitFun\u002FOpenBitFun\u002Fblob\u002Fmain\u002Fsrc\u002Fcrates\u002Fassembly\u002Fcore\u002Fbuiltin_skills\u002Ffind-skills\u002FSKILL.md",[212],{"categoryNo":166,"categoryName":167,"taxonomyType":104,"taxonomyTypeDesc":105},[214,215,51,216,175,217,218,219,220,221,93,222,223,182,224,225],"find skills","find","workflows","ask","capabilities","help","install","discover","as","domain","domain-specific","users"]