Emc
aklofas/kicad-happy
EMC pre-compliance risk analysis for KiCad PCB designs — 18 check categories, 44 rule IDs covering ground planes, decoupling, I/O filtering, switching harmonics, clock routing, differential pair…
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…
Install Vscuse Case Diagnosis
$ npx skills add OfficeDev/microsoft-365-agents-toolkit --skill vscuse-case-diagnosis -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install OfficeDev/microsoft-365-agents-toolkit vscuse-case-diagnosis --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/vscuse-case-diagnosis .claude/skills/vscuse-case-diagnosis && 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 "vscuse-case-diagnosis" agent skill from https://github.com/OfficeDev/microsoft-365-agents-toolkit/tree/dev/.github/skills/vscuse-case-diagnosis into .claude/skills/vscuse-case-diagnosis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vscuse-case-diagnosis", 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/vscuse-case-diagnosisType 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 vscuse-case-diagnosis -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install OfficeDev/microsoft-365-agents-toolkit vscuse-case-diagnosis --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/vscuse-case-diagnosis .agents/skills/vscuse-case-diagnosis && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "vscuse-case-diagnosis" agent skill from https://github.com/OfficeDev/microsoft-365-agents-toolkit/tree/dev/.github/skills/vscuse-case-diagnosis into .agents/skills/vscuse-case-diagnosis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vscuse-case-diagnosis", 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 vscuse-case-diagnosis -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install OfficeDev/microsoft-365-agents-toolkit vscuse-case-diagnosis --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/vscuse-case-diagnosis .cursor/skills/vscuse-case-diagnosis && 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 "vscuse-case-diagnosis" agent skill from https://github.com/OfficeDev/microsoft-365-agents-toolkit/tree/dev/.github/skills/vscuse-case-diagnosis into .cursor/skills/vscuse-case-diagnosis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vscuse-case-diagnosis", 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/vscuse-case-diagnosis--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 vscuse-case-diagnosis -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install OfficeDev/microsoft-365-agents-toolkit vscuse-case-diagnosis --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/vscuse-case-diagnosis .gemini/skills/vscuse-case-diagnosis && 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 "vscuse-case-diagnosis" agent skill from https://github.com/OfficeDev/microsoft-365-agents-toolkit/tree/dev/.github/skills/vscuse-case-diagnosis into .gemini/skills/vscuse-case-diagnosis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vscuse-case-diagnosis", 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 vscuse-case-diagnosisInstalls 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 vscuse-case-diagnosis -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/vscuse-case-diagnosis .github/skills/vscuse-case-diagnosis && 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 "vscuse-case-diagnosis" agent skill from https://github.com/OfficeDev/microsoft-365-agents-toolkit/tree/dev/.github/skills/vscuse-case-diagnosis into .github/skills/vscuse-case-diagnosis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vscuse-case-diagnosis", 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 vscuse-case-diagnosis -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 vscuse-case-diagnosis --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/vscuse-case-diagnosis .opencode/skills/vscuse-case-diagnosis && 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 "vscuse-case-diagnosis" agent skill from https://github.com/OfficeDev/microsoft-365-agents-toolkit/tree/dev/.github/skills/vscuse-case-diagnosis into .opencode/skills/vscuse-case-diagnosis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vscuse-case-diagnosis", 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
vscuse-case-diagnosis- GitHub stars
- 780
- Token cost
- ~4.1k tokens
- SKILL.md length
- 2,108 words
- Files
- 1
- Skills in repo
- 7
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
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…
- Works in 7 steps: Locate the Owning Case → Prepare the Runtime and Select the… → Execute the Focused Plan → …
- : running an existing vscuse test case
- SKILL.md covers Goal, Required Inputs, Core Rules and Procedure
- Needs M365_ACCOUNT_PASSWORD
What it does
Vscuse Case Diagnosis is an agent skill from OfficeDev/microsoft-365-agents-toolkit. Use 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 with vscuse-ui/noVNC when useful, and finishing with vscuse CLI validation.
Its SKILL.md is about 4.1k 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 Test generation. It works with Microsoft 365. The repository describes itself as: Developer tools for building Teams apps.
When your agent uses it
- : 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 with vscuse-ui/noVNC when useful
Example prompts
- “/vscuse-case-diagnosis”
Requirements
- Docker
Workflow steps
7 steps, taken from the step headings in SKILL.md.
- Locate the Owning Case
- Prepare the Runtime and Select the Product Image
- Execute the Focused Plan
- Gather Failure Evidence
- Classify Before Editing
- Repair the Smallest Surface with vscuse-ui First
- Validate and Report
What it can do on your machine
Read from SKILL.md and the folder at commit c89a0dd. 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
No scripts in the folder and no shell commands in SKILL.md (its code samples are powershell).
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 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
Vscuse Case Diagnosis loads about 4.1k tokens when it runs. Until then it costs about 68 tokens; SKILL.md has 2,108 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
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 2,108 words (~4,097 tokens).
“Run an existing local vscuse test case against an explicitly selected product image, show the real execution through the integrated browser, and classify any failure as one of:”
- name
- vscuse-case-diagnosis
- argument-hint
- Plan/case name, failing step, or feature workflow to diagnose
Files
Just SKILL.md in .github/skills/vscuse-case-diagnosis of OfficeDev/microsoft-365-agents-toolkit.
Open the folder on GitHubat commit c89a0dd
Compare with similar skills
Vscuse Case Diagnosis 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 |
|---|---|---|---|---|---|---|
| Vscuse Case Diagnosis this skillOfficeDev/microsoft-365-agents-toolkit | 780 | — | ~4.1k | Automated safety check: Pass | Custom licence | |
| Emcaklofas/kicad-happy | 1.4k | 1 repos | ~2.8k | Automated safety check: Pass | MIT | |
| Swig Testswig/swig | 6.3k | — | ~2.3k | Automated safety check: Pass | Custom licence | |
| Generate Test Cases342164796/generate-test-cases | 120 | 1 repos | ~2.9k | Automated safety check: Pass | None | |
| Wioworkersio/skills | 204 | — | ~5.8k | Automated safety check: Pass | MIT | |
| Verify Cc Safety Netkenryu42/cc-safety-net | 1.6k | — | ~2k | Automated safety check: Pass | MIT |
Similar skills
Swig Test
swig/swig
Run SWIG test suite for specific languages. An agent skill from swig/swig.
Generate Test Cases
342164796/generate-test-cases
自主学习型测试文档生成器。从需求文档（Markdown）生成测试用例 XMind 文件，支持持久化记忆和持续学习。当用户提到"生成测试用例"、"根据需求生成测试"时触发。
Wio
workersio/skills
Testing workflow skill for finding high-value test candidates, writing focused tests, generating realistic workloads, reviewing test value, and diagnosing test-suite health.
Verify Cc Safety Net
kenryu42/cc-safety-net
Launch and drive the real cc-safety-net CLI — the hook decision path, explain, status/doctor, logs, and the local policy GUI — against an isolated home, capturing evidence.
- Official
File Server
microsoft/WindowsProtocolTestSuites
ALWAYS LOAD THIS SKILL when working with FileServer, SMB, SMB2, SMB3, CIFS, file sharing, MS-SMB2, MS-FSCC, MS-FSA, MS-DFSC, MS-FSRVP, MS-RSVD, MS-SQOS, or any file server protocol test…
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 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.
Local Vscuse Validation
OfficeDev/microsoft-365-agents-toolkit
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…
Related
Works with
Categories
Questions about Vscuse Case Diagnosis
What does Vscuse Case Diagnosis do?
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 Case Diagnosis is an agent skill from OfficeDev/microsoft-365-agents-toolkit. Use 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 with vscuse-ui/noVNC when useful, and finishing with vscuse CLI validation.
When should I use Vscuse Case Diagnosis?
Vscuse Case Diagnosis fits situations like: : 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 with vscuse-ui/noVNC when useful.
How do I install Vscuse Case Diagnosis in Claude Code?
Run `npx skills add OfficeDev/microsoft-365-agents-toolkit --skill vscuse-case-diagnosis -a claude-code`. Or copy the skill folder (.github/skills/vscuse-case-diagnosis in OfficeDev/microsoft-365-agents-toolkit) into .claude/skills/vscuse-case-diagnosis in your project. Claude Code loads it when a task matches its description.
How do I install Vscuse Case Diagnosis in Codex?
Run `npx skills add OfficeDev/microsoft-365-agents-toolkit --skill vscuse-case-diagnosis -a codex`. Or copy the skill folder (.github/skills/vscuse-case-diagnosis in OfficeDev/microsoft-365-agents-toolkit) into .agents/skills/vscuse-case-diagnosis in your project. Codex loads it when a task matches its description.
Can I use Vscuse Case Diagnosis 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 vscuse-case-diagnosis -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/vscuse-case-diagnosis, .gemini/skills/vscuse-case-diagnosis, .github/skills/vscuse-case-diagnosis and .opencode/skills/vscuse-case-diagnosis in your project.
What does Vscuse Case Diagnosis need to run?
Going by SKILL.md and its folder, Vscuse Case Diagnosis needs credentials named M365_ACCOUNT_PASSWORD. Our summary lists: Docker.
Does Vscuse Case Diagnosis 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 Vscuse Case Diagnosis 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 Vscuse Case Diagnosis use?
Vscuse Case Diagnosis 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 Vscuse Case Diagnosis use?
About 4.1k tokens (SKILL.md is roughly 16k 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 Vscuse Case Diagnosis?
Skills that share tags, products or a category with Vscuse Case Diagnosis: Emc (aklofas/kicad-happy, 1.4k stars), Swig Test (swig/swig, 6.3k stars), Generate Test Cases (342164796/generate-test-cases, 120 stars) and Wio (workersio/skills, 204 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Vscuse Case Diagnosis?
OfficeDev (a GitHub organization) maintains it in OfficeDev/microsoft-365-agents-toolkit, which has 780 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 10, 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.