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).
- License 许可
- MIT
- 最近更新
- 2026-10-21
- Stars
- ★ 47
- Forks
- 4
01 前言 Front Matter
- name
- sqlsimtools-project-stats
- description
- 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).
- argument-hint
- Optional: earlier numbers or a date to compare against
02 资源文件 4
- 参考文档references/fix-policy.md982 B
- 参考文档references/github-pr-delivery.md2.2 KB
- 参考文档references/report-format.md1.3 KB
- 参考文档references/rubric.md1.8 KB
03 SKILL.md 正文
sqlsimtools project stats
Reports the latest public-interest numbers for microsoft/sqlsimtools by
running the repository script scripts/get-project-stats.ps1. The report is
read-only; never change repository settings, files, or releases while using
this skill.
Procedure
-
From the repository root, run the script with JSON output and capture it in a variable. Do not add shell redirects or pipes to the command itself.
$stats = .\scripts\get-project-stats.ps1 -Json | ConvertFrom-JsonIf it fails because the GitHub CLI is missing or signed out, tell the user to install it from https://cli.github.com/ or run
gh auth login, then stop. -
Summarize for the user, in this order:
- Downloads:
downloads.total, then each release indownloads.releaseswith its files sorted bydownloads, highest first. - Website:
website.statusforwebsite.url, andwebsite.clickThroughs(website.uniqueClickThroughsunique) from the site into GitHub over the last 14 days. - Repository traffic (last 14 days):
traffic.views,traffic.clones, the toptraffic.referrers, and the toptraffic.pages. Mention any notable day intraffic.dailyViews. - Repository: stars, forks, watchers, and open issues and pull requests
from
repositoryCounts.
- Downloads:
-
If the user supplied earlier numbers or asked about change over time, report the difference for each comparable value. Compare download totals per file, not only the grand total.
Interpreting the numbers
State these caveats when they affect the answer:
- Download counts are running totals since each file was uploaded. GitHub keeps no daily history, and the automatic "Source code" archives are not counted. The maintainers' own test downloads are included.
- Traffic covers only the last 14 days. Unique visitors cannot be added across days or periods.
- Clones include CI checkouts, so they overstate real users.
- GitHub provides no visitor analytics for the Pages site. Click-throughs count
only visitors who followed a link from the site into GitHub. For search
impressions and clicks, point the user to Google Search Console and Bing
Webmaster Tools (URLs in
website). - If
trafficis null andtrafficErroris set, the signed-in account lacks push access. Report downloads and repository counts, and explain that traffic and click-throughs need a maintainer account.
Formatted report
When the user wants the full console report instead of a summary, run:
.\scripts\get-project-stats.ps1
04 同仓库更多 Skills
sqlsim
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 / load testing with N threads × R iterations; measuring connection / login / 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 / data loading (sqlsim runs queries; it does not generate schemas).
sqlpysim
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).
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.
sqlsimtools-build
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).
sqlsimstudio
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/B comparisons. DO NOT USE FOR: source builds, CI, repository manual acceptance testing, or repository load-test tier recording.
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/released Studio package, Studio workload execution, tiered load tests (use sqlsimstudio-load-test), or general Studio configuration help (use sqlsimstudio).