sase-gate

name	sase_gate
description	Create beautiful, robust, and powerful custom notification gates on the fly. Use this as the easy way to propose commands for user confirmation, especially dangerous commands or commands the user asked to confirm before use.

Before doing anything else, run this command to record that you are using this skill:

sase skill use sase_gate --reason "<one-line reason for using this skill>"

Use this skill when work must pause for a durable, command-backed user decision.

Create beautiful, robust, and powerful custom notification gates on the fly. A custom gate is the easy way to propose commands for confirmation before they run: for example, a dangerous or irreversible command, a production change, or any command the user explicitly asked to approve first. Use /sase_questions instead when you only need an answer and no reviewed command should execute.

Design The Gate

Start with one option query that reads like the decision:

(restart AND verify) OR reject

Each OR branch is a mutually exclusive way to resolve the gate. A singleton branch is one button that runs its option. An AND branch is a group of independently selectable options with one submit button; the user may submit any non-empty subset. AND binds tighter than OR, and every option id must appear exactly once in the query and exactly once in the options list.

• Give the notification a fitting single-glyph icon. Examples: 🛡️ for a safety check, 🚀 for a deployment, 🧹 for cleanup, or 🔐 for an access change.
• Give every option its own clear label, command, and fitting icon such as ✅ for approve, ✋ for reject, or ⏸️ for defer. Even a reject option needs an owned command; use a no-op command that emits a JSON result.
• Set default_selected on members of an AND branch. It defaults to true; singleton branches ignore it.
• Declare exactly one complete query branch as primary_branch, with its option ids in canonical query order. Enter submits this branch from the review modal; for an AND branch it preserves any options the user toggled with Space.
• Add a groups entry when an AND branch's submit button should differ from its first option. Match the branch by its option ids, then configure the submit label and icon.
• Set every option's feedback to disabled, optional, or required. Custom gate options default to optional, but write the mode explicitly so the user-facing contract is obvious. An AND selection uses the strongest feedback mode among the selected options.
• Set gate_timeout_seconds when waiting forever would be unsafe. Omit it only when the request should remain pending until it is answered or cancelled.

Command argv arrays are executed without a shell. Their first element must name an executable command resource in the bundle. A command receives the gate input as JSON on stdin and must print exactly one JSON value on stdout; diagnostics belong on stderr. Every command's output must satisfy its option's result_schema.

Author The Request

Write the complete schema-version 3 request to a JSON file. This example asks permission to restart a service, lets the user include or omit the health check, and provides a separate rejection path:

{
  "schema_version": 3,
  "kind": "custom",
  "producer": {
    "agent": "my-agent"
  },
  "payload": {
    "intent": "Restart the example service after its configuration changed",
    "target": "example.service"
  },
  "presentation": {
    "icon": "🚀",
    "sender": "deployment-confirmation",
    "notes": ["Restart example.service now?", "Select whether to verify it afterward."],
    "tags": ["deployment", "confirmation"]
  },
  "query": "(restart AND verify) OR reject",
  "primary_branch": ["restart", "verify"],
  "options": [
    {
      "id": "restart",
      "label": "Restart service",
      "icon": "🚀",
      "default_selected": true,
      "feedback": "optional",
      "command": {
        "argv": ["commands/restart"]
      },
      "input_schema": {
        "type": "object"
      },
      "result_schema": {
        "type": "object",
        "required": ["status"],
        "properties": {
          "status": { "const": "restarted" }
        }
      }
    },
    {
      "id": "verify",
      "label": "Verify service health",
      "icon": "🧪",
      "default_selected": true,
      "feedback": "disabled",
      "command": {
        "argv": ["commands/verify"]
      },
      "result_schema": {
        "type": "object",
        "required": ["status"],
        "properties": {
          "status": { "const": "healthy" }
        }
      }
    },
    {
      "id": "reject",
      "label": "Do not restart",
      "icon": "✋",
      "feedback": "required",
      "command": {
        "argv": ["commands/reject"]
      },
      "result_schema": {
        "type": "object",
        "required": ["status"],
        "properties": {
          "status": { "const": "rejected" }
        }
      }
    }
  ],
  "groups": [
    {
      "options": ["restart", "verify"],
      "label": "Restart service",
      "icon": "🚀"
    }
  ],
  "resources": [
    {
      "path": "commands/restart",
      "role": "command",
      "content": "#!/bin/sh\nset -eu\nsystemctl --user restart example.service\nprintf '{\"status\":\"restarted\"}\\n'\n"
    },
    {
      "path": "commands/verify",
      "role": "command",
      "content": "#!/bin/sh\nset -eu\nsystemctl --user is-active example.service >/dev/null\nprintf '{\"status\":\"healthy\"}\\n'\n"
    },
    {
      "path": "commands/reject",
      "role": "command",
      "content": "#!/bin/sh\nprintf '{\"status\":\"rejected\"}\\n'\n"
    }
  ],
  "gate_timeout_seconds": 900,
  "auto": false
}

For larger commands, set a resource's source to a script you authored instead of embedding content; use exactly one of source or content. Keep command resources narrowly scoped to the action shown to the user.

Create And Wait

Create the durable gate and save its stable descriptor:

sase gate create < gate-request.json > gate-descriptor.json

Read request_id and kind from that descriptor, then wait mechanically:

sase gate wait --id <request-id> --kind custom --json

sase gate wait honors the request timeout. Its optional --timeout can shorten that deadline. If the rest of your work does not depend on the answer, proceed detached after creation instead of waiting; keep the descriptor as the durable handoff.

Handle The Result

The wait result has status (answered, cancelled, or timeout), selected_option_ids, feedback, and response_path. An answered result lists the selected options in query order. For the example, ["restart", "verify"] runs both group members, ["restart"] runs only the restart command, and ["reject"] takes the singleton rejection branch. Respect cancellation and timeout as terminal outcomes; do not run the proposed action through another path.

Never poll bundle files directly. Never run bundle commands by hand. Creation hashes every owned command and the shared executor verifies and runs the selected commands. Automatic resolution is forbidden for custom gates: never enable auto or use an automatic-resolution path to bypass the user's decision.