get a key
steadybase-$ skill pg_run_trigger_now
toolpg_run_trigger_now
groupWhat changed
endpointhttps://mcp.steadybase.io/mcp

PREVIEW A TRIGGER NOW ON THE BOX (Postgres). Runs one trigger synchronously over its whole lookback window on your book (transcripts by hybrid search, documents and signals by keyword), capped at 20 hits, nothing written. Each hit is verbatim QUOTE with RECEIPT_URL, CHAR_START/CHAR_END and a SCORE (DETAILS.score_kind says which). The hourly runner persists the real hits; read those with pg_trigger_hits.

arguments
trigger_id* string the TRIGGER_ID from pg_define_trigger or pg_list_triggers
install
claude mcp add --transport http steadybase https://mcp.steadybase.io/mcp   --header "Authorization: Bearer $STEADYBASE_KEY"
call
curl -s https://api.steadybase.io/v1/mcp/call   -H "Authorization: Bearer $STEADYBASE_KEY" -H "Content-Type: application/json"   -d '{"tool":"pg_run_trigger_now","arguments":{"trigger_id":"..."}}'
contract
A quote comes with its receiptEvery returned statement carries the verbatim sentence and the URL it came from, and where the source is a transcript, the character offsets inside it. A statement with no receipt is not returned.
Empty is an answerWhen there is no sourced statement, the skill returns nothing. It does not summarise, infer, or fill the gap from general knowledge. Handle the empty case rather than retrying until something appears.
No personal contact dataNo email address, phone number, home address or personal social account is returned by any skill, at any tier. A person is a name, a professional role, a LinkedIn profile URL and the public record that puts them in that role.
No customer data crosses a keyA tenant-scoped skill reads only that tenant. Nothing about any customer appears on the public site or in another tenant answer.

/skills/

steadybase-$