Test Tagging skill: what it does and how to install it
Classifies existing tests in .NET and other frameworks, applies standard traits, and reports the suite's positive, negative and integration mix.
Summary generated from the skill's documentation.
Install
$ npx skills add dotnet/skills --skill test-taggingRun it in a terminal. If your agent is already running, start a new session so it picks the skill up.
About this skill
What it does. Classifies each existing test by positive or negative behaviour and additive traits such as boundary, integration, security and performance. It scans names, assertions, inputs and setup, preserves existing tags, then either applies framework-specific attributes or produces a per-test mapping and non-zero distribution summary. Edit mode validates .NET changes with dotnet build and test discovery.
When to use it. Use for auditing or tagging an existing test suite and reviewing its coverage shape. Do not use it for writing or running tests, framework migrations, coverage or quality audits, or behavioural gap analysis; report-only frameworks are not edited.
History
Repo stars
5.5kAbout +384 since 9 Jul 2026
Before 1 Oct 2026 the curve is estimated from public event data.
Stars are counted for the whole repository, which holds 18 skills.
Show as a table
| Date | Repo stars |
|---|---|
| 1 Oct 2026 | 5,531 |
| 24 Sept 2026 (estimated) | 5,519 |
| 17 Sept 2026 (estimated) | 5,494 |
| 10 Sept 2026 (estimated) | 5,419 |
| 3 Sept 2026 (estimated) | 5,258 |
| 27 Aug 2026 (estimated) | 5,233 |
| 20 Aug 2026 (estimated) | 5,221 |
| 13 Aug 2026 (estimated) | 5,221 |
| 6 Aug 2026 (estimated) | 5,171 |
| 30 Jul 2026 (estimated) | 5,159 |
| 23 Jul 2026 (estimated) | 5,159 |
| 16 Jul 2026 (estimated) | 5,147 |
| 9 Jul 2026 (estimated) | 5,147 |
Installs
2.3k
Tracking since . A chart appears once there are 7 days of data.
Installs via skills.sh
Similar skills
- Skill CreatorCreates new skills, improves existing ones and measures how well they perform with evals and benchmarks.
- Finishing a Development BranchGuides the choice of how to integrate finished work once tests pass: merge, pull request or cleanup.
- Systematic DebuggingMakes the agent find the root cause of a bug, test failure or unexpected behaviour before it proposes a fix.