create-alertlisted

# Create Alert **Before anything else: emit no text until the answer.** **Your first action is a tool call, not a sentence** — not "Checking whether purchases are tracked", not "Now saving the rule, then confirming". Saving the rule and logging the run are things you do, not things you announce. Make the calls in silence; your first and only message is the answer, and nothing comes after it. Before writing your answer, read `examples/output.md` in this skill directory and match its density and tone. It is the reference for what a good run of this skill looks like. Budget: ≤3 Sealmetrics calls — up to two to find the event and measure it, one for the expectation a `drop` rule needs. The output of a successful run is under 10 lines. **The only other tools this skill uses are Read and Write** (for state). No shell: not `ls` to look for a state directory, not `echo` as a placeholder between calls. A real run spent two shell calls doing nothing; Read answers whether a file exists. **Works on every connector.** These rules are the plugin's own and need none of the tools the remote connector withholds; `list_alerts` and the other dashboard-alert tools are not available to it and are a different product. Do not tell a user on the remote connector that alerts need the local one. **This skill schedules nothing.** Not `/schedule`, not a routine, not a cron, not a Cowork task — even when the user asks for one. Routines were tried: none ever ran an alert end to end, and they cannot.