Write A Spec
inkeep/open-knowledge
Scope a feature end to end and write an implementation spec under specs/ from an accepted proposal — current-system mapping, goals/non-goals, a Decision Log for one-way-door choices, a live Open…
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…
Install Vscuse Scenario Authoring
$ npx skills add OfficeDev/microsoft-365-agents-toolkit --skill vscuse-scenario-authoring -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install OfficeDev/microsoft-365-agents-toolkit vscuse-scenario-authoring --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-scenario-authoring .claude/skills/vscuse-scenario-authoring && 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-scenario-authoring" agent skill from https://github.com/OfficeDev/microsoft-365-agents-toolkit/tree/dev/.github/skills/vscuse-scenario-authoring into .claude/skills/vscuse-scenario-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vscuse-scenario-authoring", 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-scenario-authoringType 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-scenario-authoring -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install OfficeDev/microsoft-365-agents-toolkit vscuse-scenario-authoring --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-scenario-authoring .agents/skills/vscuse-scenario-authoring && 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-scenario-authoring" agent skill from https://github.com/OfficeDev/microsoft-365-agents-toolkit/tree/dev/.github/skills/vscuse-scenario-authoring into .agents/skills/vscuse-scenario-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vscuse-scenario-authoring", 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-scenario-authoring -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install OfficeDev/microsoft-365-agents-toolkit vscuse-scenario-authoring --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-scenario-authoring .cursor/skills/vscuse-scenario-authoring && 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-scenario-authoring" agent skill from https://github.com/OfficeDev/microsoft-365-agents-toolkit/tree/dev/.github/skills/vscuse-scenario-authoring into .cursor/skills/vscuse-scenario-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vscuse-scenario-authoring", 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-scenario-authoring--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-scenario-authoring -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install OfficeDev/microsoft-365-agents-toolkit vscuse-scenario-authoring --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-scenario-authoring .gemini/skills/vscuse-scenario-authoring && 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-scenario-authoring" agent skill from https://github.com/OfficeDev/microsoft-365-agents-toolkit/tree/dev/.github/skills/vscuse-scenario-authoring into .gemini/skills/vscuse-scenario-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vscuse-scenario-authoring", 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-scenario-authoringInstalls 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-scenario-authoring -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-scenario-authoring .github/skills/vscuse-scenario-authoring && 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-scenario-authoring" agent skill from https://github.com/OfficeDev/microsoft-365-agents-toolkit/tree/dev/.github/skills/vscuse-scenario-authoring into .github/skills/vscuse-scenario-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vscuse-scenario-authoring", 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-scenario-authoring -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-scenario-authoring --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-scenario-authoring .opencode/skills/vscuse-scenario-authoring && 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-scenario-authoring" agent skill from https://github.com/OfficeDev/microsoft-365-agents-toolkit/tree/dev/.github/skills/vscuse-scenario-authoring into .opencode/skills/vscuse-scenario-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vscuse-scenario-authoring", 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-scenario-authoring- GitHub stars
- 780
- Token cost
- ~4.3k tokens
- SKILL.md length
- 2,149 words
- Files
- 1
- Skills in repo
- 7
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
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…
- Works in 7 steps: Extract the Scenario From Docs → Map Existing Coverage → Start vscuse-ui → …
- : reading a docs scenario
- SKILL.md covers Goal, Required Inputs, Core Rules and Procedure, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Vscuse Scenario Authoring is an agent skill from OfficeDev/microsoft-365-agents-toolkit. Use 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; decide existing coverage vs new case; validate product behavior against docs, then finish with vscuse CLI validation.
Its SKILL.md is about 4.3k 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 Product & Project Management, covering PRD writing, UX design and Test generation. The repository describes itself as: Developer tools for building Teams apps.
When your agent uses it
- : reading a docs scenario
- User flow and using vscuse-ui/noVNC as the primary authoring surface to record
- Update vscuse test plans
- Decide existing coverage vs new case
Example prompts
- “/vscuse-scenario-authoring”
Requirements
- Docker
Workflow steps
7 steps, taken from the step headings in SKILL.md.
- Extract the Scenario From Docs
- Map Existing Coverage
- Start vscuse-ui
- Execute the Docs Scenario in the Integrated Browser
- Record, Edit, or Update Coverage in vscuse-ui
- Clean Generated Content
- Validate the Authored Plan
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 and json).
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
Vscuse Scenario Authoring loads about 4.3k tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 2,149 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,149 words (~4,279 tokens).
“Use docs, PRDs, scenarios, or mockups as the source of truth for vscuse coverage. Use vscuse-ui and noVNC as the primary authoring surface: execute the scenario in a real vscuse desktop, decide whether product behavior matches the docs, and then…”
- name
- vscuse-scenario-authoring
- argument-hint
- Docs/mockup path and scenario to record or map to vscuse coverage
Files
Just SKILL.md in .github/skills/vscuse-scenario-authoring of OfficeDev/microsoft-365-agents-toolkit.
Open the folder on GitHubat commit c89a0dd
Compare with similar skills
Vscuse Scenario Authoring 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 Scenario Authoring this skillOfficeDev/microsoft-365-agents-toolkit | 780 | — | ~4.3k | Automated safety check: Pass | Custom licence | |
| Write A Specinkeep/open-knowledge | 4.5k | — | ~4.9k | Automated safety check: Pass | GPL-3.0 | |
| Review Rfcnurettincoban/ai-prd-workflow | 298 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Rhesisrhesis-ai/rhesis | 397 | — | ~1.2k | Automated safety check: Pass | Proprietary | |
| Reviewgolbin/agent-skills | 214 | — | ~706 | Automated safety check: Pass | None | |
| Write Product Specbholmesdev/hubble.md | 1.5k | — | ~966 | Automated safety check: Pass | MIT |
Similar skills
Review Rfc
nurettincoban/ai-prd-workflow
Review an implemented RFC in a fresh context against its acceptance criteria, RULES.md and the test plan, and save the review to reviews/.
Rhesis
rhesis-ai/rhesis
Design, run, and analyze AI test suites on Rhesis — explore endpoints, build test foundations from a spec, create requirements and metrics, execute tests, and analyze results.
Review
golbin/agent-skills
Review software designs and implementations for user experience, simplicity, and maintainability; apply fixes when requested.
Write Product Spec
bholmesdev/hubble.md
Write a PRODUCT.md spec for a significant Hubble user-facing feature, focused only on user experience and observable behavior.
Opportunity Assessment
andreaskelm/pm-brain
Assess whether an idea, feature request, or opportunity is worth pursuing before anyone writes a PRD.
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…
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
Categories
Questions about Vscuse Scenario Authoring
What does Vscuse Scenario Authoring do?
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…. Vscuse Scenario Authoring is an agent skill from OfficeDev/microsoft-365-agents-toolkit. Use 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; decide existing coverage vs new case; validate product behavior against docs, then finish with vscuse CLI validation.
When should I use Vscuse Scenario Authoring?
Vscuse Scenario Authoring fits situations like: : reading a docs scenario; user flow and using vscuse-ui/noVNC as the primary authoring surface to record; update vscuse test plans; decide existing coverage vs new case.
How do I install Vscuse Scenario Authoring in Claude Code?
Run `npx skills add OfficeDev/microsoft-365-agents-toolkit --skill vscuse-scenario-authoring -a claude-code`. Or copy the skill folder (.github/skills/vscuse-scenario-authoring in OfficeDev/microsoft-365-agents-toolkit) into .claude/skills/vscuse-scenario-authoring in your project. Claude Code loads it when a task matches its description.
How do I install Vscuse Scenario Authoring in Codex?
Run `npx skills add OfficeDev/microsoft-365-agents-toolkit --skill vscuse-scenario-authoring -a codex`. Or copy the skill folder (.github/skills/vscuse-scenario-authoring in OfficeDev/microsoft-365-agents-toolkit) into .agents/skills/vscuse-scenario-authoring in your project. Codex loads it when a task matches its description.
Can I use Vscuse Scenario Authoring 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-scenario-authoring -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-scenario-authoring, .gemini/skills/vscuse-scenario-authoring, .github/skills/vscuse-scenario-authoring and .opencode/skills/vscuse-scenario-authoring in your project.
What does Vscuse Scenario Authoring need to run?
SKILL.md names no scripts, command-line tools or credentials: Vscuse Scenario Authoring is instructions for the agent only. Our summary lists: Docker.
Does Vscuse Scenario Authoring 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 Scenario Authoring 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 Scenario Authoring use?
Vscuse Scenario Authoring 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 Scenario Authoring use?
About 4.3k tokens (SKILL.md is roughly 17k 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 Scenario Authoring?
Skills that share tags, products or a category with Vscuse Scenario Authoring: Write A Spec (inkeep/open-knowledge, 4.5k stars), Review Rfc (nurettincoban/ai-prd-workflow, 298 stars), Rhesis (rhesis-ai/rhesis, 397 stars) and Review (golbin/agent-skills, 214 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Vscuse Scenario Authoring?
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.