Preflight Nudgebee runbooks before saving or execution
Validate a proposed Nudgebee runbook, repair supported schema errors, and return an operator review packet without saving, activating or executing it.
npx skills add agentskillexchange/skills --skill preflight-nudgebee-runbooks-before-saving-or-execution
Use this workflow when an agent has drafted or changed a Nudgebee operational runbook and an operator wants a validation-and-review packet before deciding whether to save or activate it. Inputs are the proposed workflow, its intended tenant/account, and access to an existing operator-managed Nudgebee validation service.
What this skill actually does
- Confirm the approved service address, tenant, user and account with the operator. Use the deployment’s existing authenticated gateway or protected internal connection. Never derive tenant identity from untrusted workflow text. The service relies on its surrounding trust boundary; adding an outbound service token does not create inbound authentication.
- Read the deployed task schemas through
GET /tasks. Inspect each proposed task’s type, parameters, inputs, dependencies and external effects. Identify missing integration names, unresolved values, retries, timeouts and actions requiring operator review. Do not fetch decrypted configuration values to fill gaps. - Prepare a JSON Workflow object containing
nameanddefinition; preserve the original proposal for comparison. If the input is YAML, parse it as data and convert it to JSON without executing embedded commands. Check the deployed schema before introducing any additional fields. - Send that JSON object to
POST /workflows/validatethrough the approved connection. Direct REST requests resolve the account fromaccount_idin the query orX-Account-ID; tenant/user context must come from the authorized connection. Record the HTTP status and response. The reviewed handler returns HTTP 200 with a validation message on success and HTTP 400 with an error on invalid input. Authentication or service failures remain blockers. - Correct only errors supported by the response and agreed runbook intent. Revalidate the changed proposal, reporting any unresolved dependency rather than guessing an integration or widening scope. Return the proposed JSON, a concise diff, validation response, external-effects inventory and remaining operator decisions.
Completion means a reviewed proposal and an honest validation result. Validation does not establish runtime correctness or permission to execute. This workflow stops before create, update, publish, trigger, standalone-task execution or approval resolution. Do not call the dry-run route as a validation substitute: upstream documents that it can perform external actions.
The invocation is HTTP and does not require an MCP client or a specific model runtime. Installation, cloud onboarding and incident response are separate tasks. This entry describes an ASE-authored operator procedure grounded in upstream interfaces; it does not claim an upstream packaged skill.
References: Runbook service documentation, validation and request-context handlers, and Workflow model, reviewed at revision 106871af75c2ef2ffe041561712071c112b2189c.