Spfx Release
pnp/docker-spfx
Automate SPFx version releases - branch, update files, commit, open PR, then tag after merge
A skill your agent uses when: setting up shared local vscuse prerequisites, credentials, runner, local or pinned published Docker images, local VSIX, env variables, and common rules for Microsoft…
Install Local Vscuse Validation
The automated check flagged lines worth reading first. See the safety section below.
$ npx skills add OfficeDev/microsoft-365-agents-toolkit --skill local-vscuse-validation -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install OfficeDev/microsoft-365-agents-toolkit local-vscuse-validation --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/OfficeDev/microsoft-365-agents-toolkit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/local-vscuse-validation .claude/skills/local-vscuse-validation && 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 "local-vscuse-validation" agent skill from https://github.com/OfficeDev/microsoft-365-agents-toolkit/tree/dev/.github/skills/local-vscuse-validation into .claude/skills/local-vscuse-validation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "local-vscuse-validation", 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/OfficeDev/microsoft-365-agents-toolkit/tree/dev/.github/skills/local-vscuse-validationType 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 OfficeDev/microsoft-365-agents-toolkit --skill local-vscuse-validation -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install OfficeDev/microsoft-365-agents-toolkit local-vscuse-validation --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OfficeDev/microsoft-365-agents-toolkit.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/skills/local-vscuse-validation .agents/skills/local-vscuse-validation && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "local-vscuse-validation" agent skill from https://github.com/OfficeDev/microsoft-365-agents-toolkit/tree/dev/.github/skills/local-vscuse-validation into .agents/skills/local-vscuse-validation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "local-vscuse-validation", 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 OfficeDev/microsoft-365-agents-toolkit --skill local-vscuse-validation -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install OfficeDev/microsoft-365-agents-toolkit local-vscuse-validation --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OfficeDev/microsoft-365-agents-toolkit.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/skills/local-vscuse-validation .cursor/skills/local-vscuse-validation && 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 "local-vscuse-validation" agent skill from https://github.com/OfficeDev/microsoft-365-agents-toolkit/tree/dev/.github/skills/local-vscuse-validation into .cursor/skills/local-vscuse-validation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "local-vscuse-validation", 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/OfficeDev/microsoft-365-agents-toolkit.git --path .github/skills/local-vscuse-validation--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 OfficeDev/microsoft-365-agents-toolkit --skill local-vscuse-validation -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install OfficeDev/microsoft-365-agents-toolkit local-vscuse-validation --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OfficeDev/microsoft-365-agents-toolkit.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/skills/local-vscuse-validation .gemini/skills/local-vscuse-validation && 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 "local-vscuse-validation" agent skill from https://github.com/OfficeDev/microsoft-365-agents-toolkit/tree/dev/.github/skills/local-vscuse-validation into .gemini/skills/local-vscuse-validation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "local-vscuse-validation", 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 OfficeDev/microsoft-365-agents-toolkit local-vscuse-validationInstalls 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 OfficeDev/microsoft-365-agents-toolkit --skill local-vscuse-validation -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/OfficeDev/microsoft-365-agents-toolkit.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/skills/local-vscuse-validation .github/skills/local-vscuse-validation && 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 "local-vscuse-validation" agent skill from https://github.com/OfficeDev/microsoft-365-agents-toolkit/tree/dev/.github/skills/local-vscuse-validation into .github/skills/local-vscuse-validation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "local-vscuse-validation", 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 OfficeDev/microsoft-365-agents-toolkit --skill local-vscuse-validation -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install OfficeDev/microsoft-365-agents-toolkit local-vscuse-validation --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OfficeDev/microsoft-365-agents-toolkit.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/skills/local-vscuse-validation .opencode/skills/local-vscuse-validation && 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 "local-vscuse-validation" agent skill from https://github.com/OfficeDev/microsoft-365-agents-toolkit/tree/dev/.github/skills/local-vscuse-validation into .opencode/skills/local-vscuse-validation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "local-vscuse-validation", 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
local-vscuse-validation- GitHub stars
- 781
- Token cost
- ~10k tokens
- SKILL.md length
- 4,683 words
- Files
- 1
- Skills in repo
- 7
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
A skill your agent uses when: setting up shared local vscuse prerequisites, credentials, runner, local or pinned published Docker images, local VSIX, env variables, and common rules for Microsoft…
- Works in 6 steps: Start vscuse-ui with the local image,… → Confirm the non-secret container env… → Load the plan or create a new one in the… → …
- : setting up shared local vscuse prerequisites
- SKILL.md covers Skill Router, Goal, When to Use and Important Local Facts, plus 16 more sections
- Calls docker, gh and pnpm; reaches api.github.com and registry.npmjs.org; needs M365_ACCOUNT_PASSWORD
What it does
Local Vscuse Validation is an agent skill from OfficeDev/microsoft-365-agents-toolkit. Use when: setting up shared local vscuse prerequisites, credentials, runner, local or pinned published Docker images, local VSIX, env variables, and common rules for Microsoft 365 Agents Toolkit vscuse work. Use vscuse-case-diagnosis for running/fixing existing cases; use vscuse-scenario-authoring for docs/mockup-driven recording and plan generation.
Its SKILL.md is about 10k 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 Documents & Office, covering Cloud office suites and Containers. It works with Microsoft 365 and Docker. The repository describes itself as: Developer tools for building Teams apps.
When your agent uses it
- : setting up shared local vscuse prerequisites
- Pinned published Docker images
- Common rules for Microsoft 365 Agents Toolkit vscuse work
Example prompts
- “/local-vscuse-validation”
Requirements
- Python 3
- Docker
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Start vscuse-ui with the local image, required local template routing, and scenario feature flags.
- Confirm the non-secret container env before interpreting UI behavior.
- Load the plan or create a new one in the UI.
- Use noVNC plus the UI controls (Run, Continue, Next, Add Step, recording) to reach and repair the behavior.
- Clean generated JSON only after the UI change is understood.
- Run vscuse execute from a clean container as final validation.
What it can do on your machine
Read from SKILL.md and the folder at commit 5ad5e2c. 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:
dockerghpnpmnpmnode
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
api.github.comregistry.npmjs.orgpackagefeedproxy.microsoft.io
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
M365_ACCOUNT_PASSWORD
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Local Vscuse Validation loads about 10k tokens when it runs. Until then it costs about 94 tokens; SKILL.md has 4,683 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: warnings
The automated check found patterns that need a careful read before installing.
- WarningMentions a credentials file (SSH keys, cloud or package-manager tokens)SKILL.md:59
- A host-level npm registry in `.npmrc` is not inherited by the vscuse container. Set `NPM_CONFIG_REGISTRY` before start
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
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 4,683 words (~10,366 tokens).
“Use this skill to prepare and troubleshoot the shared local vscuse environment for this repository: credentials, runner access, local VSIX packaging, local or pinned published Docker image selection, env variables, noVNC/vscuse-ui service expectations, and common safety rules.”
- name
- local-vscuse-validation
- argument-hint
- Describe the feature/change and which vscuse plan or scenario to validate
Files
Just SKILL.md in .github/skills/local-vscuse-validation of OfficeDev/microsoft-365-agents-toolkit.
Open the folder on GitHubat commit 5ad5e2c
Compare with similar skills
Local Vscuse Validation 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 |
|---|---|---|---|---|---|---|
| Local Vscuse Validation this skillOfficeDev/microsoft-365-agents-toolkit | 781 | — | ~10k | Automated safety check: Warn | Custom licence | |
| Spfx Releasepnp/docker-spfx | 134 | — | ~572 | Automated safety check: Notes | MIT | |
| AI Agent PostureSCStelz/security-investigator | 250 | — | ~21k | Automated safety check: Pass | MIT | |
| Workiq Copilotgithub/awesome-copilot | 40k | 1 repos | ~1.4k | Automated safety check: Pass | MIT | |
| Teams App Developermicrosoft/skills | 3.1k | — | ~1.9k | Automated safety check: Notes | MIT | |
| Virtual DesktopLeoYeAI/openclaw-master-skills | 2.2k | — | ~4.5k | Automated safety check: Notes | MIT |
Similar skills
AI Agent Posture
SCStelz/security-investigator
Audit or report on AI agent security posture across Copilot Studio, Microsoft 365 Copilot, Microsoft Foundry, and third-party agents.
- Official
Workiq Copilot
github/awesome-copilot
Guides the Copilot CLI on how to use the WorkIQ CLI/MCP server to query Microsoft 365 Copilot data (emails, meetings, docs, Teams, people) for live context, summaries, and recommendations.
- Official
Teams App Developer
microsoft/skills
Builds, tests, and deploys Microsoft 365 apps and agents for Teams and Copilot.
Virtual Desktop
LeoYeAI/openclaw-master-skills
Full Computer Use for OpenClaw via kasmweb/chrome Docker sidecar.
Outlook Calendar
Porabuild/Poracode
Read an Outlook calendar, find meeting times, and create or move events through the Microsoft 365 MCP server.
More from OfficeDev/microsoft-365-agents-toolkit
Component Governance Remediation
OfficeDev/microsoft-365-agents-toolkit
A skill your agent uses when: retrieving, exporting, triaging, or remediating Azure DevOps Component Governance alerts for this repository, including CG report URLs, vulnerable pnpm dependencies…
Microsoft 365 Agents Toolkit
OfficeDev/microsoft-365-agents-toolkit
Builds, tests, and deploys Microsoft 365 apps and agents for Teams and Copilot.
Vscuse Case Diagnosis
OfficeDev/microsoft-365-agents-toolkit
A skill your agent uses when: running an existing vscuse test case, reproducing a failing vscuse plan, deciding product bug vs test plan drift vs setup failure vs flake, repairing a failing case…
Vscuse Scenario Authoring
OfficeDev/microsoft-365-agents-toolkit
A skill your agent uses when: reading a docs scenario, PRD, mockup, or user flow and using vscuse-ui/noVNC as the primary authoring surface to record, generate, replace, or update vscuse test plans…
Prd UX Design
OfficeDev/microsoft-365-agents-toolkit
A skill your agent uses when adding or changing product requirements, scenarios, user flows, surface behavior, or design artifacts before specs or implementation.
Vibe Coding
OfficeDev/microsoft-365-agents-toolkit
End-to-end workflow for agent-driven changes that add or modify behavior in the toolkit packages.
Related
Works with
Categories
Questions about Local Vscuse Validation
What does Local Vscuse Validation do?
A skill your agent uses when: setting up shared local vscuse prerequisites, credentials, runner, local or pinned published Docker images, local VSIX, env variables, and common rules for Microsoft…. Local Vscuse Validation is an agent skill from OfficeDev/microsoft-365-agents-toolkit. Use when: setting up shared local vscuse prerequisites, credentials, runner, local or pinned published Docker images, local VSIX, env variables, and common rules for Microsoft 365 Agents Toolkit vscuse work.
When should I use Local Vscuse Validation?
Local Vscuse Validation fits situations like: : setting up shared local vscuse prerequisites; pinned published Docker images; common rules for Microsoft 365 Agents Toolkit vscuse work.
How do I install Local Vscuse Validation in Claude Code?
Run `npx skills add OfficeDev/microsoft-365-agents-toolkit --skill local-vscuse-validation -a claude-code`. Or copy the skill folder (.github/skills/local-vscuse-validation in OfficeDev/microsoft-365-agents-toolkit) into .claude/skills/local-vscuse-validation in your project. Claude Code loads it when a task matches its description.
How do I install Local Vscuse Validation in Codex?
Run `npx skills add OfficeDev/microsoft-365-agents-toolkit --skill local-vscuse-validation -a codex`. Or copy the skill folder (.github/skills/local-vscuse-validation in OfficeDev/microsoft-365-agents-toolkit) into .agents/skills/local-vscuse-validation in your project. Codex loads it when a task matches its description.
Can I use Local Vscuse Validation 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 OfficeDev/microsoft-365-agents-toolkit --skill local-vscuse-validation -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/local-vscuse-validation, .gemini/skills/local-vscuse-validation, .github/skills/local-vscuse-validation and .opencode/skills/local-vscuse-validation in your project.
What does Local Vscuse Validation need to run?
Going by SKILL.md and its folder, Local Vscuse Validation needs the command-line tools its instructions call (docker, gh, pnpm, npm and node) and credentials named M365_ACCOUNT_PASSWORD. Our summary lists: Python 3; Docker.
Does Local Vscuse Validation access the network?
SKILL.md names 3 domains. In commands or code: api.github.com, registry.npmjs.org and packagefeedproxy.microsoft.io; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.
Is Local Vscuse Validation safe to install?
Our automated static check of SKILL.md flagged 1 warning(s): mentions a credentials file (ssh keys, cloud or package-manager tokens). Read the flagged lines before installing; the check is not a guarantee either way.
What licence does Local Vscuse Validation use?
Local Vscuse Validation has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Local Vscuse Validation use?
About 10k tokens (SKILL.md is roughly 41k 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 Local Vscuse Validation?
Skills that share tags, products or a category with Local Vscuse Validation: Spfx Release (pnp/docker-spfx, 134 stars), AI Agent Posture (SCStelz/security-investigator, 250 stars), Workiq Copilot (github/awesome-copilot, 40k stars) and Teams App Developer (microsoft/skills, 3.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Local Vscuse Validation?
OfficeDev (a GitHub organization) maintains it in OfficeDev/microsoft-365-agents-toolkit, which has 781 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 9, 2026.
Source: OfficeDev/microsoft-365-agents-toolkit on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.