submit / default

Convert approved artifacts into external drafts or local holds via MCP tools.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Collectively-Gary/GaryOS --skill submit-default
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: submit / default
Source: https://github.com/Collectively-Gary/GaryOS/tree/main/data/skills/submit/default
Command: npx skills add https://github.com/Collectively-Gary/GaryOS --skill submit-default

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of getting an approved AI-produced artifact made externally visible when no playbook-specific submit workflow exists, without guessing and risking incorrect external actions.

Core Features & Use Cases

  • Identifies the approved artifact source from the latest draft trail entry and its artifact_refs.
  • Submits external drafts when possible by creating a preview/hold in the operator-wired external system via MCP, and records returned references.
  • Holds locally when submission isn’t appropriate by storing the artifact payload for later use by the commit stage.
  • Escalates safely when it can’t proceed by setting awaiting_operator with a stuck reason and recommended next action.

Quick Start

Ask the system to run the submit step for playbook other, and it will either create an external draft/preview or record the artifact for commit depending on what the artifact_refs indicate.

Frequently Asked Questions about submit / default

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

FAQPage Schema
How do I submit an approved AI artifact to an external system when no specific workflow exists?▼

To submit an approved artifact without a specific workflow, this Skill reads the latest draft trail entry and uses operator-wired MCP tools to create an external draft or preview URL. If no external draft representation exists, it holds the artifact locally for a later commit step.

What happens to workflow orchestration artifacts that cannot be submitted externally?▼

When external submission is not appropriate, the workflow orchestration artifact is held locally by persisting the payload verbatim. This defers the artifact to a later commit step, ensuring no data is lost while waiting for the correct operator context.

How does state trail handling work for missing external references during artifact submission?▼

State trail handling for missing external references escalates safely by setting an `awaiting_operator` status with a stuck reason. This prevents guessing incorrect external actions and includes a recommended next action for the operator to resolve the hold.

Can I use MCP tools to create preview URLs for document drafts?▼

Yes, you can use operator-wired MCP tools to create preview URLs for document drafts. The Skill identifies the approved artifact source from the draft trail and creates a preview or hold in the external system when a draft representation exists.

Why does my artifact submission get stuck with an awaiting_operator status?▼

Your artifact submission gets stuck with an `awaiting_operator` status because the workflow cannot proceed safely without external draft creation logic or operator-wired MCP tools. It escalates with a stuck reason and recommended next action to prevent incorrect external actions.