[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DZ37WVC357V1AR0ZNPFS2D":3,"skill-same:01M6DZ37WVC357V1AR0ZNPFS2D":107},{"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":46,"linkOnly":47,"markdownContent":48,"markdownBody":49,"frontMatter":50,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":55,"repositoryHomepageUrl":56,"ownerHtmlUrl":57,"ownerBlogUrl":58,"ownerDescription":59,"updatedAt":60,"install":61,"resources":74},"01M6DZ37WVC357V1AR0ZNPFS2D","create-custom-agent",null,"Creates VS Code custom agent files (.agent.md) for specialized AI personas with tools, instructions, and handoffs. Use when scaffolding new custom agents, configuring agent workflows, or setting up agent-to-agent handoffs.","managedcode\u002Fdotnet-skills","managedcode","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F78253589?v=4","01M6DYDJR3EG8KB5G4PC65XCTT","Managed Code","01M6DYDJX0ZT432N04NYJW89DN",511,"MIT","https:\u002F\u002Fgithub.com\u002Fmanagedcode\u002Fdotnet-skills\u002Fblob\u002Fmain\u002Fcatalog\u002FTools\u002FOfficial-DotNet-Create-Custom-Agent\u002Fskills\u002Fcreate-custom-agent\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45],"create","custom","create custom agent","new","workflows","when","with tools","ai personas","for","with","agent workflows","scaffolding","agent-to-agent","personas","files","up","use","instructions","specialized","Tools","custom agents","code","2026-11-10 10:12:30",false,"---\nname: create-custom-agent\ndescription: Creates VS Code custom agent files (.agent.md) for specialized AI personas with tools, instructions, and handoffs. Use when scaffolding new custom agents, configuring agent workflows, or setting up agent-to-agent handoffs.\n---\n\n# Create Custom Agent\n\nThis skill helps you create VS Code custom agent files that define specialized AI personas for development tasks. Custom agents configure which tools are available, provide specialized instructions, and can chain together via handoffs.\n\n## When to Use\n\n- Creating a new custom agent from scratch\n- Scaffolding an `.agent.md` file with proper frontmatter\n- Setting up agent-to-agent handoffs for multi-step workflows\n- Configuring tool restrictions for specialized roles (planner, reviewer, etc.)\n- Creating workspace-shared or user-profile agents\n\n## When Not to Use\n\n- Creating instruction files (use `.instructions.md` instead)\n- Creating reusable prompts (use `.prompt.md` instead)\n- Modifying existing agents (edit the file directly)\n\n## Inputs\n\n| Input | Required | Description |\n|-------|----------|-------------|\n| Agent name | Yes | Descriptive name for the agent (e.g., `planner`, `code-reviewer`) |\n| Description | Yes | Brief description shown as placeholder text in chat |\n| Purpose\u002FPersona | Yes | What role the agent plays and how it should behave |\n| Tools | Recommended | List of tools or tool sets the agent can use |\n| Handoffs | Optional | Next-step agents to transition to after completing work |\n\n## Workflow\n\n### Step 1: Create the agent file\n\nCreate a file with `.agent.md` extension in the `agents\u002F` directory:\n\n```\nagents\u002F\u003Cagent-name>.agent.md\n```\n\n### Step 2: Add YAML frontmatter\n\nAdd the header with required and optional fields:\n\n```yaml\n---\nname: \u003Cagent-name>\ndescription: \u003Cbrief description for chat placeholder>\ntools:\n  - \u003Ctool-name>\n  - \u003Ctool-set-name>\n---\n```\n\n#### Available frontmatter fields:\n\n| Field | Required | Description |\n|-------|----------|-------------|\n| `name` | No | Display name (defaults to filename) |\n| `description` | Yes | Placeholder text shown in chat input |\n| `argument-hint` | No | Hint text guiding user interaction |\n| `tools` | No | List of available tools\u002Ftool sets |\n| `agents` | No | List of allowed subagents (`*` for all, `[]` for none) |\n| `model` | No | AI model name or prioritized array of models |\n| `handoffs` | No | List of next-step agent transitions |\n| `user-invokable` | No | Show in agents dropdown (default: true) |\n| `disable-model-invocation` | No | Prevent subagent invocation (default: false) |\n| `target` | No | Target environment: `vscode` or `github-copilot` |\n| `mcp-servers` | No | MCP server configs for GitHub Copilot target |\n\n### Step 3: Configure tools\n\nSpecify which tools the agent can use:\n\n```yaml\ntools:\n  - search              # Built-in tool\n  - fetch               # Built-in tool\n  - codebase            # Tool set\n  - myServer\u002F*          # All tools from MCP server\n```\n\nCommon tool patterns:\n- **Read-only agents**: `['search', 'fetch', 'codebase']`\n- **Full editing agents**: `['*']` or specific editing tools\n- **Specialized agents**: Cherry-pick specific tools\n\n### Step 4: Add handoffs (optional)\n\nConfigure transitions to other agents:\n\n```yaml\nhandoffs:\n  - label: Start Implementation\n    agent: implementation\n    prompt: Implement the plan outlined above.\n    send: false\n    model: GPT-5.2 (copilot)\n```\n\nHandoff fields:\n- `label`: Button text displayed to user\n- `agent`: Target agent identifier\n- `prompt`: Pre-filled prompt for target agent\n- `send`: Auto-submit prompt (default: false)\n- `model`: Optional model override for handoff\n\n### Step 5: Write agent instructions (body)\n\nAdd the agent's behavior instructions in Markdown:\n\n```markdown\nYou are a security-focused code reviewer. Your job is to:\n\n1. Analyze code for security vulnerabilities\n2. Check for common security anti-patterns\n3. Suggest secure alternatives\n\n## Guidelines\n\n- Focus on OWASP Top 10 vulnerabilities\n- Flag hardcoded secrets immediately\n- Review authentication and authorization logic\n\n## Reference other files\n\nSee [security guidelines](..\u002Fsecurity.md) for standards.\n```\n\nTips for instructions:\n- Use Markdown links to reference other files\n- Reference tools with `#tool:\u003Ctool-name>` syntax\n- Be specific about agent behavior and constraints\n\n### Step 6: Validate the agent\n\nVerify the agent loads correctly:\n\n1. Open Command Palette (Ctrl+Shift+P)\n2. Run \"Chat: New Custom Agent\" or check agents dropdown\n3. Use \"Diagnostics\" view (right-click in Chat view) to check for errors\n\n## Template\n\n```markdown\n---\nname: \u003Cagent-name>\ndescription: \u003Cbrief description for chat placeholder>\nargument-hint: \u003Coptional hint for user input>\ntools:\n  - \u003Ctool-1>\n  - \u003Ctool-2>\nhandoffs:\n  - label: \u003Cbutton-text>\n    agent: \u003Ctarget-agent>\n    prompt: \u003Cpre-filled-prompt>\n    send: false\n---\n\n# \u003CAgent Title>\n\n\u003COne paragraph describing the agent's persona and purpose.>\n\n## Role\n\n\u003CDescribe the agent's specialized role and expertise.>\n\n## Guidelines\n\n- \u003CGuideline 1>\n- \u003CGuideline 2>\n- \u003CGuideline 3>\n\n## Workflow\n\n1. \u003CStep 1>\n2. \u003CStep 2>\n3. \u003CStep 3>\n\n## Constraints\n\n- \u003CConstraint 1>\n- \u003CConstraint 2>\n```\n\n## Example Agents\n\n### Planning Agent\n\n```markdown\n---\nname: planner\ndescription: Generate an implementation plan\ntools:\n  - search\n  - fetch\n  - codebase\nhandoffs:\n  - label: Start Implementation\n    agent: implementation\n    prompt: Implement the plan above.\n---\n\n# Planning Agent\n\nYou are a solution architect. Generate detailed implementation plans.\n\n## Guidelines\n\n- Analyze requirements thoroughly before planning\n- Break work into discrete, testable steps\n- Identify dependencies and risks\n- Do NOT make code changes\n```\n\n### Code Review Agent\n\n```markdown\n---\nname: code-reviewer\ndescription: Review code for quality and security issues\ntools:\n  - search\n  - codebase\n---\n\n# Code Review Agent\n\nYou are a senior engineer performing code review.\n\n## Focus Areas\n\n- Security vulnerabilities\n- Performance concerns\n- Code maintainability\n- Test coverage gaps\n\n## Output Format\n\nProvide findings as:\n1. **Critical**: Must fix before merge\n2. **Warning**: Should address\n3. **Suggestion**: Nice to have\n```\n\n## Validation Checklist\n\n- [ ] File has `.agent.md` extension\n- [ ] File is in `agents\u002F` directory\n- [ ] YAML frontmatter is valid (proper indentation, no syntax errors)\n- [ ] Description is non-empty and descriptive\n- [ ] Tools list contains only available tools\n- [ ] Handoff agent names match existing agents\n- [ ] Instructions are clear and actionable\n- [ ] Agent appears in agents dropdown\n\n## Common Pitfalls\n\n| Pitfall | Solution |\n|---------|----------|\n| Agent not appearing in dropdown | Check file is in `agents\u002F` directory with `.agent.md` extension |\n| YAML syntax errors | Validate frontmatter indentation and quoting |\n| Tools not working | Verify tool names exist; unavailable tools are ignored |\n| Handoffs not showing | Target agent must exist; check agent identifier |\n| Instructions too vague | Be specific about role, constraints, and workflow |\n| Agent invoked as subagent unexpectedly | Set `disable-model-invocation: true` |\n| Want agent only as subagent | Set `user-invokable: false` |\n\n## References\n\n- [VS Code Custom Agents Documentation](https:\u002F\u002Fcode.visualstudio.com\u002Fdocs\u002Fcopilot\u002Fcustomization\u002Fcustom-agents)\n- [Tools in Chat](https:\u002F\u002Fcode.visualstudio.com\u002Fdocs\u002Fcopilot\u002Fchat\u002Fchat-tools)\n- [Custom Instructions](https:\u002F\u002Fcode.visualstudio.com\u002Fdocs\u002Fcopilot\u002Fcustomization\u002Fcustom-instructions)\n- [Prompt Files](https:\u002F\u002Fcode.visualstudio.com\u002Fdocs\u002Fcopilot\u002Fcustomization\u002Fprompt-files)\n","# Create Custom Agent\n\nThis skill helps you create VS Code custom agent files that define specialized AI personas for development tasks. Custom agents configure which tools are available, provide specialized instructions, and can chain together via handoffs.\n\n## When to Use\n\n- Creating a new custom agent from scratch\n- Scaffolding an `.agent.md` file with proper frontmatter\n- Setting up agent-to-agent handoffs for multi-step workflows\n- Configuring tool restrictions for specialized roles (planner, reviewer, etc.)\n- Creating workspace-shared or user-profile agents\n\n## When Not to Use\n\n- Creating instruction files (use `.instructions.md` instead)\n- Creating reusable prompts (use `.prompt.md` instead)\n- Modifying existing agents (edit the file directly)\n\n## Inputs\n\n| Input | Required | Description |\n|-------|----------|-------------|\n| Agent name | Yes | Descriptive name for the agent (e.g., `planner`, `code-reviewer`) |\n| Description | Yes | Brief description shown as placeholder text in chat |\n| Purpose\u002FPersona | Yes | What role the agent plays and how it should behave |\n| Tools | Recommended | List of tools or tool sets the agent can use |\n| Handoffs | Optional | Next-step agents to transition to after completing work |\n\n## Workflow\n\n### Step 1: Create the agent file\n\nCreate a file with `.agent.md` extension in the `agents\u002F` directory:\n\n```\nagents\u002F\u003Cagent-name>.agent.md\n```\n\n### Step 2: Add YAML frontmatter\n\nAdd the header with required and optional fields:\n\n```yaml\n---\nname: \u003Cagent-name>\ndescription: \u003Cbrief description for chat placeholder>\ntools:\n  - \u003Ctool-name>\n  - \u003Ctool-set-name>\n---\n```\n\n#### Available frontmatter fields:\n\n| Field | Required | Description |\n|-------|----------|-------------|\n| `name` | No | Display name (defaults to filename) |\n| `description` | Yes | Placeholder text shown in chat input |\n| `argument-hint` | No | Hint text guiding user interaction |\n| `tools` | No | List of available tools\u002Ftool sets |\n| `agents` | No | List of allowed subagents (`*` for all, `[]` for none) |\n| `model` | No | AI model name or prioritized array of models |\n| `handoffs` | No | List of next-step agent transitions |\n| `user-invokable` | No | Show in agents dropdown (default: true) |\n| `disable-model-invocation` | No | Prevent subagent invocation (default: false) |\n| `target` | No | Target environment: `vscode` or `github-copilot` |\n| `mcp-servers` | No | MCP server configs for GitHub Copilot target |\n\n### Step 3: Configure tools\n\nSpecify which tools the agent can use:\n\n```yaml\ntools:\n  - search              # Built-in tool\n  - fetch               # Built-in tool\n  - codebase            # Tool set\n  - myServer\u002F*          # All tools from MCP server\n```\n\nCommon tool patterns:\n- **Read-only agents**: `['search', 'fetch', 'codebase']`\n- **Full editing agents**: `['*']` or specific editing tools\n- **Specialized agents**: Cherry-pick specific tools\n\n### Step 4: Add handoffs (optional)\n\nConfigure transitions to other agents:\n\n```yaml\nhandoffs:\n  - label: Start Implementation\n    agent: implementation\n    prompt: Implement the plan outlined above.\n    send: false\n    model: GPT-5.2 (copilot)\n```\n\nHandoff fields:\n- `label`: Button text displayed to user\n- `agent`: Target agent identifier\n- `prompt`: Pre-filled prompt for target agent\n- `send`: Auto-submit prompt (default: false)\n- `model`: Optional model override for handoff\n\n### Step 5: Write agent instructions (body)\n\nAdd the agent's behavior instructions in Markdown:\n\n```markdown\nYou are a security-focused code reviewer. Your job is to:\n\n1. Analyze code for security vulnerabilities\n2. Check for common security anti-patterns\n3. Suggest secure alternatives\n\n## Guidelines\n\n- Focus on OWASP Top 10 vulnerabilities\n- Flag hardcoded secrets immediately\n- Review authentication and authorization logic\n\n## Reference other files\n\nSee [security guidelines](..\u002Fsecurity.md) for standards.\n```\n\nTips for instructions:\n- Use Markdown links to reference other files\n- Reference tools with `#tool:\u003Ctool-name>` syntax\n- Be specific about agent behavior and constraints\n\n### Step 6: Validate the agent\n\nVerify the agent loads correctly:\n\n1. Open Command Palette (Ctrl+Shift+P)\n2. Run \"Chat: New Custom Agent\" or check agents dropdown\n3. Use \"Diagnostics\" view (right-click in Chat view) to check for errors\n\n## Template\n\n```markdown\n---\nname: \u003Cagent-name>\ndescription: \u003Cbrief description for chat placeholder>\nargument-hint: \u003Coptional hint for user input>\ntools:\n  - \u003Ctool-1>\n  - \u003Ctool-2>\nhandoffs:\n  - label: \u003Cbutton-text>\n    agent: \u003Ctarget-agent>\n    prompt: \u003Cpre-filled-prompt>\n    send: false\n---\n\n# \u003CAgent Title>\n\n\u003COne paragraph describing the agent's persona and purpose.>\n\n## Role\n\n\u003CDescribe the agent's specialized role and expertise.>\n\n## Guidelines\n\n- \u003CGuideline 1>\n- \u003CGuideline 2>\n- \u003CGuideline 3>\n\n## Workflow\n\n1. \u003CStep 1>\n2. \u003CStep 2>\n3. \u003CStep 3>\n\n## Constraints\n\n- \u003CConstraint 1>\n- \u003CConstraint 2>\n```\n\n## Example Agents\n\n### Planning Agent\n\n```markdown\n---\nname: planner\ndescription: Generate an implementation plan\ntools:\n  - search\n  - fetch\n  - codebase\nhandoffs:\n  - label: Start Implementation\n    agent: implementation\n    prompt: Implement the plan above.\n---\n\n# Planning Agent\n\nYou are a solution architect. Generate detailed implementation plans.\n\n## Guidelines\n\n- Analyze requirements thoroughly before planning\n- Break work into discrete, testable steps\n- Identify dependencies and risks\n- Do NOT make code changes\n```\n\n### Code Review Agent\n\n```markdown\n---\nname: code-reviewer\ndescription: Review code for quality and security issues\ntools:\n  - search\n  - codebase\n---\n\n# Code Review Agent\n\nYou are a senior engineer performing code review.\n\n## Focus Areas\n\n- Security vulnerabilities\n- Performance concerns\n- Code maintainability\n- Test coverage gaps\n\n## Output Format\n\nProvide findings as:\n1. **Critical**: Must fix before merge\n2. **Warning**: Should address\n3. **Suggestion**: Nice to have\n```\n\n## Validation Checklist\n\n- [ ] File has `.agent.md` extension\n- [ ] File is in `agents\u002F` directory\n- [ ] YAML frontmatter is valid (proper indentation, no syntax errors)\n- [ ] Description is non-empty and descriptive\n- [ ] Tools list contains only available tools\n- [ ] Handoff agent names match existing agents\n- [ ] Instructions are clear and actionable\n- [ ] Agent appears in agents dropdown\n\n## Common Pitfalls\n\n| Pitfall | Solution |\n|---------|----------|\n| Agent not appearing in dropdown | Check file is in `agents\u002F` directory with `.agent.md` extension |\n| YAML syntax errors | Validate frontmatter indentation and quoting |\n| Tools not working | Verify tool names exist; unavailable tools are ignored |\n| Handoffs not showing | Target agent must exist; check agent identifier |\n| Instructions too vague | Be specific about role, constraints, and workflow |\n| Agent invoked as subagent unexpectedly | Set `disable-model-invocation: true` |\n| Want agent only as subagent | Set `user-invokable: false` |\n\n## References\n\n- [VS Code Custom Agents Documentation](https:\u002F\u002Fcode.visualstudio.com\u002Fdocs\u002Fcopilot\u002Fcustomization\u002Fcustom-agents)\n- [Tools in Chat](https:\u002F\u002Fcode.visualstudio.com\u002Fdocs\u002Fcopilot\u002Fchat\u002Fchat-tools)\n- [Custom Instructions](https:\u002F\u002Fcode.visualstudio.com\u002Fdocs\u002Fcopilot\u002Fcustomization\u002Fcustom-instructions)\n- [Prompt Files](https:\u002F\u002Fcode.visualstudio.com\u002Fdocs\u002Fcopilot\u002Fcustomization\u002Fprompt-files)\n",{"name":5,"description":7},"main","497cc9aba79a931ac6fb8d36a48cc22fe3d6d74b","catalog\u002FTools\u002FOfficial-DotNet-Create-Custom-Agent\u002Fskills\u002Fcreate-custom-agent",41,"https:\u002F\u002Fgithub.com\u002Fmanagedcode\u002Fdotnet-skills","https:\u002F\u002Fskills.managed-code.com","https:\u002F\u002Fgithub.com\u002Fmanagedcode","https:\u002F\u002Fwww.managed-code.com","Open Source Community for .NET Developers: Reliable, Actively Maintained, and Community-Driven. Made in Ukraine 🇺🇦 with ❤️","2026-11-10 19:58:06",{"source":8,"skillName":5,"commands":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add managedcode\u002Fdotnet-skills --skill create-custom-agent",{"tool":67,"command":68},"bunx","bunx skills add managedcode\u002Fdotnet-skills --skill create-custom-agent",{"tool":70,"command":71},"pnpm","pnpm dlx skills add managedcode\u002Fdotnet-skills --skill create-custom-agent","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmanagedcode\u002Fdotnet-skills\u002Fblob\u002Fmain\u002Fcatalog\u002FTools\u002FOfficial-DotNet-Create-Custom-Agent\u002Fskills\u002Fcreate-custom-agent\u002FSKILL.md",true,[75,81,85,89,93,97,101],{"path":76,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":79,"sourceHtmlUrl":80},"manifest.json","REFERENCE","参考文档",124,"https:\u002F\u002Fgithub.com\u002Fmanagedcode\u002Fdotnet-skills\u002Fblob\u002Fmain\u002Fcatalog\u002FTools\u002FOfficial-DotNet-Create-Custom-Agent\u002Fskills\u002Fcreate-custom-agent\u002Fmanifest.json",{"path":82,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Fchemical-analysis.md",19413,"https:\u002F\u002Fgithub.com\u002FJSGforever\u002Fskillguard\u002Fblob\u002Fmain\u002Fbenchmarks\u002Ffinal\u002Fskills\u002Fasset1__Microck--claude-scientific-skills\u002Fscientific-skills\u002Fdrugbank-database\u002Freferences\u002Fchemical-analysis.md",{"path":86,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":87,"sourceHtmlUrl":88},"references\u002Fdata-access.md",6062,"https:\u002F\u002Fgithub.com\u002FJSGforever\u002Fskillguard\u002Fblob\u002Fmain\u002Fbenchmarks\u002Ffinal\u002Fskills\u002Fasset1__Microck--claude-scientific-skills\u002Fscientific-skills\u002Fdrugbank-database\u002Freferences\u002Fdata-access.md",{"path":90,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":91,"sourceHtmlUrl":92},"references\u002Fdrug-queries.md",11772,"https:\u002F\u002Fgithub.com\u002FJSGforever\u002Fskillguard\u002Fblob\u002Fmain\u002Fbenchmarks\u002Ffinal\u002Fskills\u002Fasset1__Microck--claude-scientific-skills\u002Fscientific-skills\u002Fdrugbank-database\u002Freferences\u002Fdrug-queries.md",{"path":94,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":95,"sourceHtmlUrl":96},"references\u002Finteractions.md",13794,"https:\u002F\u002Fgithub.com\u002FJSGforever\u002Fskillguard\u002Fblob\u002Fmain\u002Fbenchmarks\u002Ffinal\u002Fskills\u002Fasset1__Microck--claude-scientific-skills\u002Fscientific-skills\u002Fdrugbank-database\u002Freferences\u002Finteractions.md",{"path":98,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":99,"sourceHtmlUrl":100},"references\u002Ftargets-pathways.md",18253,"https:\u002F\u002Fgithub.com\u002FJSGforever\u002Fskillguard\u002Fblob\u002Fmain\u002Fbenchmarks\u002Ffinal\u002Fskills\u002Fasset1__Microck--claude-scientific-skills\u002Fscientific-skills\u002Fdrugbank-database\u002Freferences\u002Ftargets-pathways.md",{"path":102,"resourceType":103,"resourceTypeDesc":104,"sizeBytes":105,"sourceHtmlUrl":106},"scripts\u002Fdrugbank_helper.py","SCRIPT","脚本",11822,"https:\u002F\u002Fgithub.com\u002FJSGforever\u002Fskillguard\u002Fblob\u002Fmain\u002Fbenchmarks\u002Ffinal\u002Fskills\u002Fasset1__Microck--claude-scientific-skills\u002Fscientific-skills\u002Fdrugbank-database\u002Fscripts\u002Fdrugbank_helper.py",[108,140,165,193,203,229],{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":122,"publishedAt":46},"01M6DYQE1Y9FHAQHEDTVFQ3447","xtwitter-scraper","Use XTwitterScraper when a .NET application needs typed access to Xquik's X automation REST API for tweet search, user lookup, posting workflows, extraction jobs, monitors, webhooks, or giveaway draws. USE FOR: integrating the XTwitterScraper NuGet package; reviewing Xquik API client usage; modeling API-key configuration, pagination, binary exports, raw responses, retries, and webhook\u002Fevent flows in .NET. DO NOT USE FOR: unrelated stacks; direct browser automation; generic social-media strategy; or code that does not call Xquik. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.","https:\u002F\u002Fgithub.com\u002Fmanagedcode\u002Fdotnet-skills\u002Fblob\u002Fmain\u002Fcatalog\u002FLibraries\u002FXTwitterScraper\u002Fskills\u002Fxtwitter-scraper\u002FSKILL.md",[114,117],{"categoryNo":115,"categoryName":116,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":118,"categoryName":119,"taxonomyType":120,"taxonomyTypeDesc":121},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[123,124,28,125,45,126,127,128,129,130,131,132,133,134,135,38,136,137,138,139],"xtwitter scraper","browser automation","run","browser","search","repository","api","Media","api client","access","edit","unrelated","webhooks","social","commands","modeling","webhook",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":152,"publishedAt":46},"01M6DYQ9S4PE1H6G8MCH9T21HR","sep","Use Sep for high-performance separated-value parsing and writing in .NET, including delimiter inference, explicit parser\u002Fwriter options, and low-allocation row\u002Fcolumn workflows. USE FOR: delimited data needs are performance-sensitive and allocation-aware; project needs explicit control over separator inference, escaping, trimming, and header behavior;. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.","https:\u002F\u002Fgithub.com\u002Fmanagedcode\u002Fdotnet-skills\u002Fblob\u002Fmain\u002Fcatalog\u002FLibraries\u002FSep\u002Fskills\u002Fsep\u002FSKILL.md",[146,149],{"categoryNo":147,"categoryName":148,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":150,"categoryName":151,"taxonomyType":120,"taxonomyTypeDesc":121},"01JBSEEDCAT000000000000036","内容创作者",[142,153,154,28,155,125,128,156,157,158,133,159,134,38,160,161,162,163,137,164],"writing","performance","tasks","data","parsing","parser","context","do","writer","options","project","high-performance",{"skillNo":166,"name":167,"nameZh":6,"description":168,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":169,"categories":170,"keywords":171,"publishedAt":46},"01M6DZS2DNEPXCGGF6SSCW6G5V","webgpu-threejs-tsl","Comprehensive guide for developing WebGPU-enabled Three.js applications using TSL (Three.js Shading Language). Covers WebGPU renderer setup, TSL syntax and node materials, compute shaders, post-processing effects, and WGSL integration. Use this skill when working with Three.js WebGPU, TSL shaders, node materials, or GPU compute in Three.js.","https:\u002F\u002Fgithub.com\u002Fmanagedcode\u002Fdotnet-skills\u002Fblob\u002Fmain\u002Fexternal-sources\u002Fupstreams\u002Fwebgpu-claude-skill\u002Fskills\u002Fwebgpu-threejs-tsl\u002FSKILL.md",[],[172,173,174,175,176,177,178,179,180,181,182,183,40,184,185,186,187,188,33,189,32,190,191,192,29],"webgpu","threejs","webgpu threejs tsl","setup","shaders","gpu","integration","applications","js","node","syntax","guide","language","three","compute","post","processing","renderer","materials","wgsl","effects",{"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":46},"01M6DZS0BQXW2B56A289XF1X76","roslynk","Use Roslynk for semantic inspection and edits of *.cs, *.razor and *.cshtml solution files.","https:\u002F\u002Fgithub.com\u002Fmanagedcode\u002Fdotnet-skills\u002Fblob\u002Fmain\u002Fexternal-sources\u002Fupstreams\u002Froslynk\u002Fskills\u002Froslynk\u002FSKILL.md",[],[195,40,38,200,201,32,202],"semantic","razor","inspection",{"skillNo":204,"name":205,"nameZh":6,"description":206,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":207,"categories":208,"keywords":209,"publishedAt":46},"01M6DZRW6MEJCVW80K3S4XV60K","system-text-json-net11","Imperative guidance for the System.Text.Json APIs added in .NET 11: the built-in `JsonNamingPolicy.PascalCase` naming policy, and the strongly-typed generic `JsonSerializerOptions.GetTypeInfo` and `JsonSerializerOptions.TryGetTypeInfo` metadata accessors (generic overloads that return a typed `JsonTypeInfo`). USE ONLY when the user is targeting net11.0 or later and needs PascalCase JSON property or dictionary-key names without writing a custom naming policy, a strongly-typed generic `JsonTypeInfo` instead of the non-generic `JsonTypeInfo`, or a no-throw way to probe whether a type's serialization metadata is resolved. DO NOT USE when the target is earlier than net11.0, the requested behavior uses an established pre-net11 naming policy, or the user explicitly selected another JSON library.","https:\u002F\u002Fgithub.com\u002Fmanagedcode\u002Fdotnet-skills\u002Fblob\u002Fmain\u002Fexternal-sources\u002Fupstreams\u002Fdotnet-skills\u002Fplugins\u002Fdotnet11\u002Fskills\u002Fsystem-text-json-net11\u002FSKILL.md",[],[210,211,212,213,153,214,215,216,217,218,219,40,220,221,222,223,160,224,225,226,227,32,25,228,29],"system","json","text","system text json net11","policy","metadata","library","serialization","behavior","user","only","probe","guidance","later","type","dictionary","naming","targeting","generic",{"skillNo":230,"name":231,"nameZh":6,"description":232,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":233,"categories":234,"keywords":237,"publishedAt":46},"01M6DZRRJP3S662NFSG1RSPQQ7","process-api-net11","Provides guidance on the new System.Diagnostics.Process APIs introduced in .NET 11: Process.Run, Process.RunAndCaptureText, Process.StartAndForget, Process.ReadAllText\u002FBytes\u002FLines, KillOnParentExit, InheritedHandles, and StartDetached. USE FOR: starting, orchestrating, or capturing output from external processes in applications targeting net11.0 or later. DO NOT USE FOR: applications targeting .NET 10 or earlier, or basic pre-.NET 11 Process.Start usage without new APIs.","https:\u002F\u002Fgithub.com\u002Fmanagedcode\u002Fdotnet-skills\u002Fblob\u002Fmain\u002Fexternal-sources\u002Fupstreams\u002Fdotnet-skills\u002Fplugins\u002Fdotnet11\u002Fskills\u002Fprocess-api-net11\u002FSKILL.md",[235,236],{"categoryNo":115,"categoryName":116,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":118,"categoryName":119,"taxonomyType":120,"taxonomyTypeDesc":121},[129,238,239,240,125,241,179,210,40,222,223,160,242,243,244,245,227,32,27],"process","process api net11","diagnostics","start","basic","processes","output","usage"]