[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71FXPBT3CP80D8P1T8GKPC4":3,"skill-same:01M71FXPBT3CP80D8P1T8GKPC4":81},{"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":51,"repositoryHtmlUrl":52,"repositoryHomepageUrl":6,"ownerHtmlUrl":53,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":54,"install":55,"resources":68},"01M71FXPBT3CP80D8P1T8GKPC4","unity-compile-fixer",null,"Detect and resolve Unity C# compilation errors using VSCode diagnostics. Use this skill when Unity projects have compilation errors that need diagnosis and automated fixes. Analyzes errors from VSCode Language Server, proposes solutions based on error patterns, and handles version control conflicts for Unity projects.","JSGforever\u002Fskillguard","JSGforever","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F85541948?v=4","01M71FQD3E132VMR5F4TAYX3YS","01M71FQD4DYW0XJ4XQ4YQH75Y9",2,"GPL-3.0","https:\u002F\u002Fgithub.com\u002FJSGforever\u002Fskillguard\u002Fblob\u002Fmain\u002Fbenchmarks\u002Ffinal\u002Fskills\u002Fasset1__Dev-GOM--unity-compile-fixer\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"compile","unity compile fixer","fixer","unity","control","detect","solutions","server","C#","conflicts","vscode","version","when","use","errors","for","fixes","error patterns","projects","error","2026-11-10 10:12:30",false,"---\nname: unity-compile-fixer\ndescription: Detect and resolve Unity C# compilation errors using VSCode diagnostics. Use this skill when Unity projects have compilation errors that need diagnosis and automated fixes. Analyzes errors from VSCode Language Server, proposes solutions based on error patterns, and handles version control conflicts for Unity projects.\n---\n\n# Unity Compile Fixer\n\n## Overview\n\nThis skill enables automatic detection and resolution of Unity C# compilation errors by leveraging VSCode's diagnostic system. It collects real-time errors from the OmniSharp C# language server, analyzes error patterns against a curated database of common Unity issues, and proposes context-aware solutions for user approval before applying fixes.\n\n## When to Use This Skill\n\nUse this skill when:\n- Unity projects report C# compilation errors in VSCode\n- Need to diagnose the root cause of Unity compiler errors (CS* error codes)\n- Want automated fix suggestions for common Unity scripting issues\n- Working with Unity projects that have version control integration (Git, Unity Collaborate, Plastic SCM)\n- Need to handle Unity .meta file conflicts\n\n**Example user requests:**\n- \"Check Unity compilation errors and help me fix them\"\n- \"My Unity project has compiler errors, can you diagnose and fix?\"\n- \"Unity scripts are not compiling, what's wrong?\"\n- \"Fix the C# errors in my Unity project\"\n\n## Workflow\n\nFollow this workflow when the skill is invoked:\n\n### 1. Detect Compilation Errors\n\nUse the `mcp__ide__getDiagnostics` tool to collect errors from VSCode:\n\n```typescript\n\u002F\u002F Collect all project diagnostics\nmcp__ide__getDiagnostics()\n\n\u002F\u002F Or target specific Unity script files\nmcp__ide__getDiagnostics({ uri: \"file:\u002F\u002F\u002Fpath\u002Fto\u002FPlayerController.cs\" })\n```\n\nFilter the diagnostics to focus on Unity-relevant errors:\n- **Severity**: Only process errors with `severity: \"Error\"` (ignore warnings)\n- **Source**: Only process `source: \"csharp\"` (OmniSharp C# diagnostics)\n- **Error Codes**: Focus on CS* compiler error codes (e.g., CS0246, CS0029, CS1061)\n\n### 2. Analyze Error Patterns\n\nFor each detected error:\n\n1. **Extract error information:**\n   - File path and line number from `uri` and `range`\n   - Error code from `message` (e.g., \"CS0246\")\n   - Full error message text\n\n2. **Match against error pattern database:**\n   - Load `references\u002Ferror-patterns.json`\n   - Find the error code entry (e.g., CS0246)\n   - Retrieve common causes and solutions\n\n3. **Read affected file context:**\n   - Use Read tool to load the file with errors\n   - Examine surrounding code for context\n   - Identify missing imports, incorrect types, or API misuse\n\n### 3. Generate Solution Proposals\n\nFor each error, create a structured fix proposal:\n\n```markdown\n**Error**: CS0246 at PlayerController.cs:45\n**Message**: The type or namespace name 'Rigidbody' could not be found\n\n**Analysis**:\n- Missing using directive for UnityEngine namespace\n- Common Unity API usage pattern\n\n**Proposed Solution**:\nAdd `using UnityEngine;` at the top of PlayerController.cs\n\n**Changes Required**:\n- File: Assets\u002FScripts\u002FPlayerController.cs\n- Action: Insert using directive at line 1\n```\n\n### 4. User Confirmation\n\nBefore applying any fixes:\n\n1. **Present all proposed solutions** in a clear, structured format\n2. **Use AskUserQuestion tool** to get user approval:\n   - List each error and proposed fix\n   - Allow user to approve all, select specific fixes, or cancel\n\n3. **Wait for explicit confirmation** - do not apply fixes automatically\n\n### 5. Apply Approved Fixes\n\nFor each approved fix:\n\n1. **Use Edit tool** to modify the affected file\n2. **Preserve code formatting** and existing structure\n3. **Apply minimal changes** - only fix the specific error\n\nExample:\n```typescript\nEdit({\n  file_path: \"Assets\u002FScripts\u002FPlayerController.cs\",\n  old_string: \"public class PlayerController : MonoBehaviour\",\n  new_string: \"using UnityEngine;\\n\\npublic class PlayerController : MonoBehaviour\"\n})\n```\n\n### 6. Verify Version Control Status\n\nAfter applying fixes:\n\n1. **Check for .meta file conflicts:**\n   - Use Grep to search for Unity .meta files\n   - Verify that script GUID hasn't changed\n   - Check for merge conflict markers (\u003C\u003C\u003C\u003C\u003C\u003C, ======, >>>>>>)\n\n2. **Report VCS status:**\n   - List modified files\n   - Warn about any .meta file issues\n   - Suggest git operations if needed\n\n### 7. Re-validate Compilation\n\nAfter fixes are applied:\n\n1. **Re-run diagnostics** using `mcp__ide__getDiagnostics()`\n2. **Compare error count** before and after\n3. **Report results** to the user:\n   - Number of errors fixed\n   - Remaining errors (if any)\n   - Success rate\n\n## Error Pattern Database\n\nThe skill relies on `references\u002Ferror-patterns.json` for error analysis. This database contains:\n\n- **Error Code**: CS* compiler error code\n- **Description**: Human-readable explanation\n- **Common Causes**: Typical reasons this error occurs in Unity\n- **Solutions**: Step-by-step fix instructions\n- **Unity-Specific Notes**: Unity API considerations\n\nTo analyze an error, load the database and match the error code:\n\n```typescript\nRead({ file_path: \"references\u002Ferror-patterns.json\" })\n\u002F\u002F Parse JSON and find errorCode entry\n```\n\n## Analysis Scripts\n\nThe skill includes Node.js scripts in `scripts\u002F` for complex error analysis:\n\n### scripts\u002Fanalyze-diagnostics.js\n\nProcesses VSCode diagnostics JSON output and extracts Unity-relevant errors.\n\n**Usage:**\n```bash\nnode scripts\u002Fanalyze-diagnostics.js \u003Cdiagnostics-json-file>\n```\n\n**Output:**\n- Filtered list of Unity C# compilation errors\n- Error classification by type (missing imports, type errors, API issues)\n- Severity and file location information\n\nThis script can be run independently or invoked from the SKILL.md workflow when detailed analysis is needed.\n\n## Best Practices\n\nWhen using this skill:\n\n1. **Start with full project diagnostics** - use `mcp__ide__getDiagnostics()` without parameters to get complete error picture\n2. **Prioritize errors by severity and dependency** - fix foundational errors (missing imports) before downstream errors\n3. **Batch related fixes** - group errors from the same file for efficient editing\n4. **Always verify VCS status** - Unity .meta files are critical for version control\n5. **Re-validate after fixes** - ensure errors are actually resolved\n\n## Resources\n\n### scripts\u002Fanalyze-diagnostics.js\nNode.js script for processing VSCode diagnostics and filtering Unity-specific C# errors.\n\n### references\u002Ferror-patterns.json\nCurated database of common Unity C# compilation errors with solutions and Unity-specific guidance.\n","# Unity Compile Fixer\n\n## Overview\n\nThis skill enables automatic detection and resolution of Unity C# compilation errors by leveraging VSCode's diagnostic system. It collects real-time errors from the OmniSharp C# language server, analyzes error patterns against a curated database of common Unity issues, and proposes context-aware solutions for user approval before applying fixes.\n\n## When to Use This Skill\n\nUse this skill when:\n- Unity projects report C# compilation errors in VSCode\n- Need to diagnose the root cause of Unity compiler errors (CS* error codes)\n- Want automated fix suggestions for common Unity scripting issues\n- Working with Unity projects that have version control integration (Git, Unity Collaborate, Plastic SCM)\n- Need to handle Unity .meta file conflicts\n\n**Example user requests:**\n- \"Check Unity compilation errors and help me fix them\"\n- \"My Unity project has compiler errors, can you diagnose and fix?\"\n- \"Unity scripts are not compiling, what's wrong?\"\n- \"Fix the C# errors in my Unity project\"\n\n## Workflow\n\nFollow this workflow when the skill is invoked:\n\n### 1. Detect Compilation Errors\n\nUse the `mcp__ide__getDiagnostics` tool to collect errors from VSCode:\n\n```typescript\n\u002F\u002F Collect all project diagnostics\nmcp__ide__getDiagnostics()\n\n\u002F\u002F Or target specific Unity script files\nmcp__ide__getDiagnostics({ uri: \"file:\u002F\u002F\u002Fpath\u002Fto\u002FPlayerController.cs\" })\n```\n\nFilter the diagnostics to focus on Unity-relevant errors:\n- **Severity**: Only process errors with `severity: \"Error\"` (ignore warnings)\n- **Source**: Only process `source: \"csharp\"` (OmniSharp C# diagnostics)\n- **Error Codes**: Focus on CS* compiler error codes (e.g., CS0246, CS0029, CS1061)\n\n### 2. Analyze Error Patterns\n\nFor each detected error:\n\n1. **Extract error information:**\n   - File path and line number from `uri` and `range`\n   - Error code from `message` (e.g., \"CS0246\")\n   - Full error message text\n\n2. **Match against error pattern database:**\n   - Load `references\u002Ferror-patterns.json`\n   - Find the error code entry (e.g., CS0246)\n   - Retrieve common causes and solutions\n\n3. **Read affected file context:**\n   - Use Read tool to load the file with errors\n   - Examine surrounding code for context\n   - Identify missing imports, incorrect types, or API misuse\n\n### 3. Generate Solution Proposals\n\nFor each error, create a structured fix proposal:\n\n```markdown\n**Error**: CS0246 at PlayerController.cs:45\n**Message**: The type or namespace name 'Rigidbody' could not be found\n\n**Analysis**:\n- Missing using directive for UnityEngine namespace\n- Common Unity API usage pattern\n\n**Proposed Solution**:\nAdd `using UnityEngine;` at the top of PlayerController.cs\n\n**Changes Required**:\n- File: Assets\u002FScripts\u002FPlayerController.cs\n- Action: Insert using directive at line 1\n```\n\n### 4. User Confirmation\n\nBefore applying any fixes:\n\n1. **Present all proposed solutions** in a clear, structured format\n2. **Use AskUserQuestion tool** to get user approval:\n   - List each error and proposed fix\n   - Allow user to approve all, select specific fixes, or cancel\n\n3. **Wait for explicit confirmation** - do not apply fixes automatically\n\n### 5. Apply Approved Fixes\n\nFor each approved fix:\n\n1. **Use Edit tool** to modify the affected file\n2. **Preserve code formatting** and existing structure\n3. **Apply minimal changes** - only fix the specific error\n\nExample:\n```typescript\nEdit({\n  file_path: \"Assets\u002FScripts\u002FPlayerController.cs\",\n  old_string: \"public class PlayerController : MonoBehaviour\",\n  new_string: \"using UnityEngine;\\n\\npublic class PlayerController : MonoBehaviour\"\n})\n```\n\n### 6. Verify Version Control Status\n\nAfter applying fixes:\n\n1. **Check for .meta file conflicts:**\n   - Use Grep to search for Unity .meta files\n   - Verify that script GUID hasn't changed\n   - Check for merge conflict markers (\u003C\u003C\u003C\u003C\u003C\u003C, ======, >>>>>>)\n\n2. **Report VCS status:**\n   - List modified files\n   - Warn about any .meta file issues\n   - Suggest git operations if needed\n\n### 7. Re-validate Compilation\n\nAfter fixes are applied:\n\n1. **Re-run diagnostics** using `mcp__ide__getDiagnostics()`\n2. **Compare error count** before and after\n3. **Report results** to the user:\n   - Number of errors fixed\n   - Remaining errors (if any)\n   - Success rate\n\n## Error Pattern Database\n\nThe skill relies on `references\u002Ferror-patterns.json` for error analysis. This database contains:\n\n- **Error Code**: CS* compiler error code\n- **Description**: Human-readable explanation\n- **Common Causes**: Typical reasons this error occurs in Unity\n- **Solutions**: Step-by-step fix instructions\n- **Unity-Specific Notes**: Unity API considerations\n\nTo analyze an error, load the database and match the error code:\n\n```typescript\nRead({ file_path: \"references\u002Ferror-patterns.json\" })\n\u002F\u002F Parse JSON and find errorCode entry\n```\n\n## Analysis Scripts\n\nThe skill includes Node.js scripts in `scripts\u002F` for complex error analysis:\n\n### scripts\u002Fanalyze-diagnostics.js\n\nProcesses VSCode diagnostics JSON output and extracts Unity-relevant errors.\n\n**Usage:**\n```bash\nnode scripts\u002Fanalyze-diagnostics.js \u003Cdiagnostics-json-file>\n```\n\n**Output:**\n- Filtered list of Unity C# compilation errors\n- Error classification by type (missing imports, type errors, API issues)\n- Severity and file location information\n\nThis script can be run independently or invoked from the SKILL.md workflow when detailed analysis is needed.\n\n## Best Practices\n\nWhen using this skill:\n\n1. **Start with full project diagnostics** - use `mcp__ide__getDiagnostics()` without parameters to get complete error picture\n2. **Prioritize errors by severity and dependency** - fix foundational errors (missing imports) before downstream errors\n3. **Batch related fixes** - group errors from the same file for efficient editing\n4. **Always verify VCS status** - Unity .meta files are critical for version control\n5. **Re-validate after fixes** - ensure errors are actually resolved\n\n## Resources\n\n### scripts\u002Fanalyze-diagnostics.js\nNode.js script for processing VSCode diagnostics and filtering Unity-specific C# errors.\n\n### references\u002Ferror-patterns.json\nCurated database of common Unity C# compilation errors with solutions and Unity-specific guidance.\n",{"name":5,"description":7},"main","f2ec4b3b9133d34eeaf9b38e4b0a97e8e5705a7f","benchmarks\u002Ffinal\u002Fskills\u002Fasset1__Dev-GOM--unity-compile-fixer",0,"https:\u002F\u002Fgithub.com\u002FJSGforever\u002Fskillguard","https:\u002F\u002Fgithub.com\u002FJSGforever","2026-08-29 18:27:56",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add JSGforever\u002Fskillguard --skill unity-compile-fixer",{"tool":61,"command":62},"bunx","bunx skills add JSGforever\u002Fskillguard --skill unity-compile-fixer",{"tool":64,"command":65},"pnpm","pnpm dlx skills add JSGforever\u002Fskillguard --skill unity-compile-fixer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FJSGforever\u002Fskillguard\u002Fblob\u002Fmain\u002Fbenchmarks\u002Ffinal\u002Fskills\u002Fasset1__Dev-GOM--unity-compile-fixer\u002FSKILL.md",true,[69,75],{"path":70,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":74},"references\u002Ferror-patterns.json","REFERENCE","参考文档",11738,"https:\u002F\u002Fgithub.com\u002FJSGforever\u002Fskillguard\u002Fblob\u002Fmain\u002Fbenchmarks\u002Ffinal\u002Fskills\u002Fasset1__Dev-GOM--unity-compile-fixer\u002Freferences\u002Ferror-patterns.json",{"path":76,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":79,"sourceHtmlUrl":80},"scripts\u002Fanalyze-diagnostics.js","SCRIPT","脚本",5746,"https:\u002F\u002Fgithub.com\u002FJSGforever\u002Fskillguard\u002Fblob\u002Fmain\u002Fbenchmarks\u002Ffinal\u002Fskills\u002Fasset1__Dev-GOM--unity-compile-fixer\u002Fscripts\u002Fanalyze-diagnostics.js",[82,109,125,152,174,193],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":89,"publishedAt":43},"01M71HY2SNXBA9Q00WZDTZQ31Z","skillguard-codex-scanner","Hybrid deterministic+LLM agent-skill security scanner. Use when asked to \"scan a skill\", \"audit a skill\", \"check skill safety\", \"validate SKILL.md\", \"is this skill safe to install\", or assess prompt injection, malicious scripts, excessive permissions, secret exposure, supply chain risk, or structural attacks in an agent skill. Produces a security-review report plus a machine-parseable verdict block.","https:\u002F\u002Fgithub.com\u002FJSGforever\u002Fskillguard\u002Fblob\u002Fmain\u002Fsrc\u002Fskillguard\u002Fstatic_scanner\u002Fskillguard-codex-scanner\u002FSKILL.md",[88],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[90,91,92,93,94,95,96,97,98,99,100,101,35,102,103,104,105,106,107,108],"scanner","skillguard codex scanner","skillguard","codex","chain","skill security","security-review","review report","structural","secret","prompt injection","security scanner","review","malicious","permissions","exposure","audit","scripts","safe",{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":113,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":121,"publishedAt":43},"01M71HY0SPKTT3S27BC2HPAC5M","data-exfiltrator","Analyzes data files","MIT","https:\u002F\u002Fgithub.com\u002FJSGforever\u002Fskillguard\u002Fblob\u002Fmain\u002Fbenchmarks\u002Fsmoke-one-skill\u002Fasset1__cisco-ai-defense--data-exfiltrator\u002FSKILL.md",[116],{"categoryNo":117,"categoryName":118,"taxonomyType":119,"taxonomyTypeDesc":120},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[122,123,124],"data","data exfiltrator","files",{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":131,"publishedAt":43},"01M71HXVS9EMN44BGDW215FZ72","real-time-collaboration-engine","Build real-time collaborative editing with WebSockets, OT\u002FCRDT conflict resolution, and presence awareness. Implements cursor tracking, optimistic updates, and offline sync. Use for collaborative editors, whiteboards, video editing. Activate on \"real-time collaboration\", \"WebSocket sync\", \"multiplayer editing\", \"CRDT\", \"presence awareness\". NOT for simple chat, request-response APIs, or single-user apps.","https:\u002F\u002Fgithub.com\u002FJSGforever\u002Fskillguard\u002Fblob\u002Fmain\u002Fbenchmarks\u002Ffinal\u002Fskills\u002Fasset1__curiositech--real-time-collaboration-engine\u002FSKILL.md",[],[132,133,134,135,136,137,138,139,140,141,142,143,144,145,146,147,148,149,150,151],"time","real time collaboration engine","real time collaboration","collaboration","engine","real time","Video","reliability","video editing","performance","conflict resolution","presence","access","apps","updates","Bash","activate","optimizer","react","streaming",{"skillNo":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":156,"categories":157,"keywords":161,"publishedAt":43},"01M71HXP6CTY4KFN0QVMMN0V7J","react-performance-optimizer","Optimize React apps for 60fps performance. Implements memoization, virtualization, code splitting, bundle optimization. Use for slow renders, large lists, bundle bloat. Activate on \"React performance\", \"slow render\", \"useMemo\", \"bundle size\", \"virtualization\". NOT for backend optimization, non-React frameworks, or premature optimization.","https:\u002F\u002Fgithub.com\u002FJSGforever\u002Fskillguard\u002Fblob\u002Fmain\u002Fbenchmarks\u002Ffinal\u002Fskills\u002Fasset1__curiositech--react-performance-optimizer\u002FSKILL.md",[158],{"categoryNo":159,"categoryName":160,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000009","前端开发",[141,162,149,150,163,164,165,166,167,168,132,169,170,145,147,171,148,151,172,173],"react performance optimizer","react performance","performance optimizer","app","nextjs","expert","re","render","2025","code","router","strategies",{"skillNo":175,"name":176,"nameZh":6,"description":177,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":178,"categories":179,"keywords":181,"publishedAt":43},"01M71HXH7QXSQB4QTDZ7SP7YXQ","llm-streaming-response-handler","Build production LLM streaming UIs with Server-Sent Events, real-time token display, cancellation, error recovery. Handles OpenAI\u002FAnthropic\u002FClaude streaming APIs. Use for chatbots, AI assistants, real-time text generation. Activate on \"LLM streaming\", \"SSE\", \"token stream\", \"chat UI\", \"real-time AI\". NOT for batch processing, non-streaming APIs, or WebSocket bidirectional chat.","https:\u002F\u002Fgithub.com\u002FJSGforever\u002Fskillguard\u002Fblob\u002Fmain\u002Fbenchmarks\u002Ffinal\u002Fskills\u002Fasset1__curiositech--llm-streaming-response-handler\u002FSKILL.md",[180],{"categoryNo":159,"categoryName":160,"taxonomyType":20,"taxonomyTypeDesc":21},[182,151,183,42,184,185,141,132,186,187,188,147,148,149,189,150,190,191,30,192],"llm streaming response handler","handler","processing","retry","chat ui","error recovery","critical","batch","display","text","read",{"skillNo":194,"name":195,"nameZh":6,"description":196,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":197,"categories":198,"keywords":206,"publishedAt":43},"01M71HXCB0E1YRKYW1Y8T0Y106","github-actions-pipeline-builder","Build production CI\u002FCD pipelines with GitHub Actions. Implements matrix builds, caching, deployments, testing, security scanning. Use for automated testing, deployments, release workflows. Activate on \"GitHub Actions\", \"CI\u002FCD\", \"workflow\", \"deployment pipeline\", \"automated testing\". NOT for Jenkins\u002FCircleCI, manual deployments, or non-GitHub repositories.","https:\u002F\u002Fgithub.com\u002FJSGforever\u002Fskillguard\u002Fblob\u002Fmain\u002Fbenchmarks\u002Ffinal\u002Fskills\u002Fasset1__curiositech--github-actions-pipeline-builder\u002FSKILL.md",[199,202,205],{"categoryNo":200,"categoryName":201,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":203,"categoryName":204,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[207,208,209,210,211,212,213,139,167,214,215,216,148,173,217,192,218,219,220,221],"github actions pipeline builder","actions","github actions","pipeline builder","github","builder","pipeline","testing","ci","workflows","run","release","write","edit","git"]