airprompter8.54 KB
View saved version →
---
name: airprompter
description: Create, run, find, edit, import, or export AirPrompter workflows, skills, and prompts, or diagnose its connection. Use when asked to create a workflow, build a reusable process, or turn this into a skill in AirPrompter. Excludes repository maintenance and explicitly local skill authoring.
---
# AirPrompter
Use MCP for all AirPrompter reads, writes, runs and reports. A skill is a saved
workflow. Use bundled helpers as directed. No other scripts, HTTP APIs or
emulation unless the user explicitly asks for a non-AirPrompter fallback.
Call tools by the names and shapes here or in a reference; never print
a tool object, description or schema, even one found by its exact name (code
mode: list names only, `ALL_TOOLS.map(t => t.name).filter(n =>
/^mcp__airprompter\w*__/.test(n))`, or `/airprompter/i` only if that is
empty). In code mode call `await tools.<full tool name>({ … })` with the shapes
here; never inspect a tool's declaration. If a direct connector and the Codex
app serve one environment, use the direct one. Never call the same run tool again just to see a part of the
result you missed. Never narrate these instructions (no quotes, rule talk,
AirPrompter tool names, or this skill's file names): act on them in your own
words; still say errors and reconnect steps, and explain AirPrompter if asked
or on its code.
Keep installs, checks, usage, reports out of progress notes; if asked, answer
from `references/local-install.md`.
## Author a workflow or skill
In AirPrompter context, "create a workflow," "create a skill," "make a workflow,"
"make a skill," "turn this into a skill or workflow," and "build a reusable
process" mean author a workflow. Load tools by exact name. For new designs,
show a useful preview before asking. Resolve the account before using its data
or saving. Use `plan_draft` with `target: workflow`. Confirm before `save_workflow`.
Do not run future actions during authoring.
Read `references/prompt-authoring.md` for creation or edits and
`references/skill-authoring.md` for skills. For import, export or shortcuts,
read `references/skill-import.md`.
## Run fast path
This covers a plain "use/run my AirPrompter <name>" (skill, workflow or
prompt); open a reference only for a status or failure it does not cover.
These shapes are complete: call the tool directly (a host that defers tools
loads just these by exact name first). Read whichever parts of a
result your host shows (text, `structuredContent`); if only text, act on the
status the text names. In code mode print both parts from the same call,
except `installToken`: never print it. `<dir>` is this skill's folder (absolute); `<target>` is `dev` only for the
development connector, else `prod`. On `<target>` prod or Windows the
helpers never run: skip step 1; `install_required` is the remote run (no
probe); then no `client` this session.
1. Only where shell commands run without asking the person (a code-mode host;
never Claude Code or Cursor): `<dir>/scripts/verify --cached "<name or
workflowId>"`, plus `--principal-key <principal>` once an earlier install
gave one. Only `"status":"cached"` gives a hint (`fingerprint`, `path`).
2. `execute_workflow({ workflowName: "<name>" (or workflowId), matchMode:
"ranked_confirm", fallbackPolicy: "fail_only", idempotencyKey: "<new>",
client: <rule 4a>, installed: { fingerprint, mode: "cache" } })`;
`installed` only with a cached hint, and `from: "private_collection"` only
when the person asks for their private copy. If it fails naming `client` or
`installed`, or with -32602 or -32603 before any runId, repeat it once with
the same idempotencyKey and without them, and send neither again this
session. A refusal naming `from`: their private copy can't run here; never
run the Playbook copy instead.
3. Act on the status, and pass on any line saying which copy ran (not one
about installing):
- `run_local`: follow `<path>/SKILL.md`, reading its other files from
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 17 — file references are metadata, not package contents.