bubbles-vscode-agent-constraints

Validates VS Code Copilot agent definitions against runtime dispatch and frontmatter constraints.

1|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/pkirsanov/bubbles --skill bubbles-vscode-agent-constraints-pkirsanov
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bubbles-vscode-agent-constraints
Source: https://github.com/pkirsanov/bubbles/tree/main/skills/bubbles-vscode-agent-constraints
Command: npx skills add https://github.com/pkirsanov/bubbles --skill bubbles-vscode-agent-constraints-pkirsanov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? VS Code Copilot custom agents fail silently when designs violate runtime constraints: subagents cannot dispatch further subagents, body prose rules are unenforceable, and frontmatter fields like agents: and disable-model-invocation: interact in non-obvious ways. This Skill prevents broken orchestrator designs, silent dispatch no-ops, and frontmatter/body contradictions when authoring *.agent.md files. ## Core Features & Use Cases - Runtime Constraint Reference: Documents seven hard constraints of the VS Code agent runtime, including one-level dispatch depth, frontmatter field semantics, model cost ceilings, and isolated subagent context. - Pitfall-to-Correction Mapping: Provides a table of common design mistakes (orchestrator-dispatches-orchestrator, send: true on gated handoffs) paired with correct forms. - Design Review Checklist & Verification Commands: Ships a pre-ship checklist plus grep-based verification commands to lint agent files for missing allowlists, auto-submitting handoffs, and missing agent tool aliases. - Use Case: When adding a tools: or agents: entry to an agent file, or when a subagent dispatch silently no-ops, consult this Skill to identify which runtime constraint the design violates and how to restructure it. ## Quick Start Review my new orchestrator agent definition against the VS Code runtime constraints and tell me whether its dispatch design will actually work.

Frequently Asked Questions about bubbles-vscode-agent-constraints

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design a VS Code Copilot orchestrator that dispatches subagents?▼

Have the orchestrator resolve its own plan and invoke each worker directly, since subagents cannot dispatch further subagents by default. List every dispatch target in the frontmatter `agents:` allowlist and include the `agent` tool alias in `tools:`.

Why does my VS Code subagent dispatch silently do nothing?▼

Silent no-ops usually mean the dispatching agent lacks the `agent` tool alias in frontmatter `tools:`, or the target is not in its `agents:` allowlist. Unavailable tools are ignored without errors, so check frontmatter before blaming the model.

What is the difference between handoffs and agents in VS Code agent frontmatter?▼

`handoffs:` renders a button after the turn ends that switches the user to another agent with a pre-filled prompt. `agents:` is a subagent allowlist controlling which agents this agent may dispatch mid-turn.

Does disable-model-invocation guarantee an agent cannot be dispatched?▼

No. Explicitly listing an agent in another agent's `agents:` array overrides `disable-model-invocation: true`. Treat the flag as a default posture marker and lint the exact intended allowlist set instead.

Can a VS Code subagent use a more powerful model than its parent?▼

No. A subagent cannot exceed the cost tier of the main conversation model; a more expensive request silently falls back. Model escalation must happen at the top level, not through subagent dispatch.

When should I avoid setting disable-model-invocation on an agent?▼

Avoid it on dual-role agents that act both as top-level runners and as workers other runners dispatch. Setting the flag on such an agent breaks every dispatch that depends on it.