[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M69AF0RHM1NAZBAPBS6TEK0H":3,"skill-same:01M69AF0RHM1NAZBAPBS6TEK0H":70},{"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":28,"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":47,"ownerDescription":48,"updatedAt":49,"install":50,"resources":63},"01M69AF0RHM1NAZBAPBS6TEK0H","sql-server-dba",null,"Diagnose SQL Server and Azure SQL with safe native evidence","microsoft\u002Ffrontier-sre-agent-rvas","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M69AEEC1N2F4B8HCZH37RK7V",8,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ffrontier-sre-agent-rvas\u002Fblob\u002Fmain\u002FStudent\u002FResources\u002Fsql-server-mcp\u002Fagent\u002Fskills\u002Fsql-server-dba\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[29,30,31,32,33,34],"sql","sql server","sql server dba","safe","azure sql","diagnose","2026-11-10 10:12:30",false,"---\nname: sql-server-dba\ndescription: 'Diagnose SQL Server and Azure SQL with safe native evidence'\n---\n\n# SQL Server DBA\n\n## Overview\n\nUse native SQL Server and Azure SQL capabilities to discover database structure,\nmonitor health, troubleshoot incidents, identify performance bottlenecks, and\nproduce evidence-based tuning recommendations.\n\nThis skill is read-only and platform-aware. It does not create database helper\nobjects or treat a recommendation as permission to apply a change.\n\n## Prerequisites\n\nBefore querying a target, require:\n\n* The `sqlserver-mcp` connector assigned explicitly to the custom agent\n* An explicit server or service endpoint and database name\n* A permitted observation scope and time window\n* Required database and performance-state permissions\n\nFor Azure SQL, use the Azure SRE Agent user-assigned managed identity through\nthe `sqlserver-mcp` connection. The MCP workload identity must exist as a\ncontained Microsoft Entra user in the target database and hold the approved\nread-only role. Azure RBAC alone does not grant SQL data-plane access.\n\nFor SQL Server outside Azure SQL, use only an approved connection and\nauthentication profile exposed by `sqlserver-mcp`. If none exists, report the\nmissing prerequisite. Never substitute the SQL administrator, request a\npassword, or invent another authentication method.\n\n## Exclusive Tool Contract\n\nUse only these `sqlserver-mcp` tools for live database work:\n\n| Tool            | Use                                                                        |\n|-----------------|----------------------------------------------------------------------------|\n| `list_profiles` | Discover allowlisted targets and select the correct profile                |\n| `get_object`    | Retrieve native metadata for one relation or routine                       |\n| `run_query`     | Run bounded, parameterized, parser-validated read-only T-SQL                |\n| `analyze_query` | Compile and summarize an estimated execution plan without running workload |\n\nDo not use ODBC, pyodbc, sqlcmd, Azure CLI, PowerShell, Python, shell commands,\nlanguage drivers, generated programs, or another connector to open or query a\ndatabase.\n\nDo not install packages, drivers, or command-line utilities. Do not construct\nor handle connection strings, passwords, or access tokens.\n\nIf the connector or required profile is unavailable, stop and report the\nmissing capability. A failed MCP call is evidence to troubleshoot, not\npermission to attempt another connection path.\n\n## Quick Start\n\n1. Confirm the target server, database, user objective, incident time window,\n   and whether production query execution is permitted.\n2. Call `list_profiles` and select the named target profile.\n3. Identify the engine edition, product version, database, compatibility level,\n   and available permissions with a bounded `run_query` call.\n4. Select the smallest diagnostic path that answers the request.\n5. Run bounded native metadata and diagnostic queries.\n6. Correlate evidence before identifying a cause.\n7. Report findings, limitations, recommendations, and confirmation that no\n   changes were applied.\n\n## Connection and Capability Discovery\n\nFor Azure SQL:\n\n* Use only the configured `sqlserver-mcp` profile\n* Require the logical server fully qualified domain name and database name\n* Let the MCP service acquire and apply the Azure SQL token\n* Do not request, display, cache, or pass a raw token in conversation\n* Rely on the MCP connection policy for encryption and certificate validation\n* Never use the SQL-authenticated administrator\n\nFor other SQL Server deployments:\n\n* Use only a named profile on the same `sqlserver-mcp` connector\n* Do not assume that the Azure SRE Agent UAMI is accepted outside Azure SQL\n* Stop when network reachability, trust, or authentication is unresolved\n\nAfter connecting, collect only the identifiers needed to choose supported\nqueries:\n\n* `SERVERPROPERTY('EngineEdition')`\n* `SERVERPROPERTY('ProductVersion')`\n* `SERVERPROPERTY('ProductLevel')`\n* `SERVERPROPERTY('Edition')`\n* `DB_NAME()`\n* Database compatibility level\n* Query Store state\n* Effective database performance-state permissions\n\nDo not run server-scoped queries until the platform and effective permissions\nshow that they are available.\n\n## Diagnostic Workflow\n\n### Understand database structure\n\nUse `run_query` with native catalog views to discover:\n\n* Schemas, tables, views, and programmable objects\n* Columns, data types, nullability, defaults, and computed columns\n* Primary keys, unique constraints, checks, and foreign keys\n* Index keys, included columns, filters, and disabled state\n* Declared dependencies between objects\n\nBuild entity relationships from declared primary and foreign keys. Label\nrelationships inferred from naming or query behavior as inferred, not declared.\nDo not sample business data unless the user asks and the sample is necessary.\nUse `get_object` when details for one known relation or routine are sufficient.\n\n### Establish current activity\n\nInspect bounded current activity for:\n\n* Active requests and sessions\n* Wait type, wait duration, blocking session, and resource\n* Open transactions and transaction age\n* Locks involved in an active blocking chain\n* Query text and available plans\n* Memory grants and spills where evidence exists\n\nCapture observation timestamps in UTC. Current-state DMVs are point-in-time\nevidence and must not be described as historical trends.\n\n### Analyze historical query performance\n\nUse Query Store when it is enabled and readable:\n\n* Compare runtime intervals rather than lifetime averages alone\n* Identify regressions in duration, CPU, reads, writes, and execution count\n* Compare plans and plan changes for the same query\n* Consider parameter-sensitive behavior and workload shifts\n* Record Query Store capture state and observation interval\n\nIf Query Store is unavailable, use live and cached evidence and state that the\nhistorical conclusion is limited. Do not enable or reconfigure Query Store.\n\n### Investigate resource bottlenecks\n\nCorrelate workload evidence across relevant categories:\n\n* CPU pressure and expensive queries\n* Data and log I\u002FO latency\n* Database and server waits\n* Blocking, lock escalation, and deadlocks\n* Memory grants, concurrency, and spills\n* Tempdb usage and contention\n* Transaction-log usage and long-running transactions\n* Storage, database size, and growth\n* Azure SQL resource-governance and service-tier limits\n\nWait statistics identify where time accumulated, not root cause by themselves.\nAccount for scope, reset time, benign waits, platform filtering, and the\nobservation window.\n\n### Evaluate plans, indexes, and statistics\n\nWhen evidence points to query-plan quality, use `analyze_query` for an\nestimated plan:\n\n* Correlate estimated-plan evidence with Query Store or existing runtime data\n* Check estimates, predicates, join strategies, conversions, spills, and\n  memory grants\n* Check whether parameter values or plan changes explain the behavior\n* Evaluate existing indexes before proposing another one\n* Treat missing-index DMVs as cumulative, volatile suggestions\n* Consider write cost, storage, overlap, selectivity, and maintenance cost\n* Check statistics metadata and modification counters before attributing stale\n  estimates to statistics\n\n`analyze_query` does not execute the submitted workload. Do not seek another\ntool or connection method to obtain an actual plan.\n\nSee [native diagnostics](references\u002Fnative-diagnostics.md) for the preferred\nsystem surfaces and platform notes.\n\n## Query Safety Rules\n\nApply these rules to every SQL query:\n\n* Use read-only statements and native system objects\n* Fully qualify system objects with the `sys` schema\n* Select named columns instead of `SELECT *`, especially from DMVs\n* Add `TOP`, time ranges, database filters, or object filters where applicable\n* Avoid broad plan-cache extraction and unbounded XML plan retrieval\n* Use `LIMITED` or narrowly scoped modes for expensive physical-statistics\n  functions\n* Avoid scanning application tables unless the user request requires it\n* Do not execute application stored procedures\n* Do not expose credentials, tokens, sensitive query parameters, or business\n  data in the response\n\nNever execute:\n\n* `INSERT`, `UPDATE`, `DELETE`, `MERGE`, or bulk data operations\n* `CREATE`, `ALTER`, `DROP`, `TRUNCATE`, or permission changes\n* Index rebuilds, reorganizations, creation, or removal\n* Statistics updates\n* Query Store plan forcing, hints, capture changes, or cleanup\n* Configuration changes, failovers, backup, restore, or maintenance commands\n* Creation of monitoring views, procedures, tables, functions, jobs, or\n  Extended Events sessions\n\nExisting Extended Events sessions and targets may be read when the tool,\nplatform, and permissions support safe access.\n\n## Evidence Standard\n\nClassify every important statement as one of:\n\n* Observation supported by returned evidence\n* Interpretation consistent with the evidence\n* Hypothesis requiring additional evidence\n* Recommendation not yet applied\n\nFor each finding, record:\n\n* Target and UTC observation window\n* Native source and relevant identifiers\n* Measured value or returned state\n* Expected impact\n* Alternative explanations\n* Evidence needed to confirm the cause\n\nDo not claim that a recommendation resolves an issue until a controlled change\nand post-change measurement demonstrate the result.\n\n## Response Format\n\nReturn:\n\n1. **Scope**: target, platform, database, time window, and permissions\n2. **Findings**: impact-ranked observations with native evidence\n3. **Analysis**: interpretation, correlations, and uncertainties\n4. **Recommendations**: read-only next steps or proposed changes with tradeoffs\n5. **Limitations**: unavailable evidence, permissions, or platform constraints\n6. **Change status**: state that no database changes were applied\n\nWhen no bottleneck is demonstrated, say so and identify the observation window\nand evidence reviewed. Do not manufacture an issue to satisfy the request.\n\n## Troubleshooting\n\nIf authentication fails, distinguish:\n\n* Azure SRE Agent to MCP managed identity or audience failure\n* MCP target profile missing or unavailable\n* Network or DNS reachability\n* TLS or certificate validation\n* Microsoft Entra token or identity failure\n* Missing contained database user\n* Login accepted but database access denied\n* Required DMV permission denied\n\nReturn the exact failure without exposing secrets. Do not retry with broader\ncredentials or another database client.\n\nIf a system object or column is unavailable, verify the engine, version, and\nplatform-specific documentation. Use a supported alternative or report the\nlimitation. Do not guess a replacement column.\n\nIf evidence is empty, check capture state, reset time, filters, permissions,\nand workload activity before concluding that the condition did not occur.","# SQL Server DBA\n\n## Overview\n\nUse native SQL Server and Azure SQL capabilities to discover database structure,\nmonitor health, troubleshoot incidents, identify performance bottlenecks, and\nproduce evidence-based tuning recommendations.\n\nThis skill is read-only and platform-aware. It does not create database helper\nobjects or treat a recommendation as permission to apply a change.\n\n## Prerequisites\n\nBefore querying a target, require:\n\n* The `sqlserver-mcp` connector assigned explicitly to the custom agent\n* An explicit server or service endpoint and database name\n* A permitted observation scope and time window\n* Required database and performance-state permissions\n\nFor Azure SQL, use the Azure SRE Agent user-assigned managed identity through\nthe `sqlserver-mcp` connection. The MCP workload identity must exist as a\ncontained Microsoft Entra user in the target database and hold the approved\nread-only role. Azure RBAC alone does not grant SQL data-plane access.\n\nFor SQL Server outside Azure SQL, use only an approved connection and\nauthentication profile exposed by `sqlserver-mcp`. If none exists, report the\nmissing prerequisite. Never substitute the SQL administrator, request a\npassword, or invent another authentication method.\n\n## Exclusive Tool Contract\n\nUse only these `sqlserver-mcp` tools for live database work:\n\n| Tool            | Use                                                                        |\n|-----------------|----------------------------------------------------------------------------|\n| `list_profiles` | Discover allowlisted targets and select the correct profile                |\n| `get_object`    | Retrieve native metadata for one relation or routine                       |\n| `run_query`     | Run bounded, parameterized, parser-validated read-only T-SQL                |\n| `analyze_query` | Compile and summarize an estimated execution plan without running workload |\n\nDo not use ODBC, pyodbc, sqlcmd, Azure CLI, PowerShell, Python, shell commands,\nlanguage drivers, generated programs, or another connector to open or query a\ndatabase.\n\nDo not install packages, drivers, or command-line utilities. Do not construct\nor handle connection strings, passwords, or access tokens.\n\nIf the connector or required profile is unavailable, stop and report the\nmissing capability. A failed MCP call is evidence to troubleshoot, not\npermission to attempt another connection path.\n\n## Quick Start\n\n1. Confirm the target server, database, user objective, incident time window,\n   and whether production query execution is permitted.\n2. Call `list_profiles` and select the named target profile.\n3. Identify the engine edition, product version, database, compatibility level,\n   and available permissions with a bounded `run_query` call.\n4. Select the smallest diagnostic path that answers the request.\n5. Run bounded native metadata and diagnostic queries.\n6. Correlate evidence before identifying a cause.\n7. Report findings, limitations, recommendations, and confirmation that no\n   changes were applied.\n\n## Connection and Capability Discovery\n\nFor Azure SQL:\n\n* Use only the configured `sqlserver-mcp` profile\n* Require the logical server fully qualified domain name and database name\n* Let the MCP service acquire and apply the Azure SQL token\n* Do not request, display, cache, or pass a raw token in conversation\n* Rely on the MCP connection policy for encryption and certificate validation\n* Never use the SQL-authenticated administrator\n\nFor other SQL Server deployments:\n\n* Use only a named profile on the same `sqlserver-mcp` connector\n* Do not assume that the Azure SRE Agent UAMI is accepted outside Azure SQL\n* Stop when network reachability, trust, or authentication is unresolved\n\nAfter connecting, collect only the identifiers needed to choose supported\nqueries:\n\n* `SERVERPROPERTY('EngineEdition')`\n* `SERVERPROPERTY('ProductVersion')`\n* `SERVERPROPERTY('ProductLevel')`\n* `SERVERPROPERTY('Edition')`\n* `DB_NAME()`\n* Database compatibility level\n* Query Store state\n* Effective database performance-state permissions\n\nDo not run server-scoped queries until the platform and effective permissions\nshow that they are available.\n\n## Diagnostic Workflow\n\n### Understand database structure\n\nUse `run_query` with native catalog views to discover:\n\n* Schemas, tables, views, and programmable objects\n* Columns, data types, nullability, defaults, and computed columns\n* Primary keys, unique constraints, checks, and foreign keys\n* Index keys, included columns, filters, and disabled state\n* Declared dependencies between objects\n\nBuild entity relationships from declared primary and foreign keys. Label\nrelationships inferred from naming or query behavior as inferred, not declared.\nDo not sample business data unless the user asks and the sample is necessary.\nUse `get_object` when details for one known relation or routine are sufficient.\n\n### Establish current activity\n\nInspect bounded current activity for:\n\n* Active requests and sessions\n* Wait type, wait duration, blocking session, and resource\n* Open transactions and transaction age\n* Locks involved in an active blocking chain\n* Query text and available plans\n* Memory grants and spills where evidence exists\n\nCapture observation timestamps in UTC. Current-state DMVs are point-in-time\nevidence and must not be described as historical trends.\n\n### Analyze historical query performance\n\nUse Query Store when it is enabled and readable:\n\n* Compare runtime intervals rather than lifetime averages alone\n* Identify regressions in duration, CPU, reads, writes, and execution count\n* Compare plans and plan changes for the same query\n* Consider parameter-sensitive behavior and workload shifts\n* Record Query Store capture state and observation interval\n\nIf Query Store is unavailable, use live and cached evidence and state that the\nhistorical conclusion is limited. Do not enable or reconfigure Query Store.\n\n### Investigate resource bottlenecks\n\nCorrelate workload evidence across relevant categories:\n\n* CPU pressure and expensive queries\n* Data and log I\u002FO latency\n* Database and server waits\n* Blocking, lock escalation, and deadlocks\n* Memory grants, concurrency, and spills\n* Tempdb usage and contention\n* Transaction-log usage and long-running transactions\n* Storage, database size, and growth\n* Azure SQL resource-governance and service-tier limits\n\nWait statistics identify where time accumulated, not root cause by themselves.\nAccount for scope, reset time, benign waits, platform filtering, and the\nobservation window.\n\n### Evaluate plans, indexes, and statistics\n\nWhen evidence points to query-plan quality, use `analyze_query` for an\nestimated plan:\n\n* Correlate estimated-plan evidence with Query Store or existing runtime data\n* Check estimates, predicates, join strategies, conversions, spills, and\n  memory grants\n* Check whether parameter values or plan changes explain the behavior\n* Evaluate existing indexes before proposing another one\n* Treat missing-index DMVs as cumulative, volatile suggestions\n* Consider write cost, storage, overlap, selectivity, and maintenance cost\n* Check statistics metadata and modification counters before attributing stale\n  estimates to statistics\n\n`analyze_query` does not execute the submitted workload. Do not seek another\ntool or connection method to obtain an actual plan.\n\nSee [native diagnostics](references\u002Fnative-diagnostics.md) for the preferred\nsystem surfaces and platform notes.\n\n## Query Safety Rules\n\nApply these rules to every SQL query:\n\n* Use read-only statements and native system objects\n* Fully qualify system objects with the `sys` schema\n* Select named columns instead of `SELECT *`, especially from DMVs\n* Add `TOP`, time ranges, database filters, or object filters where applicable\n* Avoid broad plan-cache extraction and unbounded XML plan retrieval\n* Use `LIMITED` or narrowly scoped modes for expensive physical-statistics\n  functions\n* Avoid scanning application tables unless the user request requires it\n* Do not execute application stored procedures\n* Do not expose credentials, tokens, sensitive query parameters, or business\n  data in the response\n\nNever execute:\n\n* `INSERT`, `UPDATE`, `DELETE`, `MERGE`, or bulk data operations\n* `CREATE`, `ALTER`, `DROP`, `TRUNCATE`, or permission changes\n* Index rebuilds, reorganizations, creation, or removal\n* Statistics updates\n* Query Store plan forcing, hints, capture changes, or cleanup\n* Configuration changes, failovers, backup, restore, or maintenance commands\n* Creation of monitoring views, procedures, tables, functions, jobs, or\n  Extended Events sessions\n\nExisting Extended Events sessions and targets may be read when the tool,\nplatform, and permissions support safe access.\n\n## Evidence Standard\n\nClassify every important statement as one of:\n\n* Observation supported by returned evidence\n* Interpretation consistent with the evidence\n* Hypothesis requiring additional evidence\n* Recommendation not yet applied\n\nFor each finding, record:\n\n* Target and UTC observation window\n* Native source and relevant identifiers\n* Measured value or returned state\n* Expected impact\n* Alternative explanations\n* Evidence needed to confirm the cause\n\nDo not claim that a recommendation resolves an issue until a controlled change\nand post-change measurement demonstrate the result.\n\n## Response Format\n\nReturn:\n\n1. **Scope**: target, platform, database, time window, and permissions\n2. **Findings**: impact-ranked observations with native evidence\n3. **Analysis**: interpretation, correlations, and uncertainties\n4. **Recommendations**: read-only next steps or proposed changes with tradeoffs\n5. **Limitations**: unavailable evidence, permissions, or platform constraints\n6. **Change status**: state that no database changes were applied\n\nWhen no bottleneck is demonstrated, say so and identify the observation window\nand evidence reviewed. Do not manufacture an issue to satisfy the request.\n\n## Troubleshooting\n\nIf authentication fails, distinguish:\n\n* Azure SRE Agent to MCP managed identity or audience failure\n* MCP target profile missing or unavailable\n* Network or DNS reachability\n* TLS or certificate validation\n* Microsoft Entra token or identity failure\n* Missing contained database user\n* Login accepted but database access denied\n* Required DMV permission denied\n\nReturn the exact failure without exposing secrets. Do not retry with broader\ncredentials or another database client.\n\nIf a system object or column is unavailable, verify the engine, version, and\nplatform-specific documentation. Use a supported alternative or report the\nlimitation. Do not guess a replacement column.\n\nIf evidence is empty, check capture state, reset time, filters, permissions,\nand workload activity before concluding that the condition did not occur.",{"name":5,"description":7},"main","866211cec05349537247310817d4159381245d11","Student\u002FResources\u002Fsql-server-mcp\u002Fagent\u002Fskills\u002Fsql-server-dba",17,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ffrontier-sre-agent-rvas","https:\u002F\u002Fmicrosoft.github.io\u002Ffrontier-sre-agent-rvas\u002F","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-13 02:08:04",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add microsoft\u002Ffrontier-sre-agent-rvas --skill sql-server-dba",{"tool":56,"command":57},"bunx","bunx skills add microsoft\u002Ffrontier-sre-agent-rvas --skill sql-server-dba",{"tool":59,"command":60},"pnpm","pnpm dlx skills add microsoft\u002Ffrontier-sre-agent-rvas --skill sql-server-dba","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ffrontier-sre-agent-rvas\u002Fblob\u002Fmain\u002FStudent\u002FResources\u002Fsql-server-mcp\u002Fagent\u002Fskills\u002Fsql-server-dba\u002FSKILL.md",true,[64],{"path":65,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Fnative-diagnostics.md","REFERENCE","参考文档",9908,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ffrontier-sre-agent-rvas\u002Fblob\u002Fmain\u002FStudent\u002FResources\u002Fsql-server-mcp\u002Fagent\u002Fskills\u002Fsql-server-dba\u002Freferences\u002Fnative-diagnostics.md",[71,83,94,104,111,118],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":35},"01M6PJ2RHX48TKT2J011CMECNN","example","Use when the user asks for the example check. Describe the trigger here.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ffrontier-sre-agent-rvas\u002Fblob\u002Fmain\u002Fusecases\u002F_template\u002Fmanifests\u002Fskills\u002Fexample\u002FSKILL.md",[],[73,78,79,80,81,82],"check","user","use","trigger","for",{"skillNo":84,"name":85,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":91,"publishedAt":35},"01M6PJ2M7WX6EK7VQ6C2TMP2DS","0003-skill-only","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ffrontier-sre-agent-rvas\u002Fblob\u002Fmain\u002Fusecases\u002F_framework\u002Ftests\u002Ffixtures\u002Fvalid\u002F0003-skill-only\u002FSKILL.md",[88],{"categoryNo":89,"categoryName":90,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[92,93],"only","0003 skill only",{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":35},"01M6PJ2FSA6RJ4WK7HDGYTPVWM","validated-fixture","Fixture skill.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ffrontier-sre-agent-rvas\u002Fblob\u002Fmain\u002Fusecases\u002F_framework\u002Ftests\u002Ffixtures\u002Fvalid\u002F0002-validated-fixture\u002FSKILL.md",[],[101,102,103],"fixture","validated fixture","fixture skill",{"skillNo":105,"name":106,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":35},"01M6PJ2BXMH50J34D20XZH0T5Y","0001-vnt","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ffrontier-sre-agent-rvas\u002Fblob\u002Fmain\u002Fusecases\u002F_framework\u002Ftests\u002Ffixtures\u002Finvalid\u002Fvalidated-no-tests\u002F0001-vnt\u002FSKILL.md",[],[110],"0001 vnt",{"skillNo":112,"name":113,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":35},"01M6PJ27V9011D0AE8RJ76VSMZ","0001-iwc","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ffrontier-sre-agent-rvas\u002Fblob\u002Fmain\u002Fusecases\u002F_framework\u002Ftests\u002Ffixtures\u002Finvalid\u002Fidea-with-components\u002F0001-iwc\u002FSKILL.md",[],[117],"0001 iwc",{"skillNo":119,"name":120,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":35},"01M6PJ26EA35R4PBY543D50SGK","0001-no-products","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ffrontier-sre-agent-rvas\u002Fblob\u002Fmain\u002Fusecases\u002F_framework\u002Ftests\u002Ffixtures\u002Finvalid\u002Fbuilt-no-products\u002F0001-no-products\u002FSKILL.md",[],[124],"0001 no products"]