Cabloy Spec Generation
cabloy/cabloy
A skill your agent uses to create or maintain Cabloy suite specifications under repo-specs, including PRD, SRS, PDP/WBS, acceptance planning, progress, and suite ADRs.
End-to-end workflow for agent-driven changes that add or modify behavior in the toolkit packages.
Install Vibe Coding
$ npx skills add OfficeDev/microsoft-365-agents-toolkit --skill vibe-coding -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install OfficeDev/microsoft-365-agents-toolkit vibe-coding --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/vibe-coding .claude/skills/vibe-coding && 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 "vibe-coding" agent skill from https://github.com/OfficeDev/microsoft-365-agents-toolkit/tree/dev/.github/skills/vibe-coding into .claude/skills/vibe-coding/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-coding", 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/vibe-codingType 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 vibe-coding -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install OfficeDev/microsoft-365-agents-toolkit vibe-coding --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/vibe-coding .agents/skills/vibe-coding && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "vibe-coding" agent skill from https://github.com/OfficeDev/microsoft-365-agents-toolkit/tree/dev/.github/skills/vibe-coding into .agents/skills/vibe-coding/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-coding", 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 vibe-coding -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install OfficeDev/microsoft-365-agents-toolkit vibe-coding --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/vibe-coding .cursor/skills/vibe-coding && 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 "vibe-coding" agent skill from https://github.com/OfficeDev/microsoft-365-agents-toolkit/tree/dev/.github/skills/vibe-coding into .cursor/skills/vibe-coding/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-coding", 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/vibe-coding--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 vibe-coding -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install OfficeDev/microsoft-365-agents-toolkit vibe-coding --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/vibe-coding .gemini/skills/vibe-coding && 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 "vibe-coding" agent skill from https://github.com/OfficeDev/microsoft-365-agents-toolkit/tree/dev/.github/skills/vibe-coding into .gemini/skills/vibe-coding/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-coding", 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 vibe-codingInstalls 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 vibe-coding -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/vibe-coding .github/skills/vibe-coding && 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 "vibe-coding" agent skill from https://github.com/OfficeDev/microsoft-365-agents-toolkit/tree/dev/.github/skills/vibe-coding into .github/skills/vibe-coding/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-coding", 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 vibe-coding -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 vibe-coding --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/vibe-coding .opencode/skills/vibe-coding && 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 "vibe-coding" agent skill from https://github.com/OfficeDev/microsoft-365-agents-toolkit/tree/dev/.github/skills/vibe-coding into .opencode/skills/vibe-coding/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-coding", 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
vibe-coding- GitHub stars
- 781
- Token cost
- ~5.5k tokens
- SKILL.md length
- 2,647 words
- Files
- 1
- Skills in repo
- 7
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
End-to-end workflow for agent-driven changes that add or modify behavior in the toolkit packages.
- Works in 9 steps: PRD + scenario handoff validation → Design first (spec) → Confirm design inputs → …
- Changing a behavior (anything that warrants an Acceptance Criteria row)
- SKILL.md covers When to use this skill, What this skill enforces, Workflow and Common pitfalls, plus 2 more sections
- Calls npm
What it does
Vibe Coding is an agent skill from OfficeDev/microsoft-365-agents-toolkit. End-to-end workflow for agent-driven changes that add or modify behavior in the toolkit packages. Use when: adding or changing a behavior (anything that warrants an Acceptance Criteria row); refactoring toward a structural shape governed by ADRs in docs/02-architecture/; changing v4 scaffolding architecture, removing duplicate Q1/Q2/Q3 logic, extracting shared engines, or moving logic into providers/validators/steps; adding a behavior-changing CLI or VS Code action. Codifies the design-first → tests-from-AC →…
Its SKILL.md is about 5.5k 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 Development, covering Architecture decision records, Project scaffolding and User stories. It works with Visual Studio Code. The repository describes itself as: Developer tools for building Teams apps.
When your agent uses it
- Changing a behavior (anything that warrants an Acceptance Criteria row)
- Refactoring toward a structural shape governed by ADRs in docs/02-architecture/
- Changing v4 scaffolding architecture
- Removing duplicate Q1/Q2/Q3 logic
Example prompts
- “/vibe-coding”
Workflow steps
9 steps, taken from the step headings in SKILL.md.
- PRD + scenario handoff validation
- Design first (spec)
- Confirm design inputs
- Tests from AC and Flow (before any implementation)
- Implement to pass tests
- Verify gates (mechanical)
- Self-review (judgement)
- Downstream docs (conditional)
- PR
What it can do on your machine
Read from SKILL.md and the folder at commit 17203f2. 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:
npm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npm, 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
Vibe Coding loads about 5.5k tokens when it runs. Until then it costs about 157 tokens; SKILL.md has 2,647 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,647 words (~5,466 tokens).
“Use this skill when the change is non-trivial AND meets at least one of these conditions — the workflow is the same whether a human or an AI agent (Copilot, Claude Code, Cursor, etc.) is doing the work:”
- name
- vibe-coding
- argument-hint
- Describe the behavior change or structural-shape work
Files
Just SKILL.md in .github/skills/vibe-coding of OfficeDev/microsoft-365-agents-toolkit.
Open the folder on GitHubat commit 17203f2
Compare with similar skills
Vibe Coding 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 |
|---|---|---|---|---|---|---|
| Vibe Coding this skillOfficeDev/microsoft-365-agents-toolkit | 781 | — | ~5.5k | Automated safety check: Pass | Custom licence | |
| Cabloy Spec Generationcabloy/cabloy | 982 | — | ~3.2k | Automated safety check: Notes | MIT | |
| Task Workflowikarenkov/Modo | 343 | — | ~2.4k | Automated safety check: Pass | None | |
| Bmad Architectureaj-geddes/claude-code-bmad-skills | 487 | — | ~1.9k | Automated safety check: Notes | Custom licence | |
| Bmad Helpaj-geddes/claude-code-bmad-skills | 487 | — | ~1.7k | Automated safety check: Notes | Custom licence | |
| Documentation Criteriashinpr/claude-code-workflows | 690 | — | ~1.9k | Automated safety check: Pass | MIT |
Similar skills
Task Workflow
ikarenkov/Modo
Spec-driven workflow for non-trivial work. An agent skill from ikarenkov/Modo.
Bmad Architecture
aj-geddes/claude-code-bmad-skills
Solutioning skill (Winston, the Architect). An agent skill from aj-geddes/claude-code-bmad-skills.
Bmad Help
aj-geddes/claude-code-bmad-skills
Orchestration spine and "what do I do next?" router for the BMAD Planning & Orchestrator plugin.
Documentation Criteria
shinpr/claude-code-workflows
Determines which of PRD, ADR, UI Spec, Design Doc, and Work Plan a change requires, and where each is stored.
Implement Feature
Log2n-io/Typhon
Implement a GitHub issue end-to-end — scope it (whole issue or specific phases), build an acceptance-criteria plan from its design doc, get the plan approved, then develop autonomously with tests…
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.
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 Vibe Coding
What does Vibe Coding do?
End-to-end workflow for agent-driven changes that add or modify behavior in the toolkit packages. Vibe Coding is an agent skill from OfficeDev/microsoft-365-agents-toolkit. End-to-end workflow for agent-driven changes that add or modify behavior in the toolkit packages.
When should I use Vibe Coding?
Vibe Coding fits situations like: changing a behavior (anything that warrants an Acceptance Criteria row); refactoring toward a structural shape governed by ADRs in docs/02-architecture/; changing v4 scaffolding architecture; removing duplicate Q1/Q2/Q3 logic.
How do I install Vibe Coding in Claude Code?
Run `npx skills add OfficeDev/microsoft-365-agents-toolkit --skill vibe-coding -a claude-code`. Or copy the skill folder (.github/skills/vibe-coding in OfficeDev/microsoft-365-agents-toolkit) into .claude/skills/vibe-coding in your project. Claude Code loads it when a task matches its description.
How do I install Vibe Coding in Codex?
Run `npx skills add OfficeDev/microsoft-365-agents-toolkit --skill vibe-coding -a codex`. Or copy the skill folder (.github/skills/vibe-coding in OfficeDev/microsoft-365-agents-toolkit) into .agents/skills/vibe-coding in your project. Codex loads it when a task matches its description.
Can I use Vibe Coding 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 vibe-coding -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/vibe-coding, .gemini/skills/vibe-coding, .github/skills/vibe-coding and .opencode/skills/vibe-coding in your project.
What does Vibe Coding need to run?
Going by SKILL.md and its folder, Vibe Coding needs the command-line tools its instructions call (npm).
Does Vibe Coding access the network?
SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Vibe Coding 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 Vibe Coding use?
Vibe Coding 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 Vibe Coding use?
About 5.5k tokens (SKILL.md is roughly 22k 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 Vibe Coding?
Skills that share tags, products or a category with Vibe Coding: Cabloy Spec Generation (cabloy/cabloy, 982 stars), Task Workflow (ikarenkov/Modo, 343 stars), Bmad Architecture (aj-geddes/claude-code-bmad-skills, 487 stars) and Bmad Help (aj-geddes/claude-code-bmad-skills, 487 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Vibe Coding?
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 7, 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.