vscuse-scenario-authoring
100 / 100 · Low risk
Fine to try.
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.
What this skill can do
We found nothing in the files we read that matches our rules. That does not prove the skill is safe: see the limits of static scanning.
Install
Paste this into your terminal. It downloads exactly the version we scanned, not whatever is newest.
if [ -e ~/.agents/skills/'vscuse-scenario-authoring' ] || [ -L ~/.agents/skills/'vscuse-scenario-authoring' ]; then echo 'A skill folder named vscuse-scenario-authoring already exists — not replacing it' >&2; false; else d=$(mktemp -d) && git clone --quiet --filter=blob:none --no-checkout 'https://github.com/OfficeDev/microsoft-365-agents-toolkit' "$d" && git -C "$d" checkout --quiet '9c36453f37474e6ce535a24b727f8349ceb67612' -- '.github/skills/vscuse-scenario-authoring' && mkdir -p ~/.agents/skills && cp -R "$d"/'.github/skills/vscuse-scenario-authoring' ~/.agents/skills/'vscuse-scenario-authoring' && rm -rf "$d"; fi
Codex reads ~/.agents/skills directly. For Claude Code, Cursor, Copilot, Gemini CLI, Antigravity or OpenCode, also link it. For Claude Code: ln -s ~/.agents/skills/'vscuse-scenario-authoring' ~/.claude/skills/'vscuse-scenario-authoring' (other agents: ~/.cursor/skills, ~/.copilot/skills, ~/.gemini/skills, ~/.gemini/config/skills, ~/.config/opencode/skills). Or install through the finder skill, which does both.
Badge for your README
[](https://zalavijaysinh.github.io/skilltrust/repos/OfficeDev/microsoft-365-agents-toolkit/)
Score history
| Date | Version | Score |
|---|---|---|
| 2026-11-12 | 9c36453 | 100 |
| 2026-11-08 | 0f174df | 100 |