New Event Source
aws/aws-lambda-dotnet
Add a new AWS event source attribute (e.g., Kinesis, Kafka, MQ) to the Lambda .NET Annotations framework, including the attribute class, source generator integration, CloudFormation writer, unit…
MUST USE when an existing .NET test project was excluded from a .slnf/CI solution filter, disappeared from .sln/.slnx discovery, or lost its production ProjectReference; also for requests to set up…
Install Scaffold Dotnet Test Project
$ npx skills add dotnet/skills --skill scaffold-dotnet-test-project -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install dotnet/skills scaffold-dotnet-test-project --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/dotnet/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/dotnet-test/skills/scaffold-dotnet-test-project .claude/skills/scaffold-dotnet-test-project && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "scaffold-dotnet-test-project" agent skill from https://github.com/dotnet/skills/tree/main/plugins/dotnet-test/skills/scaffold-dotnet-test-project into .claude/skills/scaffold-dotnet-test-project/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scaffold-dotnet-test-project", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/dotnet/skills/tree/main/plugins/dotnet-test/skills/scaffold-dotnet-test-projectType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add dotnet/skills --skill scaffold-dotnet-test-project -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install dotnet/skills scaffold-dotnet-test-project --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dotnet/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/dotnet-test/skills/scaffold-dotnet-test-project .agents/skills/scaffold-dotnet-test-project && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "scaffold-dotnet-test-project" agent skill from https://github.com/dotnet/skills/tree/main/plugins/dotnet-test/skills/scaffold-dotnet-test-project into .agents/skills/scaffold-dotnet-test-project/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scaffold-dotnet-test-project", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add dotnet/skills --skill scaffold-dotnet-test-project -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install dotnet/skills scaffold-dotnet-test-project --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dotnet/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/dotnet-test/skills/scaffold-dotnet-test-project .cursor/skills/scaffold-dotnet-test-project && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "scaffold-dotnet-test-project" agent skill from https://github.com/dotnet/skills/tree/main/plugins/dotnet-test/skills/scaffold-dotnet-test-project into .cursor/skills/scaffold-dotnet-test-project/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scaffold-dotnet-test-project", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/dotnet/skills.git --path plugins/dotnet-test/skills/scaffold-dotnet-test-project--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add dotnet/skills --skill scaffold-dotnet-test-project -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install dotnet/skills scaffold-dotnet-test-project --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dotnet/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/dotnet-test/skills/scaffold-dotnet-test-project .gemini/skills/scaffold-dotnet-test-project && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "scaffold-dotnet-test-project" agent skill from https://github.com/dotnet/skills/tree/main/plugins/dotnet-test/skills/scaffold-dotnet-test-project into .gemini/skills/scaffold-dotnet-test-project/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scaffold-dotnet-test-project", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install dotnet/skills scaffold-dotnet-test-projectInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add dotnet/skills --skill scaffold-dotnet-test-project -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/dotnet/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/dotnet-test/skills/scaffold-dotnet-test-project .github/skills/scaffold-dotnet-test-project && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "scaffold-dotnet-test-project" agent skill from https://github.com/dotnet/skills/tree/main/plugins/dotnet-test/skills/scaffold-dotnet-test-project into .github/skills/scaffold-dotnet-test-project/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scaffold-dotnet-test-project", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add dotnet/skills --skill scaffold-dotnet-test-project -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install dotnet/skills scaffold-dotnet-test-project --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dotnet/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/dotnet-test/skills/scaffold-dotnet-test-project .opencode/skills/scaffold-dotnet-test-project && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "scaffold-dotnet-test-project" agent skill from https://github.com/dotnet/skills/tree/main/plugins/dotnet-test/skills/scaffold-dotnet-test-project into .opencode/skills/scaffold-dotnet-test-project/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scaffold-dotnet-test-project", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
scaffold-dotnet-test-project- GitHub stars
- 5.6k
- Used in
- 1 other repo
- Token cost
- ~2.8k tokens
- SKILL.md length
- 1,468 words
- Files
- 1
- Skills in repo
- 91
- Repo updated
- First seen
- Licence
- MIT
At a glance
MUST USE when an existing .NET test project was excluded from a .slnf/CI solution filter, disappeared from .sln/.slnx discovery, or lost its production ProjectReference; also for requests to set up…
- Works in 5 steps: Establish the repository contract → Create only when the project is absent → Repair only the missing edge when the… → …
- An existing .NET test project was excluded from a .slnf/CI solution filter
- SKILL.md covers Repository overlay, Route the Request, Workflow and Output, plus 1 more section
- Calls dotnet
What it does
Scaffold Dotnet Test Project is an agent skill from dotnet/skills, published by the product's own GitHub organization. MUST USE when an existing .NET test project was excluded from a .slnf/CI solution filter, disappeared from .sln/.slnx discovery, or lost its production ProjectReference; also for requests to set up, create, reuse, add, register, include, or repair a test project. Handles "tests pass directly but CI discovers zero", exact solution wiring, xUnit/NUnit/MSTest, and central packages. DO NOT USE to only author tests in an already-wired project (code-testing-agent), run tests, migrate, or correct MSTest…
Its SKILL.md is about 2.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Testing & QA, covering Unit testing. It works with .NET. The repository describes itself as: Repository for skills to assist AI coding agents with .NET and C. The licence is MIT.
When your agent uses it
- An existing .NET test project was excluded from a .slnf/CI solution filter
- Disappeared from .sln/.slnx discovery
- Lost its production ProjectReference
- Also for requests to set up
Example prompts
- “tests pass directly but CI discovers zero”
- “/scaffold-dotnet-test-project”
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit a660de8. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
dotnet
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Scaffold Dotnet Test Project loads about 2.8k tokens when it runs. Until then it costs about 153 tokens; SKILL.md has 1,468 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from dotnet/skills at commit a660de8, republished under its MIT licence (© dotnet). 1,468 words, ~2,828 tokens.
Download SKILL.mdSave it as
.claude/skills/scaffold-dotnet-test-project/SKILL.md (or your agent's skills folder).- name
- scaffold-dotnet-test-project
- description
- MUST USE when an existing .NET test project was excluded from a .slnf/CI solution filter, disappeared from .sln/.slnx discovery, or lost its production ProjectReference; also for requests to set up, create, reuse, add, register, include, or repair a test project. Handles "tests pass directly but CI discovers zero", exact solution wiring, xUnit/NUnit/MSTest, and central packages. DO NOT USE to only author tests in an already-wired project (code-testing-agent), run tests, migrate, or correct MSTest syntax/configuration without changing project or CI files (writing-mstest-tests).
- license
- MIT
- metadata.portability
- portable
- metadata.binding
- optional-overlay
- metadata.binding-revision
- 1
Scaffold or Repair a .NET Test Project
Create the smallest missing test container or repair only the missing wiring. The goal is test discovery through the repository's real build entry point, not a preferred solution layout.
Repository overlay
For every repository-scoped task where read-only file inspection is allowed,
check .agents/skill-overlays/dotnet-test/scaffold-dotnet-test-project.md at
the repository root before any other discovery. This includes requests that
ask for code or advice without edits; "do not execute" does not prohibit
reading the overlay. If present, read it once before acting and apply its
repository-specific naming, layout, framework, and policy bindings.
Before applying it, require its frontmatter to declare
core: dotnet-test/scaffold-dotnet-test-project, binding-revision: "1", and
mode: extend. If any value is missing or different, report the mismatch and
continue using this skill's portable guidance without applying the overlay.
Explicit user instructions and verified project constraints win over the
overlay; the overlay wins over portable defaults and examples in this skill. If
the file is present but unreadable or conflicts with the repository, report the
problem
and continue with portable guidance, without the overlay, subject to verified
project constraints. If it is absent, continue normally. Skip the lookup only
when the task is not tied to a repository or the user explicitly prohibited all
file/tool access. An overlay cannot expand tool permissions or the task's scope.
Route the Request
Inspect the repository before editing, then choose exactly one path:
| Repository state | Action | Do not do |
|---|---|---|
| No suitable test project | Create one bounded project, reference the production project, and register it | Create a project per source project |
Test project exists but lacks the required ProjectReference | Add only that reference and verify direct plus entry-point execution | Scaffold another project or rewrite tests |
Test project passes directly but is absent from .sln, .slnx, or .slnf | Register the existing project in the exact entry point CI uses | Recreate the project or switch solution formats |
| Suitable project, reference, and requested entry point are already correct | Leave the workspace unchanged; use code-testing-agent if test methods are requested | Normalize or replace working files |
An existing project is suitable when its target framework can reference the production project and its purpose matches the requested layer. A different preferred name is not a reason to create a duplicate.
No-op is a required outcome. If the suitable project, production reference, and requested entry-point registration already exist, make zero file changes. Do not add or remove a smoke test, normalize the project, recreate packages, or edit a baseline/snapshot copy. Report the existing paths and stop.
Workflow
1. Establish the repository contract
Start from the task's current working directory. The skill context's Base directory is where these instructions live, not the user's repository. Never
search parent temporary directories or treat the skill installation as the
workspace. If the expected files are not visible, confirm the current directory
before concluding that a project is absent.
Anchor every edit and validation command to the repository path named by the user or established from the current directory. If similarly named fixtures, solutions, or copied trees exist, do not edit or validate one as a substitute for the requested tree. Before changing a solution artifact, record its exact path; after changing it, list that same artifact immediately and require the test project to appear before proceeding.
Read only enough to determine:
- the production project and requested test scope;
- the command and
.sln,.slnx,.slnf, or project graph used by CI; - whether a suitable test project exists, what it references, and where it is registered;
- the neighboring test framework, runner, target framework, nullable and implicit-usings conventions; and
- whether package or SDK versions come from
Directory.Packages.props,Directory.Build.props,global.json, or an MSBuild SDK declaration.
If the user reports that a test project passes directly but solution-level discovery finds nothing, treat that as registration evidence. Inspect the entry point before considering project creation.
2. Create only when the project is absent
Choose one test project for the narrowest requested production project. Follow, in order, the user's explicit framework choice, neighboring test projects, repository-wide package/SDK conventions, then a standard SDK template.
Use a dotnet new template only when its generated framework generation and
package style match the repository contract. Inspect template availability
before creation. In particular, generic dotnet new xunit commonly emits xUnit
2 packages; for a centrally managed xunit.v3 repository, use a repository or
installed xUnit v3 template, or create the minimal SDK project directly. Never
generate versioned xUnit 2 references and then rewrite them into xUnit v3.
Then:
- align target framework, nullable, implicit usings, runner, and package style;
- use
dotnet add <test-project> reference <production-project>for only the production projects exercised by the requested tests; - delete template sample files such as
UnitTest1.cs, then create a behavior-named test file rather than repurposing the template filename; and - omit package versions when central package management supplies them.
For xUnit v3 projects that run through dotnet test, preserve or add:
<OutputType>Exe</OutputType>
<TestingPlatformDotnetTestSupport>true</TestingPlatformDotnetTestSupport>OutputType=Exe alone proves only the self-hosted runner path, not discovery by
the repository's dotnet test command.
Show full SKILL.md (635 more words)Show less
3. Repair only the missing edge when the project exists
- Missing production reference: use
dotnet add <test-project> reference <production-project>, inspect the resulting project, and leave every other project element plus all test source files unchanged. Compare the project before and after so the addedProjectReferenceis the only semantic change. - Missing
.slnor.slnxregistration: rundotnet sln <entry-point> add <test-project>, then immediately rundotnet sln <entry-point> listagainst that exact path. If the project is absent, the repair has not happened; do not validate a sibling solution or report success. - Missing
.slnfregistration: add the existing project to its underlying solution if necessary, then include that same project path in the filter. If the underlying solution already contains it, edit only the filter. - Multiple solution artifacts: modify only the one named by the user or invoked by CI. Do not substitute an easier format.
- No solution artifact: preserve the existing project-oriented workflow. Do not create a solution for aesthetics.
4. Add only the requested smoke behavior
For a newly created project, replace template examples with the smallest smoke suite the user requested. Each test must invoke a real production symbol and assert a concrete deterministic result without network, wall-clock, process, or real-filesystem dependencies.
For an existing-project wiring repair, do not add, rewrite, rename, or expand tests unless the user explicitly asks for test behavior changes. Registration and test authoring are separate operations.
5. Verify the repaired path
Run the narrowest commands that prove the chosen route:
| Route | Required evidence |
|---|---|
| Newly created project | dotnet test <test-project>, the exact entry-point command CI uses, and registration listing. If the entry point is a .slnf/.slnx containing tests, run dotnet test on that artifact rather than proving only that it builds. |
| Missing reference | Targeted project test plus the exact solution/root test command requested |
Missing .sln/.slnx registration | Listing and dotnet test for that exact artifact; never use another solution as a fallback |
Missing .slnf entry | Inspect the filter entry and run the exact CI filter build command; do not prepend a deliberately failing alternate command |
| Already correct/no-op | Structural inspection of the existing reference and registration. Unless execution was requested, do not run tests merely to prove a no-op because that creates bin/obj and weakens byte-for-byte cleanliness evidence. |
Inspect the repository's command before adding switches. Do not prepend a
speculative --no-restore attempt or hide alternatives in command-a || command-b; run the configured entry-point command whose clean exit is the
evidence.
For every wiring repair, invoke the exact validation command directly and preserve its exit status. Reading generated files, a grader script, or a later build is not a substitute for observing that command complete successfully.
Before reporting completion, inspect the final changed-file set. Remove only
bin/obj or equivalent build artifacts created by this task when they were
absent beforehand and are not intentionally tracked; never remove pre-existing
artifacts. Preserve the passing command's complete result so the handoff can
state the exact entry point and discovered test count.
For a no-op, inspect rather than rewrite and report the existing paths. A green
dotnet build is not test-discovery evidence. If validation is blocked, report
the exact failing command and first actionable error; never describe an unrun or
failed command as successful.
Output
Keep the handoff proportional to the change:
| Requirement | Evidence |
|---|---|
| Project created, reused, or repaired | Test project path and chosen route |
| Production reference | Referenced .csproj, or why no change was needed |
| Build registration | Exact .sln/.slnx/.slnf entry or project workflow |
| Test discovery | Passing harness-level command and discovered test |
Completion Checks
- Existing projects were checked before creation.
- Only the requested production scope is referenced and tested.
- Framework, runner, target framework, and central package conventions remain intact.
- Template samples are removed from a newly created project.
- Existing test code is untouched for a wiring-only repair.
- The exact repository entry point discovers and runs the test project.
© dotnet, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in plugins/dotnet-test/skills/scaffold-dotnet-test-project of dotnet/skills.
Open the folder on GitHubat commit a660de8
Used in 1 other repository
We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in dotnet/skills, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Scaffold Dotnet Test Project next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Scaffold Dotnet Test Project this skilldotnet/skills | 5.6k | 1 repos | ~2.8k | Automated safety check: Pass | MIT | |
| New Event Sourceaws/aws-lambda-dotnet | 1.7k | — | ~3k | Automated safety check: Pass | Apache-2.0 | |
| ScottPlot Test RunnerScottPlot/ScottPlot | 6.8k | — | ~308 | Automated safety check: Pass | MIT | |
| Aspire Integration TestingDevBetterCom/DevBetterWeb | 157 | 2 repos | ~2.3k | Automated safety check: Pass | None | |
| Vstest Build Testmicrosoft/vstest | 969 | — | ~1.9k | Automated safety check: Pass | MIT | |
| Coverage Analysisrunceel/ReactiveProperty | 944 | — | ~5.9k | Automated safety check: Warn | MIT |
Similar skills
- Official
ScottPlot Test Runner
ScottPlot/ScottPlot
Run or add ScottPlot 5 tests. Use for unit-test and cookbook-test work; unless explicitly asked otherwise, restrict manual test execution to the Unit Tests…
Aspire Integration Testing
DevBetterCom/DevBetterWeb
Write integration tests using .NET Aspire's testing facilities with xUnit.
- Official
Vstest Build Test
microsoft/vstest
Build, test, and validate changes in the vstest repository. An agent skill from microsoft/vstest.
Coverage Analysis
runceel/ReactiveProperty
Automated, project-wide code coverage and CRAP (Change Risk Anti-Patterns) score analysis for .NET projects with existing unit tests.
Unit Testing
OpenCoreMMO/OpenCoreMMO
Write, fix, or review NeoServer unit tests using xUnit and FluentAssertions.
More from dotnet/skills
All 91 skills in this repo- Official
Apple Crash Log .NET Symbolication
dotnet/skills
Resolves .NET runtime frames in Apple .ips crash logs to function names, source files and line numbers using dSYM symbols, atos and the Microsoft symbol server.
- Official
Android Tombstone Symbolication
dotnet/skills
Resolves native crash frames from .NET Android tombstones to function names, source files and line numbers using BuildIds, Microsoft's symbol server and llvm-symbolizer.
- Official
Analyzing .NET Performance
dotnet/skills
Scans C# and .NET code for about 50 performance anti-patterns and reports prioritized findings with concrete fixes, at a scan depth you choose.
- Official
Find Untested Sources
dotnet/skills
Statically pairs source files with test files to list code that no test references, using Roslyn for C# or tree-sitter for many languages, with no build.
- Official
Microbenchmarking
dotnet/skills
Activate this skill when BenchmarkDotNet (BDN) is involved in the task — creating, running, configuring, or reviewing BDN benchmarks.
- Official
.NET Native AOT Compatibility
dotnet/skills
Makes .NET projects compatible with Native AOT and trimming by resolving IL trim and AOT analyzer warnings through annotations rather than suppressions.
Related
Works with
Categories
Questions about Scaffold Dotnet Test Project
What does Scaffold Dotnet Test Project do?
MUST USE when an existing .NET test project was excluded from a .slnf/CI solution filter, disappeared from .sln/.slnx discovery, or lost its production ProjectReference; also for requests to set up…. Scaffold Dotnet Test Project is an agent skill from dotnet/skills, published by the product's own GitHub organization.slnx discovery, or lost its production ProjectReference; also for requests to set up, create, reuse, add, register, include, or repair a test project.
When should I use Scaffold Dotnet Test Project?
Scaffold Dotnet Test Project fits situations like: an existing .NET test project was excluded from a .slnf/CI solution filter; disappeared from .sln/.slnx discovery; lost its production ProjectReference; also for requests to set up.
How do I install Scaffold Dotnet Test Project in Claude Code?
Run `npx skills add dotnet/skills --skill scaffold-dotnet-test-project -a claude-code`. Or copy the skill folder (plugins/dotnet-test/skills/scaffold-dotnet-test-project in dotnet/skills) into .claude/skills/scaffold-dotnet-test-project in your project. Claude Code loads it when a task matches its description.
How do I install Scaffold Dotnet Test Project in Codex?
Run `npx skills add dotnet/skills --skill scaffold-dotnet-test-project -a codex`. Or copy the skill folder (plugins/dotnet-test/skills/scaffold-dotnet-test-project in dotnet/skills) into .agents/skills/scaffold-dotnet-test-project in your project. Codex loads it when a task matches its description.
Can I use Scaffold Dotnet Test Project in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add dotnet/skills --skill scaffold-dotnet-test-project -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/scaffold-dotnet-test-project, .gemini/skills/scaffold-dotnet-test-project, .github/skills/scaffold-dotnet-test-project and .opencode/skills/scaffold-dotnet-test-project in your project.
What does Scaffold Dotnet Test Project need to run?
Going by SKILL.md and its folder, Scaffold Dotnet Test Project needs the command-line tools its instructions call (dotnet).
Does Scaffold Dotnet Test Project access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Scaffold Dotnet Test Project safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Scaffold Dotnet Test Project use?
Scaffold Dotnet Test Project is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Scaffold Dotnet Test Project use?
About 2.8k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Scaffold Dotnet Test Project?
Skills that share tags, products or a category with Scaffold Dotnet Test Project: New Event Source (aws/aws-lambda-dotnet, 1.7k stars), ScottPlot Test Runner (ScottPlot/ScottPlot, 6.8k stars), Aspire Integration Testing (DevBetterCom/DevBetterWeb, 157 stars) and Vstest Build Test (microsoft/vstest, 969 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Scaffold Dotnet Test Project?
dotnet (a GitHub organization, an official publisher) maintains it in dotnet/skills, which has 5,576 GitHub stars. The repository holds 91 skills in this directory. The repository was last updated on October 8, 2026.
Source: dotnet/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.