answer_job
ChatGPTAnswer a job that is waiting for a person (or that ended with outcome needs_human). answer is what the person said; option names the one of the offered options they picked (answer may repeat it), options the several they picked when the question lets a person pick more than one (they reach the agent one per line, before the answer). resume: auto (default) resumes the agent's session with the answer when the run already ended; never only records it. If the machine reports a terminal job missing, the disposition is recorded in the cloud (delivered: cloud_only); the original status, outcome and links remain, and no job resumes.
cancel_job
ChatGPTCancel a queued or running job on its machine. Confirm with the person first.
delete_skill
ChatGPTRemove a skill from a machine's skills/ (moved to jobs/.removed-skills/ there, where it can be restored). Its webhook answers 404 from then on. Confirm with the person first.
describe_cloud
ChatGPTCall this first. The organisation, this key's scopes, its role and whose access it carries (acts_for: its creator, or null once they left); every machine it can see (status, mode, runners not ready); what needs a person now: agents waiting for an answer (with their question), open alerts, failing or warning health checks, jobs that failed and webhooks rejected in the last 24 hours; the day's numbers (jobs, cost, deliveries); and next_steps naming the tools that act on each.
disable_hosted_url
ChatGPTTurn a skill's hosted URL off: senders get 404 until it is turned on again, with a new URL. Confirm with the person first.
disconnect_machine
ChatGPTRevoke a machine's token and cancel its pending commands: it stops syncing at once. Its history stays; pairing again creates a new machine. Confirm with the person first.
dismiss_alert
ChatGPTResolve an open alert by hand (it opens again only if its condition clears and recurs). Alerts also resolve themselves: answering a waiting agent resolves its needs_human alert, and a later successful run of the same skill on the same machine resolves its earlier job_failed alerts.
enable_hosted_url
ChatGPTCreate a hosted URL for a machine's skill, or a new one: any previous URL for the skill stops working at once (update the sender).
get_command
ChatGPTA command's status and result; wait_seconds (up to 30) waits for it to finish.
get_delivery
ChatGPTOne webhook delivery: outcome and reason, HTTP status, sender, redacted headers, the job it started and, with include_body, the stored body.
get_feedback
ChatGPTOne item of the board by its number (12 or #12) or id: title, description (feature requests), status, votes, the comments (official: true marks the Skillhook team's response) and the timeline of status changes with the team's notes. This organisation's own issues also carry report (its dashboard link, request id and the context it was filed with).
get_hosted_url
ChatGPTThe hosted URL of a machine's skill, to configure in the webhook sender (GitHub, Sentry, Granola, Stripe…). The machine still checks every delivery's signature with the skill's own secret.
get_issue
ChatGPTOne report by number (12 or #12) or id, with its diagnostics and whether its emails went out.
get_job
ChatGPTA job as its page shows it: status, outcome, the agent's response and result excerpt, failure, cost and tokens, the pending question and answer, the progress timeline, the live output when it is being streamed (watch_job), artifacts fetched so far and the commands sent about it.
get_job_artifact
ChatGPTFetch one of a job's files from its machine: stdout or stderr (the agent's transcript), prompt (what it was told), result, response, payload or event (the webhook it got). Up to 256 KiB is returned (the end of stdout and stderr, the start of the others). Secrets are scrubbed on the machine; payload, event and prompt (which contain the webhook body) are withheld when the organisation keeps no bodies.
get_machine
ChatGPTOne machine as its page shows it: the link (last sync, clock skew, events waiting), its policy (mode, allow/deny lists), failing or warning health checks with their fix, runner readiness, skills (and those that failed to load), schedules, linked repositories, running jobs and a day of its own stats; for admin keys its skillhook.json as last reported.
get_settings
ChatGPTThe organisation (name, slug, plan) and its settings: whether webhook bodies are kept (store_payloads).
get_skill
ChatGPTA skill's summary and its SKILL.md fetched from the machine (the machine must be online). Edit the content and save it with save_skill.
get_stats
ChatGPTThe Stats page for every machine: per day of the window, jobs (succeeded, failed, needing a person), agent cost, tokens, p50/p95 duration and deliveries (accepted, rejected, skipped, via hosted URLs); totals with the success rate; and each skill's runs, failures, cost, p95 and last run.
list_alerts
ChatGPTConditions worth a person's attention, newest first: an agent waiting for a person (needs_human), a machine gone offline, a failed job, a failing health check. They resolve themselves when the condition clears. state: resolved lists recently resolved ones.
list_audit_log
ChatGPTEvery change and every command, by whom (person, API key, machine, system), newest first. Payloads, answers and file contents are never in it. action filters by an exact action or a prefix ending in a dot (command., machine., hosted_url.).
list_channels
ChatGPTWhere alerts are sent (Slack, webhook, email): which alert types, whether on, and the last delivery or error. Adding a channel is done on the dashboard.
list_commands
ChatGPTCommands sent to the machines (by people, keys and the cloud), newest first: type, status, who asked, the ids they were about and their error. get_command has a command's result.
list_deliveries
ChatGPTWebhooks the machines received, newest first, including rejected, skipped and duplicate ones with the reason. q searches the sender's delivery id, the machine's delivery id, the reason, the code, the path, the address and the user agent (case-insensitive, anywhere); since and until bound when it was received; delivery_id is the sender's id exactly, job the machine's id of the job it started. via: http came to the machine's own URL, ingress through a hosted URL. next_before pages.
list_feedback
ChatGPTThe public feedback board shared by every Skillhook organisation: feature requests and published issues with their status (open, planned, in_progress, done, declined, duplicate), votes and comment count. Search before filing (q), then upvote a match instead of filing a duplicate. status defaults to active (open, planned, in progress); all lists every status. viewer.voted says whether this organisation voted. next_cursor pages.
list_hosted_urls
ChatGPTHosted webhook URLs (the cloud receives the webhook and holds it, sealed, up to 72 hours until the machine collects it): per skill whether it is on, its key prefix, what it received and how many deliveries wait for the machine. Never the URL itself: get_hosted_url.
list_inbox
ChatGPTWhat the agents need from a person, what they are doing and what they did, as the dashboard's Inbox shows it. Per job: title (what the agent called it), state (needs_input, in_progress, done, failed), progress (message, percent, step, with recent_updates while it runs), headline (the result in one line), summary (Markdown), links (the event's source, pull requests, issues, messages, documents, deployments, how to test; plus the webhook delivery that started it) and, while it waits for a person, question {text, context, choices: {options, recommended, multiple}}. view: needs_input, in_progress, done, failed or all (default: needs_input when anyone waits, else all); sort: activity (latest first, the default), oldest (waiting longest), progress (furthest along) or created. counts gives how many wait and how many run. next_offset pages.
list_issues
ChatGPTProblems this organisation reported to the Skillhook team, newest first: number, title, description, kind, severity, status and its item on the feedback board (feedback.number for get_feedback).
list_jobs
ChatGPTJobs on every machine, newest first, with status (how the process ended), outcome (whether the task was done), failure kind, the pending question and cost. waiting: true lists only agents waiting for a person. next_before pages.
list_machines
ChatGPTEvery paired machine: status (online, degraded, offline), mode (observe = read-only, control = accepts actions), link state, runner readiness, health summary, skillhook version, last seen.
list_members
ChatGPTThe organisation's people, their roles (viewer, member, admin, owner) and teams (each person's, with member or maintainer), and the teams with their head counts; admin keys also see pending invitations and the teams they join. Inviting, removing, changing roles and team membership are done on the dashboard.
list_my_feedback
ChatGPTWhat this organisation filed (feature requests, and issues, which stay private to it and the Skillhook team) and the items it follows because it voted or commented, newest activity first.
list_reviews
ChatGPTPublished reviews of Skillhook with the team's response under each, and the aggregate (count, average, distribution of ratings). mine is this organisation's own review, whatever its status.
list_schedules
ChatGPTCloud-owned timers and their recent dispatch events, skips and command results. Timers fire from the Cloud tick, with no machine-owned schedule required.
list_skills
ChatGPTSkills on every machine (or one): runner, model, auth type and whether its secret is set, when-filters, schedule, whether webhooks reach it, its hosted URL (on/off, never the URL) and its last job.
pause_schedule
ChatGPTStop a skill's schedule on a machine from firing, without changing its repository: for a schedule from skillhook.yaml or a SKILL.md the machine keeps the pause (its webhook still works, slots that pass are not caught up, a repository pull or restart keeps it, until ends it by itself; needs skillhook 0.16 on the machine); for a Cloud timer it is disabled. reason says why, for whoever looks next. resume_schedule undoes it.
remove_feedback_vote
ChatGPTTake this organisation's vote off an item; its people stay subscribed only if they filed it or commented.
rename_machine
ChatGPTChange the name the cloud shows for a machine (its hostname stays what it reports).
replay_delivery
ChatGPTRun a stored delivery again through the skill as it is now. force is needed for deliveries that failed their checks (it skips them); skip_filters ignores the skill's when-filters. machine or skill run it elsewhere: the stored body and redacted headers go to that machine or skill as a fresh run, the way run_skill does (no signature check, no filters, so force and skip_filters do not apply); that needs the body to be stored (no_body otherwise).
replay_job
ChatGPTRun a job again with the same payload through the skill as it is now (a new job, trigger replay).
report_issue
ChatGPTFile a report with the Skillhook team after a failure, or when something in skillhook or Skillhook Cloud is wrong: say what happened, what you expected and how to reproduce it, name the machine, job or delivery it concerns, and pass request_id (the x-request-id of a failed API call) and context (ids, versions, error codes). Similar open items come back first (created: false, similar): upvote a match with upvote_feedback; force: true files anyway. Reports stay private to this organisation and the team (list_issues, get_feedback), are acknowledged by email (contact_email, else the person who created this API key), routed to the team, and every status change is emailed. Returns its number and dashboard link.
request_feature
ChatGPTAsk for something skillhook or Skillhook Cloud should do, when the person wishes the product did something it does not. Similar requests come back first (created: false, similar): upvote the one that matches with upvote_feedback instead; force: true files anyway. A new request is public on the board with this organisation's vote, and its author is thanked by email and told about every status change.
resume_schedule
ChatGPTLet a paused schedule fire again from its next slot (slots that passed while paused are not caught up), whether the machine fires it from its repository or it is a Cloud timer.
run_skill
ChatGPTRun an installed skill on a machine as if a webhook arrived with this payload (no signature check, no filters). wait_seconds waits for the job to finish or to ask a person.
save_schedule
ChatGPTCreate or update a named Cloud-owned schedule on a machine. Remove the local schedule before enabling it. Five-field cron and IANA timezone; missed slots and overlapping jobs are skipped. Saving with enabled=false pauses it.
save_skill
ChatGPTWrite skills/<skill>/SKILL.md on a machine, creating or replacing it; the machine validates it first and answers with the error when it is invalid. Not for hooks from a linked repository (change those in the repository). auth: none needs allow_unauthenticated. No secret is created: use the dashboard or skillhook cloud secret for that. Try a draft with test_skill first.
submit_review
ChatGPTPost this organisation's public review of Skillhook (one per organisation; posting again edits it, at most once an hour, earlier versions are kept): rating 1-5 and, if the person wants, a title, what they like and dislike, their use case and the name to show. Only post what the person said; never invent a rating. marketing_consent: true only when they agree to be quoted.
test_channel
ChatGPTSend a sample alert to a channel and record whether it arrived.
test_skill
ChatGPTRun a SKILL.md once on a machine without installing it (trigger test), to try a skill before save_skill.
update_settings
ChatGPTRename the organisation or change whether the cloud keeps webhook bodies the machines upload (store_payloads: false keeps none from now on).
upvote_feedback
ChatGPTVote for an item on the board as this organisation (one vote per organisation): votes decide what is built and fixed first. The person behind this key is subscribed and thanked by email. Voting twice keeps one vote.
watch_job
ChatGPTStream a running job's stdout (or stderr) to the cloud for ttl_seconds (default 900); get_job then shows it as output, refreshed every few seconds.