orca-confirm

Confirm proposed agent teams with automatic bypass on blank responses.

2|2|Updated Dec 16, 2025
One-click install
npx skills add https://github.com/adilkalam/orca --skill orca-confirm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: orca-confirm
Source: https://github.com/adilkalam/orca/tree/main/skills/orca-confirm
Command: npx skills add https://github.com/adilkalam/orca --skill orca-confirm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Handles team confirmations for /orca with a one-shot bypass mode when no answer is possible.

Core Features & Use Cases

  • Visible confirmation: Propose team, ask for confirmation once.
  • Bypass mode handling: If response is blank, proceed with proposed team.
  • Use Case: Release gating with predefined teams and bypass policy.

Quick Start

Present the proposed team, issue a single confirmation question, and return a parsed RESULT.

Frequently Asked Questions about orca-confirm

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

FAQPage Schema
How do I confirm a proposed agent team with a single confirmation step?

Team confirmation involves presenting a visible proposal, requesting one confirmation response, and proceeding automatically if no answer is provided. This single-pass approach enforces a bypass mode for cases where immediate feedback isn't available, returning a parsed STATUS for downstream routing.

What happens if a user doesn't respond to a team confirmation request?

Blank responses trigger bypass mode, allowing the proposed team to proceed without retry. This handles scenarios where confirmation cannot be obtained, such as during automated project onboarding or task routing across multiple projects.

Can I use team confirmation for release gating with predefined teams?

Yes. The Skill presents a predefined team proposal with a single confirmation gate and enforces a bypass policy when responses are blank, making it suitable for release workflows that require visible approval or automatic progression.

How does the confirmation output integrate with downstream systems?

The Skill returns a parseable STATUS output designed for downstream systems to consume, enabling immediate team assignment or routing decisions based on the confirmation result or bypass trigger.

What's the difference between team confirmation and retry-based approval flows?

This approach enforces non-retry confirmation: one question, one response window, with bypass handling for blank answers. This differs from retry-based flows that repeatedly prompt for input, providing deterministic behavior for time-sensitive routing decisions.