[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M756CKGEMRT9JHMXF39AS0XM":3,"skill-same:01M756CKGEMRT9JHMXF39AS0XM":45},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M756CKGEMRT9JHMXF39AS0XM","create-skill",null,"Scaffolds new agent skills for the dotnet\u002Fskills repository. Use when creating a new skill, generating SKILL.md files, or setting up skill directory structures. Handles frontmatter generation, section templates, and validation guidance.","weiflycc-cmd\u002Fskills","weiflycc-cmd","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F250846518?v=4","01M756C4PFGZJWKK04WFB9S5XF","威飛工作室","01M756C4QJJ66QDXN2RN6SXY87",0,"MIT","https:\u002F\u002Fgithub.com\u002Fweiflycc-cmd\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcreate-skill\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: create-skill\ndescription: Scaffolds new agent skills for the dotnet\u002Fskills repository. Use when creating a new skill, generating SKILL.md files, or setting up skill directory structures. Handles frontmatter generation, section templates, and validation guidance.\n---\n\n# Create Skill\n\nThis skill helps you scaffold new agent skills that conform to the Agent Skills specification and the dotnet\u002Fskills repository conventions.\n\n## When to Use\n\n- Creating a new skill from scratch\n- Generating a SKILL.md file with proper frontmatter\n- Setting up the skill directory structure with optional folders\n- Ensuring compliance with agentskills.io specification\n\n## When Not to Use\n\n- Modifying existing skills (edit directly instead)\n- Creating custom agents (use the agents\u002F directory pattern)\n\n## Inputs\n\n| Input | Required | Description |\n|-------|----------|-------------|\n| Skill name | Yes | Lowercase, alphanumeric, hyphens only (e.g., `code-review`, `ci-triage`) |\n| Description | Yes | What the skill does and when agents should use it (1-1024 chars) |\n| Purpose | Yes | One paragraph describing the outcome |\n| Workflow steps | Recommended | Numbered steps the agent should follow |\n\n## Workflow\n\n### Step 1: Validate the skill name\n\nEnsure the name:\n- Contains only lowercase letters, numbers, and hyphens\n- Does not start or end with a hyphen\n- Does not contain consecutive hyphens\n- Is between 1-64 characters\n\n### Step 2: Create the skill directory\n\n```\nskills\u002F\u003Cskill-name>\u002F\n└── SKILL.md\n```\n\n### Step 3: Generate SKILL.md with frontmatter\n\nCreate the file with required YAML frontmatter:\n\n```yaml\n---\nname: \u003Cskill-name>\ndescription: \u003Cdescription of what the skill does and when to use it>\n---\n```\n\n### Step 4: Add body content sections\n\nInclude these recommended sections:\n\n1. **Purpose**: One paragraph describing the outcome\n2. **When to Use**: Bullet list of appropriate scenarios\n3. **When Not to Use**: Boundaries and exclusions\n4. **Inputs**: Table of required and optional inputs\n5. **Workflow**: Numbered steps with checkpoints\n6. **Validation**: How to confirm the skill worked correctly\n7. **Common Pitfalls**: Known traps and how to avoid them\n\n### Step 5: Add optional directories (if needed)\n\n```\nskills\u002F\u003Cskill-name>\u002F\n├── SKILL.md\n├── scripts\u002F       # Executable code agents can run\n├── references\u002F    # Additional documentation loaded on demand\n└── assets\u002F        # Templates, images, data files\n```\n\n### Step 6: Update CODEOWNERS\n\nAdd entries in `.github\u002FCODEOWNERS` for the new skill and its test directory:\n\n```\n\u002Fplugins\u002F\u003Cplugin>\u002Fskills\u002F\u003Cskill-name>\u002F  @owner-team\n\u002Ftests\u002F\u003Cplugin>\u002F\u003Cskill-name>\u002F           @owner-team\n```\n\nMatch the owner pattern used by sibling skills in the same plugin.\n\n### Step 7: Validate the skill\n\n- Confirm frontmatter fields are valid\n- Ensure SKILL.md is under 500 lines\n- Check that file references use relative paths\n- Verify instructions are actionable and specific\n\n## SKILL.md Template\n\nUse this template when creating a new skill:\n\n```markdown\n---\nname: \u003Cskill-name>\ndescription: \u003C1-1024 char description of what the skill does and when to use it>\n---\n\n# \u003CSkill Title>\n\n\u003COne paragraph describing the skill's purpose and outcome.>\n\n## When to Use\n\n- \u003CScenario 1>\n- \u003CScenario 2>\n\n## When Not to Use\n\n- \u003CExclusion 1>\n- \u003CExclusion 2>\n\n## Inputs\n\n| Input | Required | Description |\n|-------|----------|-------------|\n| \u003Cinput-name> | Yes\u002FNo | \u003Cdescription> |\n\n## Workflow\n\n### Step 1: \u003CAction>\n\n\u003CInstructions for this step>\n\n### Step 2: \u003CAction>\n\n\u003CInstructions for this step>\n\n## Validation\n\n- [ ] \u003CVerification step 1>\n- [ ] \u003CVerification step 2>\n\n## Common Pitfalls\n\n| Pitfall | Solution |\n|---------|----------|\n| \u003CProblem> | \u003CHow to avoid or fix> |\n```\n\n## Validation Checklist\n\nAfter creating a skill, verify:\n\n- [ ] Skill name matches directory name exactly\n- [ ] Skill name is lowercase with hyphens only\n- [ ] Description is non-empty and under 1024 characters\n- [ ] SKILL.md body is under 500 lines\n- [ ] Instructions are specific and actionable\n- [ ] Workflow has numbered steps with clear checkpoints\n- [ ] Validation section exists with observable success criteria\n- [ ] No secrets, tokens, or internal URLs included\n- [ ] `.github\u002FCODEOWNERS` has entries for the new skill and its test directory\n\n## Common Pitfalls\n\n| Pitfall | Solution |\n|---------|----------|\n| Name contains uppercase letters | Use only lowercase: `code-review` not `Code-Review` |\n| Description is vague | Include what it does AND when to use it |\n| Instructions are ambiguous | Use numbered steps with concrete actions |\n| Missing validation steps | Add checkpoints that verify success |\n| SKILL.md too long | Move detailed content to `references\u002F` files |\n| Hardcoded environment assumptions | Document requirements in `compatibility` field |\n| Missing CODEOWNERS entry | Add entries for both `\u002Fplugins\u002F\u003Cplugin>\u002Fskills\u002F\u003Cskill-name>\u002F` and `\u002Ftests\u002F\u003Cplugin>\u002F\u003Cskill-name>\u002F` matching sibling skills' owner pattern |\n\n## References\n\n- [Agent Skills Specification](https:\u002F\u002Fagentskills.io\u002Fspecification)\n- [Repository README](..\u002F..\u002FREADME.md)\n- [Contributing Guidelines](..\u002F..\u002FCONTRIBUTING.md)\n","# Create Skill\n\nThis skill helps you scaffold new agent skills that conform to the Agent Skills specification and the dotnet\u002Fskills repository conventions.\n\n## When to Use\n\n- Creating a new skill from scratch\n- Generating a SKILL.md file with proper frontmatter\n- Setting up the skill directory structure with optional folders\n- Ensuring compliance with agentskills.io specification\n\n## When Not to Use\n\n- Modifying existing skills (edit directly instead)\n- Creating custom agents (use the agents\u002F directory pattern)\n\n## Inputs\n\n| Input | Required | Description |\n|-------|----------|-------------|\n| Skill name | Yes | Lowercase, alphanumeric, hyphens only (e.g., `code-review`, `ci-triage`) |\n| Description | Yes | What the skill does and when agents should use it (1-1024 chars) |\n| Purpose | Yes | One paragraph describing the outcome |\n| Workflow steps | Recommended | Numbered steps the agent should follow |\n\n## Workflow\n\n### Step 1: Validate the skill name\n\nEnsure the name:\n- Contains only lowercase letters, numbers, and hyphens\n- Does not start or end with a hyphen\n- Does not contain consecutive hyphens\n- Is between 1-64 characters\n\n### Step 2: Create the skill directory\n\n```\nskills\u002F\u003Cskill-name>\u002F\n└── SKILL.md\n```\n\n### Step 3: Generate SKILL.md with frontmatter\n\nCreate the file with required YAML frontmatter:\n\n```yaml\n---\nname: \u003Cskill-name>\ndescription: \u003Cdescription of what the skill does and when to use it>\n---\n```\n\n### Step 4: Add body content sections\n\nInclude these recommended sections:\n\n1. **Purpose**: One paragraph describing the outcome\n2. **When to Use**: Bullet list of appropriate scenarios\n3. **When Not to Use**: Boundaries and exclusions\n4. **Inputs**: Table of required and optional inputs\n5. **Workflow**: Numbered steps with checkpoints\n6. **Validation**: How to confirm the skill worked correctly\n7. **Common Pitfalls**: Known traps and how to avoid them\n\n### Step 5: Add optional directories (if needed)\n\n```\nskills\u002F\u003Cskill-name>\u002F\n├── SKILL.md\n├── scripts\u002F       # Executable code agents can run\n├── references\u002F    # Additional documentation loaded on demand\n└── assets\u002F        # Templates, images, data files\n```\n\n### Step 6: Update CODEOWNERS\n\nAdd entries in `.github\u002FCODEOWNERS` for the new skill and its test directory:\n\n```\n\u002Fplugins\u002F\u003Cplugin>\u002Fskills\u002F\u003Cskill-name>\u002F  @owner-team\n\u002Ftests\u002F\u003Cplugin>\u002F\u003Cskill-name>\u002F           @owner-team\n```\n\nMatch the owner pattern used by sibling skills in the same plugin.\n\n### Step 7: Validate the skill\n\n- Confirm frontmatter fields are valid\n- Ensure SKILL.md is under 500 lines\n- Check that file references use relative paths\n- Verify instructions are actionable and specific\n\n## SKILL.md Template\n\nUse this template when creating a new skill:\n\n```markdown\n---\nname: \u003Cskill-name>\ndescription: \u003C1-1024 char description of what the skill does and when to use it>\n---\n\n# \u003CSkill Title>\n\n\u003COne paragraph describing the skill's purpose and outcome.>\n\n## When to Use\n\n- \u003CScenario 1>\n- \u003CScenario 2>\n\n## When Not to Use\n\n- \u003CExclusion 1>\n- \u003CExclusion 2>\n\n## Inputs\n\n| Input | Required | Description |\n|-------|----------|-------------|\n| \u003Cinput-name> | Yes\u002FNo | \u003Cdescription> |\n\n## Workflow\n\n### Step 1: \u003CAction>\n\n\u003CInstructions for this step>\n\n### Step 2: \u003CAction>\n\n\u003CInstructions for this step>\n\n## Validation\n\n- [ ] \u003CVerification step 1>\n- [ ] \u003CVerification step 2>\n\n## Common Pitfalls\n\n| Pitfall | Solution |\n|---------|----------|\n| \u003CProblem> | \u003CHow to avoid or fix> |\n```\n\n## Validation Checklist\n\nAfter creating a skill, verify:\n\n- [ ] Skill name matches directory name exactly\n- [ ] Skill name is lowercase with hyphens only\n- [ ] Description is non-empty and under 1024 characters\n- [ ] SKILL.md body is under 500 lines\n- [ ] Instructions are specific and actionable\n- [ ] Workflow has numbered steps with clear checkpoints\n- [ ] Validation section exists with observable success criteria\n- [ ] No secrets, tokens, or internal URLs included\n- [ ] `.github\u002FCODEOWNERS` has entries for the new skill and its test directory\n\n## Common Pitfalls\n\n| Pitfall | Solution |\n|---------|----------|\n| Name contains uppercase letters | Use only lowercase: `code-review` not `Code-Review` |\n| Description is vague | Include what it does AND when to use it |\n| Instructions are ambiguous | Use numbered steps with concrete actions |\n| Missing validation steps | Add checkpoints that verify success |\n| SKILL.md too long | Move detailed content to `references\u002F` files |\n| Hardcoded environment assumptions | Document requirements in `compatibility` field |\n| Missing CODEOWNERS entry | Add entries for both `\u002Fplugins\u002F\u003Cplugin>\u002Fskills\u002F\u003Cskill-name>\u002F` and `\u002Ftests\u002F\u003Cplugin>\u002F\u003Cskill-name>\u002F` matching sibling skills' owner pattern |\n\n## References\n\n- [Agent Skills Specification](https:\u002F\u002Fagentskills.io\u002Fspecification)\n- [Repository README](..\u002F..\u002FREADME.md)\n- [Contributing Guidelines](..\u002F..\u002FCONTRIBUTING.md)\n",{"name":5,"description":7},"main","5810d492c9b301d8227f932bf87b5c954c4fa4d6",".agents\u002Fskills\u002Fcreate-skill","https:\u002F\u002Fgithub.com\u002Fweiflycc-cmd\u002Fskills","https:\u002F\u002Fgithub.com\u002Fweiflycc-cmd","weiflycc.com","2026-11-10 03:26:55",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add weiflycc-cmd\u002Fskills --skill create-skill",{"tool":37,"command":38},"bunx","bunx skills add weiflycc-cmd\u002Fskills --skill create-skill",{"tool":40,"command":41},"pnpm","pnpm dlx skills add weiflycc-cmd\u002Fskills --skill create-skill","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fweiflycc-cmd\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcreate-skill\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M76SGT4WG5682JQJ0V3NSK6X","system-text-json-net11","Provides guidance on new System.Text.Json APIs introduced in .NET 11. It covers typed JsonTypeInfo access via GetTypeInfo\u003CT> and TryGetTypeInfo\u003CT> on JsonSerializerOptions, and the new JsonNamingPolicy.PascalCase static property. Use when serializing or deserializing JSON in .NET 11 applications and needing typed metadata access or PascalCase property naming.","https:\u002F\u002Fgithub.com\u002Fweiflycc-cmd\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fdotnet11\u002Fskills\u002Fsystem-text-json-net11\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M76SGPNZYYV9BCZJW7BF7J8A","nuget-trusted-publishing","Set up NuGet trusted publishing (OIDC) on a GitHub Actions repo — replaces long-lived API keys with short-lived tokens. USE FOR: trusted publishing, NuGet OIDC, keyless NuGet publish, migrate from NuGet API key, NuGet\u002Flogin, secure NuGet publishing. DO NOT USE FOR: publishing to private feeds or Azure Artifacts (OIDC is nuget.org only). INVOKES: shell (powershell or bash), edit, create, ask_user for guided repo setup.","https:\u002F\u002Fgithub.com\u002Fweiflycc-cmd\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fdotnet\u002Fskills\u002Fnuget-trusted-publishing\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M76SGHVNBNVM1DMVDYTMAE5G","dotnet-pinvoke","Correctly call native (C\u002FC++) libraries from .NET using P\u002FInvoke and LibraryImport. Covers function signatures, string marshalling, memory lifetime, SafeHandle, and cross-platform patterns. USE FOR: writing new P\u002FInvoke or LibraryImport declarations, reviewing or debugging existing native interop code, wrapping a C or C++ library for use in .NET, diagnosing crashes, memory leaks, or corruption at the managed\u002Fnative boundary. DO NOT USE FOR: COM interop, C++\u002FCLI mixed-mode assemblies, or pure managed code with no native dependencies.","https:\u002F\u002Fgithub.com\u002Fweiflycc-cmd\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fdotnet\u002Fskills\u002Fdotnet-pinvoke\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M76SGDB9Z3GSB1CFW314NC84","csharp-scripts","Run file-based C# apps with the .NET CLI when the user explicitly wants C#\u002F.NET code without creating a project. Use for C# language\u002FAPI experiments, one-file C# apps, small multi-file C# apps composed with `#:include`\u002F`#:exclude`, or C# file-based apps linked with `#:ref`. Do not use for language-agnostic throwaway scripts, generic computations, Python\u002FPowerShell-style automation, full projects, or existing app integration.","https:\u002F\u002Fgithub.com\u002Fweiflycc-cmd\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fdotnet\u002Fskills\u002Fcsharp-scripts\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M76SG805T8W764WAKB1NP3CJ","thread-abort-migration","Guides migration of .NET Framework Thread.Abort usage to cooperative cancellation in modern .NET. USE FOR: modernizing code that calls Thread.Abort, catching ThreadAbortException, replacing Thread.ResetAbort, replacing Thread.Interrupt for thread termination, resolving PlatformNotSupportedException or SYSLIB0006 after retargeting to .NET 6+, migrating ASP.NET Response.End or Response.Redirect(url, true) which internally call Thread.Abort. DO NOT USE FOR: code that only uses Thread.Join, Thread.Sleep, or Thread.Start without any abort, interrupt, or ThreadAbortException usage — these APIs work identically in modern .NET and need no migration. Also not for projects staying on .NET Framework, or Thread.Abort usage inside third-party libraries you do not control.","https:\u002F\u002Fgithub.com\u002Fweiflycc-cmd\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fdotnet-upgrade\u002Fskills\u002Fthread-abort-migration\u002FSKILL.md",[],[],{"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":87,"publishedAt":19},"01M76SG2588ZJBE5C51HYJJSKV","migrate-nullable-references","Enable nullable reference types in a C# project and systematically resolve all warnings. USE FOR: adopting NRTs in existing codebases, file-by-file or project-wide migration, fixing CS8602\u002FCS8618\u002FCS86xx warnings, annotating APIs for nullability, cleaning up null-forgiving operators, upgrading dependencies with new nullable annotations. DO NOT USE FOR: projects already fully migrated with zero warnings (unless auditing suppressions), fixing a handful of nullable warnings in code that already has NRTs enabled, suppressing warnings without fixing them, C# 7.3 or earlier projects. INVOKES: Get-NullableReadiness.ps1 scanner script.","https:\u002F\u002Fgithub.com\u002Fweiflycc-cmd\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fdotnet-upgrade\u002Fskills\u002Fmigrate-nullable-references\u002FSKILL.md",[],[]]