Link Workspace Packages
nomcopter/react-mosaic
Link workspace packages in monorepos (npm, yarn, pnpm, bun).
Validate and fix two-slash TypeScript examples for aspire.dev.
OfficialMITAuto-check passed
Install Twoslash Validator
$ npx skills add microsoft/aspire.dev --skill twoslash-validator -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install microsoft/aspire.dev twoslash-validator --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/microsoft/aspire.dev.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/twoslash-validator .claude/skills/twoslash-validator && 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 "twoslash-validator" agent skill from https://github.com/microsoft/aspire.dev/tree/main/.agents/skills/twoslash-validator into .claude/skills/twoslash-validator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "twoslash-validator", 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/microsoft/aspire.dev/tree/main/.agents/skills/twoslash-validatorType 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 microsoft/aspire.dev --skill twoslash-validator -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install microsoft/aspire.dev twoslash-validator --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/microsoft/aspire.dev.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/twoslash-validator .agents/skills/twoslash-validator && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "twoslash-validator" agent skill from https://github.com/microsoft/aspire.dev/tree/main/.agents/skills/twoslash-validator into .agents/skills/twoslash-validator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "twoslash-validator", 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 microsoft/aspire.dev --skill twoslash-validator -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install microsoft/aspire.dev twoslash-validator --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/microsoft/aspire.dev.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/twoslash-validator .cursor/skills/twoslash-validator && 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 "twoslash-validator" agent skill from https://github.com/microsoft/aspire.dev/tree/main/.agents/skills/twoslash-validator into .cursor/skills/twoslash-validator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "twoslash-validator", 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/microsoft/aspire.dev.git --path .agents/skills/twoslash-validator--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 microsoft/aspire.dev --skill twoslash-validator -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install microsoft/aspire.dev twoslash-validator --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/microsoft/aspire.dev.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/twoslash-validator .gemini/skills/twoslash-validator && 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 "twoslash-validator" agent skill from https://github.com/microsoft/aspire.dev/tree/main/.agents/skills/twoslash-validator into .gemini/skills/twoslash-validator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "twoslash-validator", 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 microsoft/aspire.dev twoslash-validatorInstalls 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 microsoft/aspire.dev --skill twoslash-validator -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/microsoft/aspire.dev.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/twoslash-validator .github/skills/twoslash-validator && 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 "twoslash-validator" agent skill from https://github.com/microsoft/aspire.dev/tree/main/.agents/skills/twoslash-validator into .github/skills/twoslash-validator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "twoslash-validator", 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 microsoft/aspire.dev --skill twoslash-validator -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install microsoft/aspire.dev twoslash-validator --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/microsoft/aspire.dev.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/twoslash-validator .opencode/skills/twoslash-validator && 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 "twoslash-validator" agent skill from https://github.com/microsoft/aspire.dev/tree/main/.agents/skills/twoslash-validator into .opencode/skills/twoslash-validator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "twoslash-validator", 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
twoslash-validator- GitHub stars
- 196
- Token cost
- ~856 tokens
- SKILL.md length
- 388 words
- Files
- 1
- Skills in repo
- 8
- Repo updated
- First seen
- Licence
- MIT
At a glance
Validate and fix two-slash TypeScript examples for aspire.dev.
- Works in 4 steps: Ensure dependencies are installed → If TypeScript API JSON changed,… → Run the two-slash block gate → …
- Editing twoslash code fences
- SKILL.md covers When to use this skill, Core rule, Validation workflow and Fix strategy, plus 2 more sections
- Calls pnpm
What it does
Twoslash Validator is an agent skill from microsoft/aspire.dev, published by the product's own GitHub organization. Validate and fix two-slash TypeScript examples for aspire.dev. Use when adding or editing twoslash code fences, TypeScript AppHost samples, generated TypeScript API data, or failures from pnpm test:unit:twoslash-blocks.
Its SKILL.md is about 860 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It works with TypeScript and pnpm. The repository describes itself as: The official website for all things aspire.dev. The licence is MIT.
When your agent uses it
- Editing twoslash code fences
- TypeScript AppHost samples
- Generated TypeScript API data
- Failures from pnpm test:unit:twoslash-blocks
Example prompts
- “/twoslash-validator”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Ensure dependencies are installed
- If TypeScript API JSON changed, regenerate the two-slash declaration bundle
- Run the two-slash block gate
- If the test fails, read every reported file, line, block number, and ts(...) code. Fix every diagnostic before considering the work…
What it can do on your machine
Read from SKILL.md and the folder at commit a097c7e. 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:
pnpm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use pnpm, which can reach the network depending on how they are called.
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
Twoslash Validator loads about 856 tokens when it runs. Until then it costs about 61 tokens; SKILL.md has 388 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 microsoft/aspire.dev at commit a097c7e, republished under its MIT licence (© microsoft). 388 words, ~856 tokens.
Download SKILL.mdSave it as
.claude/skills/twoslash-validator/SKILL.md (or your agent's skills folder).- name
- twoslash-validator
- description
- Validate and fix two-slash TypeScript examples for aspire.dev. Use when adding or editing `twoslash` code fences, TypeScript AppHost samples, generated TypeScript API data, or failures from `pnpm test:unit:twoslash-blocks`.
Two-slash Validator Skill
Use this skill to keep aspire.dev from shipping rendered two-slash error UI. Any TypeScript diagnostic in a twoslash code block renders an error box on the site, so diagnostics must be fixed rather than suppressed.
When to use this skill
- Adding or editing a TypeScript code fence with the
twoslashmeta flag - Updating TypeScript AppHost examples that import
'./.aspire/modules/aspire.mjs' - Refreshing
src/frontend/src/data/ts-modules/orsrc/frontend/src/data/twoslash/aspire.d.ts - Investigating failures from
pnpm test:unit:twoslash-blocks - Reviewing docs changes that affect TypeScript sample rendering
Core rule
Do not add diagnostic allowlists or suppressions. A two-slash diagnostic is user-visible output on aspire.dev. Fix the docs sample, fix/regenerate the generated type surface, or remove the twoslash meta until the sample compiles cleanly.
Validation workflow
Run commands from the repository root unless noted.
Ensure dependencies are installed:
powershell Set-Location -Path .\src\frontend pnpm install --frozen-lockfile --prefer-offlineIf TypeScript API JSON changed, regenerate the two-slash declaration bundle:
powershell pnpm twoslash-typesRun the two-slash block gate:
powershell pnpm test:unit:twoslash-blocksIf the test fails, read every reported file, line, block number, and
ts(...)code. Fix every diagnostic before considering the work complete.
Show full SKILL.md (218 more words)Show less
Fix strategy
Use this order when deciding what to change:
- Docs sample bug: If the TypeScript snippet calls the wrong API, uses the wrong argument shape, has a stale model name, or chains incompatible resources, fix the MDX sample.
- Generated type data stale: If the sample matches the product API but
src/frontend/src/data/twoslash/aspire.d.tsis stale, runpnpm twoslash-typesand commit the regenerated bundle. - Generator type-shape gap: If regeneration is not enough because
scripts/generate-twoslash-types.tsloses valid SDK shape, fix the generator and regenerateaspire.d.ts. - Feature not representable yet: If a correct sample cannot be represented by the current two-slash type data, remove the
twoslashmeta from that block and leave the code sample visible without two-slash rendering. Do not leave a rendered diagnostic.
What not to do
- Do not reintroduce
KNOWN_TYPE_BUGS, per-page diagnostic budgets, or equivalent allowlists. - Do not disable
TWOSLASH_ENABLEDto make the test pass. - Do not change
noErrorValidationas a substitute for fixing diagnostics; it exists so the audit can collect all failures at once. - Do not hide failures by changing the fence language away from TypeScript unless the sample is not TypeScript.
- Do not edit generated
aspire.d.tsby hand; update the generator or source JSON and regenerate.
Expected final checks
Before finishing a two-slash-related change, run:
Set-Location -Path .\src\frontend
pnpm test:unit:twoslash-blocksIf you changed the generator, also run:
pnpm test:unit:twoslash-types© microsoft, 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 .agents/skills/twoslash-validator of microsoft/aspire.dev.
Open the folder on GitHubat commit a097c7e
Compare with similar skills
Twoslash Validator 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 |
|---|---|---|---|---|---|---|
| Twoslash Validator this skillmicrosoft/aspire.dev | 196 | — | ~856 | Automated safety check: Pass | MIT | |
| Link Workspace Packagesnomcopter/react-mosaic | 4.8k | 5 repos | ~760 | Automated safety check: Pass | Custom licence | |
| Pnpm Engineteambit/bit | 18k | — | ~1.9k | Automated safety check: Pass | Custom licence | |
| Create Docsvictorgarciaesgi/nuxt-typed-router | 413 | 2 repos | ~2.8k | Automated safety check: Pass | MIT | |
| Testing Changespnpm/pnpm | 37k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Windows Releasemilind-soni/OpenMausBot | 4.1k | — | ~1.5k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Pnpm Engine
teambit/bit
Work on the pnpm Rust engine (@pnpm/napi, the pacquet crates) that bit install runs through.
Create Docs
victorgarciaesgi/nuxt-typed-router
Create complete documentation sites for projects. An agent skill from victorgarciaesgi/nuxt-typed-router.
Testing Changes
pnpm/pnpm
Run the tests that cover a change in the pnpm repository, in the Rust workspace (pnpm/, pnpr/) or the TypeScript CLI (pnpm11/), and recognize the cases where a scoped run passes without testing…
Windows Release
milind-soni/OpenMausBot
Build and verify the Windows desktop build (NSIS installer + latest.yml) for the canonical OpenMausBot release and its legacy updater mirror.
evlog Adapter Creator
evloghq/evlog
Walks through adding a new built-in evlog drain adapter for an observability platform: source, build config, exports, tests, docs and PR scope.
More from microsoft/aspire.dev
All 8 skills in this repo- Official
Aspire
microsoft/aspire.dev
Orchestrates Aspire distributed applications using the Aspire CLI for running, debugging, and managing distributed apps.
- Official
Whatsnew
microsoft/aspire.dev
Step-argument skill that formalizes writing an Aspire "What's new in N.N" release-notes page (src/frontend/src/content/docs/whats-new/aspire-N-N.mdx) as a repeatable lifecycle.
- Official
Container Images
microsoft/aspire.dev
Extracts all container image references (registry, image, tag) from the microsoft/aspire source code and produces a JSON data file for the aspire.dev Astro site.
- Official
Doc Writer
microsoft/aspire.dev
Guidelines for producing accurate and maintainable documentation for the Aspire documentation site.
- Official
Update Samples
microsoft/aspire.dev
Update the samples data file by fetching sample metadata from the microsoft/aspire-samples GitHub repository.
- Official
Update Integrations
microsoft/aspire.dev
Update integration documentation links and API reference data by synchronizing NuGet package names with their documentation URLs and generating per-package API schemas.
Related
Works with
Questions about Twoslash Validator
What does Twoslash Validator do?
Validate and fix two-slash TypeScript examples for aspire.dev. dev, published by the product's own GitHub organization.dev.
When should I use Twoslash Validator?
Twoslash Validator fits situations like: editing twoslash code fences; typeScript AppHost samples; generated TypeScript API data; failures from pnpm test:unit:twoslash-blocks.
How do I install Twoslash Validator in Claude Code?
Run `npx skills add microsoft/aspire.dev --skill twoslash-validator -a claude-code`. Or copy the skill folder (.agents/skills/twoslash-validator in microsoft/aspire.dev) into .claude/skills/twoslash-validator in your project. Claude Code loads it when a task matches its description.
How do I install Twoslash Validator in Codex?
Run `npx skills add microsoft/aspire.dev --skill twoslash-validator -a codex`. Or copy the skill folder (.agents/skills/twoslash-validator in microsoft/aspire.dev) into .agents/skills/twoslash-validator in your project. Codex loads it when a task matches its description.
Can I use Twoslash Validator 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 microsoft/aspire.dev --skill twoslash-validator -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/twoslash-validator, .gemini/skills/twoslash-validator, .github/skills/twoslash-validator and .opencode/skills/twoslash-validator in your project.
What does Twoslash Validator need to run?
Going by SKILL.md and its folder, Twoslash Validator needs the command-line tools its instructions call (pnpm).
Does Twoslash Validator 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 Twoslash Validator 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 Twoslash Validator use?
Twoslash Validator is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Twoslash Validator use?
About 856 tokens (SKILL.md is roughly 3.4k 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 Twoslash Validator?
Skills that share tags, products or a category with Twoslash Validator: Link Workspace Packages (nomcopter/react-mosaic, 4.8k stars), Pnpm Engine (teambit/bit, 18k stars), Create Docs (victorgarciaesgi/nuxt-typed-router, 413 stars) and Testing Changes (pnpm/pnpm, 37k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Twoslash Validator?
microsoft (a GitHub organization, an official publisher) maintains it in microsoft/aspire.dev, which has 196 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on October 7, 2026.
Source: microsoft/aspire.dev on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.