[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M69A0STTQJ0PDQHNXR6R08Z4":3,"skill-same:01M69A0STTQJ0PDQHNXR6R08Z4":65},{"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":26,"publishedAt":36,"linkOnly":37,"markdownContent":38,"markdownBody":39,"frontMatter":40,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":44,"repositoryHtmlUrl":45,"repositoryHomepageUrl":46,"ownerHtmlUrl":47,"ownerBlogUrl":48,"ownerDescription":49,"updatedAt":50,"install":51,"resources":64},"01M69A0STTQJ0PDQHNXR6R08Z4","sqlsimtools-build",null,"Build and test sqlsimtools from source. USE WHEN: cloning the repository, setting up a development environment, compiling sqlsim, preparing sqlpysim, building sqlsim Studio, running smoke tests or the full test suite, checking prerequisites, or diagnosing a build or test failure on Windows or Linux. DO NOT USE FOR: running SQL workloads with the released tools (use the sqlsim or sqlpysim skills), or cutting a release (use the sqlsimtools-release skill).","microsoft\u002Fsqlsimtools","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M69A087F3FDFGXM54PHMKQ9Z",49,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fsqlsimtools\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fsqlsimtools-build\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",[27,28,29,30,31,32,33,34,35],"sqlsimtools build","linux","build and test","test","smoke tests","windows","sql","sqlpysim","sqlsim","2026-11-10 10:12:30",false,"---\nname: sqlsimtools-build\ndescription: \"Build and test sqlsimtools from source. USE WHEN: cloning the repository, setting up a development environment, compiling sqlsim, preparing sqlpysim, building sqlsim Studio, running smoke tests or the full test suite, checking prerequisites, or diagnosing a build or test failure on Windows or Linux. DO NOT USE FOR: running SQL workloads with the released tools (use the sqlsim or sqlpysim skills), or cutting a release (use the sqlsimtools-release skill).\"\n---\n\n# Build and test sqlsimtools\n\nDeveloper skill for working with this repository's source. Each tool builds and\ntests independently and owns its own scripts. Always run a tool's scripts from\nthat tool's directory.\n\n## Order of operations\n\n1. Check prerequisites.\n2. Build the tool.\n3. Run its smoke test.\n4. Run its full test suite if behavior changed.\n\nStudio depends on step 2 for sqlsim: its build copies the compiled binary out\nof `sqlsim\u002Fbuild\u002F\u003Carch>\u002FRelease\u002F`. Build sqlsim before building Studio.\n\n## Prerequisites\n\n| Tool | Windows | Linux |\n|------|---------|-------|\n| sqlsim | `.\\check-prerequisites.ps1` | `bash .\u002Fcheck-prerequisites-linux.sh --require-driver` |\n| sqlpysim | `python --version` (3.10+), then `python -c \"import mssql_python\"` after installing requirements | Verify Python 3.10+, install `mssql-python`, then use the native Bash suites below |\n| Studio | .NET 10 SDK | .NET 10 SDK |\n\nAll tools need Microsoft ODBC Driver 18 to reach a live SQL target. sqlsim also\nneeds CMake 3.15+ and a C++17 toolchain: Visual Studio 2022 or 2026 Build Tools\non Windows, `build-essential` and `unixodbc-dev` on Ubuntu.\n\n## Build\n\n```powershell\n# sqlsim, Windows. Default builds x64 and ARM64.\ncd sqlsim\n.\\build.ps1 -Clean -Architecture x64\n\n# sqlsim Studio, Windows. Requires sqlsim built first.\ncd sqlsimstudio\n.\\build.ps1 -Runtime win-x64\n```\n\n```bash\n# sqlsim, Ubuntu 24.04 or 26.04 LTS x64\ncd sqlsim\nbash .\u002Fbuild-linux.sh --clean\n\n# sqlsim Studio, Linux\ncd sqlsimstudio\nbash .\u002Fbuild-linux.sh linux-x64\n```\n\nsqlpysim has no build step:\n\n```powershell\ncd sqlpysim\npython -m pip install -r requirements.txt\n```\n\nBuild outputs:\n\n| Tool | Windows | Linux |\n|------|---------|-------|\n| sqlsim | `build\u002Fx64\u002FRelease\u002Fsqlsim.exe`, `build\u002FARM64\u002FRelease\u002Fsqlsim.exe` | `build\u002Flinux-x64\u002Fsqlsim` |\n| Studio | `build\u002Fwin-x64\u002Fsqlsimstudio.exe` | `build\u002Flinux-x64\u002Fsqlsimstudio` |\n\n## Install a source build into a project\n\nTo install sqlsim (and optionally sqlpysim) with its manual, examples, skill,\nand Workload Builder into another project, use the wrapper from the repository\nroot rather than copying files:\n\n```powershell\n.\\scripts\\install-local.ps1 -Workspace C:\\myproject -Build\n.\\scripts\\install-local.ps1 -Workspace C:\\myproject -Tool sqlsim, sqlpysim -Preview\n```\n\nIt checks prerequisites, builds, installs, validates offline, and prints a\nreceipt. It never deletes project files and stops before writing if a file it\ninstalls already differs; re-run with `-Force` only after the user agrees to\nreplace those files. On Ubuntu use\n`bash sqlsim\u002Fpublish-linux.sh --skip-build --release-dir \u003Cproject>`, which\naccepts `--preview` and `--force`. Re-check an installed project with\n`release\\validate-package-layout.ps1`.\n\n## Test\n\nSmoke tests are fast and validate core behavior. The full suites are the gate\nfor any behavior or CLI change.\n\n```powershell\ncd sqlsim\n.\\smoke-test.ps1 -SkipBuild\n.\\full-test-suite.ps1 -SkipBuild\n```\n\n```bash\ncd sqlsim\nbash .\u002Fsmoke-test-linux.sh\nbash .\u002Ffull-test-suite-linux.sh\n```\n\nShared parameters for sqlsim `smoke-test.ps1` and `full-test-suite.ps1`:\n`-Server`, `-Database`, `-UseToken`, `-Username`, `-Password`, `-SkipBuild`,\n`-Verbose`, `-OutputFile`. `full-test-suite.ps1` also accepts `-SkipScale` to\nskip the 1024-thread test on constrained targets.\n\nsqlpysim Windows tests use `smoke-test.ps1` and `full-test-suite.ps1`.\nNative Linux\u002FWSL Bash suites are supported for both tools, so PowerShell is not\nrequired. They take the target as options and work from any Linux VM,\ncontainer, or WSL distribution that can reach the server over TCP:\n\n```bash\ncd sqlpysim   # or sqlsim\nbash .\u002Fsmoke-test-linux.sh --server HOST --database DB \\\n  --username USER --password-file FILE\nbash .\u002Ffull-test-suite-linux.sh --server HOST --database DB \\\n  --username USER --password-file FILE\n```\n\nFor token authentication, use `--token-file FILE` instead of the username and\npassword options. Secret files are read from their first line, and a Windows\nCRLF ending is ignored. Every suite, PowerShell and Bash, hands the token or\npassword to the engine on stdin (`-T -`, `-P -`), so it never appears in a\nprocess list. When adding a test, build its arguments from the suite's auth\narray and launch the engine through the suite's launcher (`$runSqlsim`,\n`$runSqlPySim`, or `with_secret`) so this stays true. All four suites support `--list-tests` and `--help`.\nThe sqlpysim suites also take `--python` and `--skip-install`. The sqlsim full\nsuite takes `--sqlsim`, `--skip-scale`, and `--stop-on-error`, and needs `jq`.\nA WSL distribution in NAT mode cannot reach SQL Server on the Windows host via\n`localhost`; target a reachable server name or address instead.\n\nStudio `smoke-test.ps1` takes `-SkipBuild`, `-StartupOnly`, `-StudioExecutable`,\nand `-QueryStoreDatabase`. `-StartupOnly` is what CI uses to verify a packaged\nbuild starts without touching SQL Server. Interactive GUI coverage is manual and\ntracked in `sqlsimstudio\u002FMANUAL-TEST.md`.\n\nAzure SQL targets are auto-detected by server name. Prefer `-UseToken` over\ninteractive authentication so runs stay non-interactive:\n\n```powershell\n$token = az account get-access-token --resource https:\u002F\u002Fdatabase.windows.net --query accessToken -o tsv\n.\\full-test-suite.ps1 -SkipBuild -Server myserver.database.windows.net -Database mydb -UseToken $token\n```\n\n## Suite parity\n\nThe PowerShell and native Bash suites are deliberate parity counterparts for\nsqlsim and sqlpysim, so Linux and WSL users do not need PowerShell for the\nsupported test suites. Adding or changing a test in only one counterpart is a\ndefect. Check with:\n\n```powershell\n.\u002Fscripts\u002Fcheck-suite-parity.ps1\n```\n\n## Plugin packages\n\nCanonical skills live under `.github\u002Fskills\u002F`. Plugin copies are generated.\n\n```powershell\n.\u002Fscripts\u002Fsync-plugins.ps1      # after editing a canonical skill\n.\u002Fscripts\u002Fvalidate-plugins.ps1  # gate; also runs in CI\n```\n\nNever edit `plugins\u002F\u003Ctool>\u002Fskills\u002F` directly.\n\n## Rules\n\n1. Use each tool's own scripts. Do not call `cmake`, `msbuild`, or\n   `dotnet publish` directly.\n2. Never append `2>&1`, `> file`, or `| Select-String` to a tool invocation.\n   Capture into a variable instead, or use the script's `-OutputFile`.\n3. Supply exactly one authentication mode. Nothing defaults.\n4. Keep credentials out of process arguments. Use `-P -` or `-T -` with\n   redirected stdin where a script supports it.\n5. Do not scale thread counts against a shared or production SQL instance.\n6. Treat a failing test as a real defect until proven otherwise. Do not skip or\n   disable tests to get a green run.\n","# Build and test sqlsimtools\n\nDeveloper skill for working with this repository's source. Each tool builds and\ntests independently and owns its own scripts. Always run a tool's scripts from\nthat tool's directory.\n\n## Order of operations\n\n1. Check prerequisites.\n2. Build the tool.\n3. Run its smoke test.\n4. Run its full test suite if behavior changed.\n\nStudio depends on step 2 for sqlsim: its build copies the compiled binary out\nof `sqlsim\u002Fbuild\u002F\u003Carch>\u002FRelease\u002F`. Build sqlsim before building Studio.\n\n## Prerequisites\n\n| Tool | Windows | Linux |\n|------|---------|-------|\n| sqlsim | `.\\check-prerequisites.ps1` | `bash .\u002Fcheck-prerequisites-linux.sh --require-driver` |\n| sqlpysim | `python --version` (3.10+), then `python -c \"import mssql_python\"` after installing requirements | Verify Python 3.10+, install `mssql-python`, then use the native Bash suites below |\n| Studio | .NET 10 SDK | .NET 10 SDK |\n\nAll tools need Microsoft ODBC Driver 18 to reach a live SQL target. sqlsim also\nneeds CMake 3.15+ and a C++17 toolchain: Visual Studio 2022 or 2026 Build Tools\non Windows, `build-essential` and `unixodbc-dev` on Ubuntu.\n\n## Build\n\n```powershell\n# sqlsim, Windows. Default builds x64 and ARM64.\ncd sqlsim\n.\\build.ps1 -Clean -Architecture x64\n\n# sqlsim Studio, Windows. Requires sqlsim built first.\ncd sqlsimstudio\n.\\build.ps1 -Runtime win-x64\n```\n\n```bash\n# sqlsim, Ubuntu 24.04 or 26.04 LTS x64\ncd sqlsim\nbash .\u002Fbuild-linux.sh --clean\n\n# sqlsim Studio, Linux\ncd sqlsimstudio\nbash .\u002Fbuild-linux.sh linux-x64\n```\n\nsqlpysim has no build step:\n\n```powershell\ncd sqlpysim\npython -m pip install -r requirements.txt\n```\n\nBuild outputs:\n\n| Tool | Windows | Linux |\n|------|---------|-------|\n| sqlsim | `build\u002Fx64\u002FRelease\u002Fsqlsim.exe`, `build\u002FARM64\u002FRelease\u002Fsqlsim.exe` | `build\u002Flinux-x64\u002Fsqlsim` |\n| Studio | `build\u002Fwin-x64\u002Fsqlsimstudio.exe` | `build\u002Flinux-x64\u002Fsqlsimstudio` |\n\n## Install a source build into a project\n\nTo install sqlsim (and optionally sqlpysim) with its manual, examples, skill,\nand Workload Builder into another project, use the wrapper from the repository\nroot rather than copying files:\n\n```powershell\n.\\scripts\\install-local.ps1 -Workspace C:\\myproject -Build\n.\\scripts\\install-local.ps1 -Workspace C:\\myproject -Tool sqlsim, sqlpysim -Preview\n```\n\nIt checks prerequisites, builds, installs, validates offline, and prints a\nreceipt. It never deletes project files and stops before writing if a file it\ninstalls already differs; re-run with `-Force` only after the user agrees to\nreplace those files. On Ubuntu use\n`bash sqlsim\u002Fpublish-linux.sh --skip-build --release-dir \u003Cproject>`, which\naccepts `--preview` and `--force`. Re-check an installed project with\n`release\\validate-package-layout.ps1`.\n\n## Test\n\nSmoke tests are fast and validate core behavior. The full suites are the gate\nfor any behavior or CLI change.\n\n```powershell\ncd sqlsim\n.\\smoke-test.ps1 -SkipBuild\n.\\full-test-suite.ps1 -SkipBuild\n```\n\n```bash\ncd sqlsim\nbash .\u002Fsmoke-test-linux.sh\nbash .\u002Ffull-test-suite-linux.sh\n```\n\nShared parameters for sqlsim `smoke-test.ps1` and `full-test-suite.ps1`:\n`-Server`, `-Database`, `-UseToken`, `-Username`, `-Password`, `-SkipBuild`,\n`-Verbose`, `-OutputFile`. `full-test-suite.ps1` also accepts `-SkipScale` to\nskip the 1024-thread test on constrained targets.\n\nsqlpysim Windows tests use `smoke-test.ps1` and `full-test-suite.ps1`.\nNative Linux\u002FWSL Bash suites are supported for both tools, so PowerShell is not\nrequired. They take the target as options and work from any Linux VM,\ncontainer, or WSL distribution that can reach the server over TCP:\n\n```bash\ncd sqlpysim   # or sqlsim\nbash .\u002Fsmoke-test-linux.sh --server HOST --database DB \\\n  --username USER --password-file FILE\nbash .\u002Ffull-test-suite-linux.sh --server HOST --database DB \\\n  --username USER --password-file FILE\n```\n\nFor token authentication, use `--token-file FILE` instead of the username and\npassword options. Secret files are read from their first line, and a Windows\nCRLF ending is ignored. Every suite, PowerShell and Bash, hands the token or\npassword to the engine on stdin (`-T -`, `-P -`), so it never appears in a\nprocess list. When adding a test, build its arguments from the suite's auth\narray and launch the engine through the suite's launcher (`$runSqlsim`,\n`$runSqlPySim`, or `with_secret`) so this stays true. All four suites support `--list-tests` and `--help`.\nThe sqlpysim suites also take `--python` and `--skip-install`. The sqlsim full\nsuite takes `--sqlsim`, `--skip-scale`, and `--stop-on-error`, and needs `jq`.\nA WSL distribution in NAT mode cannot reach SQL Server on the Windows host via\n`localhost`; target a reachable server name or address instead.\n\nStudio `smoke-test.ps1` takes `-SkipBuild`, `-StartupOnly`, `-StudioExecutable`,\nand `-QueryStoreDatabase`. `-StartupOnly` is what CI uses to verify a packaged\nbuild starts without touching SQL Server. Interactive GUI coverage is manual and\ntracked in `sqlsimstudio\u002FMANUAL-TEST.md`.\n\nAzure SQL targets are auto-detected by server name. Prefer `-UseToken` over\ninteractive authentication so runs stay non-interactive:\n\n```powershell\n$token = az account get-access-token --resource https:\u002F\u002Fdatabase.windows.net --query accessToken -o tsv\n.\\full-test-suite.ps1 -SkipBuild -Server myserver.database.windows.net -Database mydb -UseToken $token\n```\n\n## Suite parity\n\nThe PowerShell and native Bash suites are deliberate parity counterparts for\nsqlsim and sqlpysim, so Linux and WSL users do not need PowerShell for the\nsupported test suites. Adding or changing a test in only one counterpart is a\ndefect. Check with:\n\n```powershell\n.\u002Fscripts\u002Fcheck-suite-parity.ps1\n```\n\n## Plugin packages\n\nCanonical skills live under `.github\u002Fskills\u002F`. Plugin copies are generated.\n\n```powershell\n.\u002Fscripts\u002Fsync-plugins.ps1      # after editing a canonical skill\n.\u002Fscripts\u002Fvalidate-plugins.ps1  # gate; also runs in CI\n```\n\nNever edit `plugins\u002F\u003Ctool>\u002Fskills\u002F` directly.\n\n## Rules\n\n1. Use each tool's own scripts. Do not call `cmake`, `msbuild`, or\n   `dotnet publish` directly.\n2. Never append `2>&1`, `> file`, or `| Select-String` to a tool invocation.\n   Capture into a variable instead, or use the script's `-OutputFile`.\n3. Supply exactly one authentication mode. Nothing defaults.\n4. Keep credentials out of process arguments. Use `-P -` or `-T -` with\n   redirected stdin where a script supports it.\n5. Do not scale thread counts against a shared or production SQL instance.\n6. Treat a failing test as a real defect until proven otherwise. Do not skip or\n   disable tests to get a green run.\n",{"name":5,"description":7},"main","767dba350d19a836343e0e82620a30778b6b4ec7",".github\u002Fskills\u002Fsqlsimtools-build",4,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fsqlsimtools","https:\u002F\u002Fmicrosoft.github.io\u002Fsqlsimtools\u002F","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-10-21 06:27:32",{"source":8,"skillName":5,"commands":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add microsoft\u002Fsqlsimtools --skill sqlsimtools-build",{"tool":57,"command":58},"bunx","bunx skills add microsoft\u002Fsqlsimtools --skill sqlsimtools-build",{"tool":60,"command":61},"pnpm","pnpm dlx skills add microsoft\u002Fsqlsimtools --skill sqlsimtools-build","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fsqlsimtools\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fsqlsimtools-build\u002FSKILL.md",true,[],[66,88,99,110,124,134],{"skillNo":67,"name":35,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":78,"publishedAt":36},"01M69A146N7H4J6BBJK4GSYJ5J","Run SQL queries, scripts, or multi-threaded workloads against SQL Server, Azure SQL Database, Azure SQL Managed Instance, or SQL database in Microsoft Fabric using the sqlsim CLI. USE FOR — executing T-SQL ad-hoc or from a `.sql` file; stress \u002F load testing with N threads × R iterations; measuring connection \u002F login \u002F fetch timings; producing JSON metrics for automation; capturing per-query statistics (`-querystats`). DO NOT USE FOR — non-SQL Server engines (MySQL, Postgres, Oracle), or schema generation \u002F data loading (sqlsim runs queries; it does not generate schemas).","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fsqlsimtools\u002Fblob\u002Fmain\u002Fplugins\u002Fsqlsim\u002Fskills\u002Fsqlsim\u002FSKILL.md",[71,72,73],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":74,"categoryName":75,"taxonomyType":76,"taxonomyTypeDesc":77},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[35,79,80,33,81,82,83,84,85,86,9,87],"load testing","sql server","azure sql database","microsoft fabric","testing","cli","oracle","automation","azure sql",{"skillNo":89,"name":34,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":94,"publishedAt":36},"01M69A11MWNF3Z8B1JNJ8HTT8D","Public Preview Python-based port of sqlsim built on Microsoft's native `mssql-python` driver. USE FOR — running SQL queries, scripts, and multi-threaded workloads from Python environments; mixed workload files (`-workload`); live progress streaming (`-stream-json`); periodic query-statistic snapshots (`-querystats-interval`); comparing driver behavior between native ODBC (sqlsim) and `mssql-python`; producing sqlpysim JSON for automation. DO NOT USE FOR — sqlsim-only replay modes; setting an application name (`-app`, which the driver reserves); exact cross-tool JSON compatibility; or performance comparisons that require the lowest possible client overhead (use sqlsim instead).","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fsqlsimtools\u002Fblob\u002Fmain\u002Fplugins\u002Fsqlpysim\u002Fskills\u002Fsqlpysim\u002FSKILL.md",[93],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[34,95,96,97,86,9,98,33,35],"workload","python","performance","odbc",{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":36},"01M69A0Z2MZFK5ZCG4GK080290","sqlsimtools-release","Build, package, validate, and publish sqlsimtools release assets. USE WHEN: running a release candidate dry run, cutting a version, tagging a release, publishing a draft GitHub Release, verifying archive contents, diagnosing a failed release workflow, or changing any publish script. DO NOT USE FOR: running sqlsim or sqlpysim workloads (use the sqlsim or sqlpysim skills), or day-to-day source edits.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fsqlsimtools\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fsqlsimtools-release\u002FSKILL.md",[],[106,107,35,108,109,34],"sqlsimtools release","validate","github","workflow",{"skillNo":111,"name":112,"nameZh":6,"description":113,"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":118,"publishedAt":36},"01M69A0WDK5Y07WSVWSTVR57S1","sqlsimtools-project-stats","Source-repository-only maintainer report of current sqlsimtools project numbers: release download counts per file, GitHub Pages website status and click-throughs, 14-day repository views, clones, referrers, and popular pages, plus stars, forks, and watchers. USE WHEN: a maintainer asks for project stats, download numbers, how many people downloaded a release, website or repository traffic, referrers, or how usage changed since earlier numbers. DO NOT USE FOR: tool run telemetry (sqlsimtools collects none), Google Search Console or Bing Webmaster Tools data (view those in their portals), or running SQL workloads (use the sqlsim, sqlpysim, or sqlsimstudio skills).","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fsqlsimtools\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fsqlsimtools-project-stats\u002FSKILL.md",[116,117],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":74,"categoryName":75,"taxonomyType":76,"taxonomyTypeDesc":77},[119,120,108,121,122,33,34,35,123],"sqlsimtools project stats","google","status","telemetry","sqlsimstudio",{"skillNo":125,"name":123,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":130,"publishedAt":36},"01M69A0QE6KTSWZM4XQW716XN4","Use when a user wants to install, launch, configure, authenticate, run, monitor, compare, or troubleshoot released sqlsim Studio, including the Windows package, browser bootstrap, sqlsim or sqlpysim workloads, JSON results, Query Store statistics, cancellation, saved configurations, themes, or A\u002FB comparisons. DO NOT USE FOR: source builds, CI, repository manual acceptance testing, or repository load-test tier recording.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fsqlsimtools\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fsqlsimstudio\u002FSKILL.md",[129],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[123,83,131,30,132,32,133,34,35],"troubleshoot","launch","query store",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":144,"publishedAt":36},"01M69A0M6QRPH9HFNHMMNRWZ8H","sqlsimstudio-manual-test","Source-repository-only guided sqlsim Studio manual acceptance test. Use when a contributor asks to start or resume the repository MANUAL-TEST.md checklist, verify a release candidate built from this checkout, record GUI evidence, diagnose acceptance failures, or produce a session report. DO NOT USE FOR: ordinary use of an installed\u002Freleased Studio package, Studio workload execution, tiered load tests (use sqlsimstudio-load-test), or general Studio configuration help (use sqlsimstudio).","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fsqlsimtools\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fsqlsimstudio-manual-test\u002FSKILL.md",[140,141],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":142,"categoryName":143,"taxonomyType":76,"taxonomyTypeDesc":77},"01JBSEEDCAT000000000000038","人力资源",[30,145,121,95,35],"sqlsimstudio manual test"]