Customers
What people run on Skillhook Cloud
Short, technical stories: the situation, how a webhook becomes an agent's job, the prompt that sets it up with your own agent, the SKILL.md, and where a person comes in. One is our own loop; the others are worked playbooks, labelled as such. No testimonials, no invented numbers.
Our own use
A Sentry alert posts to a hosted URL. The machine collects it, the skill finds the cause, lands a small tested fix through a pull request, checks it in production, and asks a person only for what is theirs.
Trigger
A Sentry alert, and a sweep every three hours
Lands alone
A small fix with a test that failed before it
Asks a person for
Migrations, environment, billing, the loop itself
Hosted URLSchedulesInboxAlertsJobs
A worked playbook
Notes become actionable tasks. Your agent starts authorized work, reports what it completed and what is still running, and pauses for your input or approval. See an illustrative ten-task recap and the Granola notes and follow-ups playbook.
Trigger
Granola's note.generated webhook
Before sending
Approve the draft and exact recipients
Asks a person when
An owner or a due date is unclear
Hosted URLInboxDeliveriesJobs
A worked playbook
Every new issue gets a run. A small, well-specified one gets a fix on a branch and a pull request; the rest get a triage comment with findings and questions. Design questions go to a person, and nothing merges without one.
Trigger
GitHub's issues webhook, action opened
Merges
Nothing without a person
Asks a person for
Design questions, with the options as buttons
Hosted URLInboxReplayJobs
A worked playbook
A customer writes in. The skill looks at the logs, Sentry and the database before it drafts an answer; it replies through Intercom when the answer is certain, and otherwise leaves an internal note and asks a person in the inbox: send the draft, edit it, or escalate.
Trigger
Intercom's conversation webhooks
Replies alone when
The answer is certain from what it found
Otherwise
An internal note, and the draft as a choice in the inbox
Hosted URLInboxAlertsJobs
A worked playbook
A dispute arrives with a deadline. The skill collects the customer, the invoices, the access and usage logs, the correspondence and the delivery records, writes the evidence up, submits it through the API when it is complete, and asks a person first when it is thin or the amount is large.
Trigger
Stripe's charge.dispute.created event
Submits alone when
The evidence is complete and the amount small
Asks a person when
The evidence is thin or the amount is large
Hosted URLInboxAlertsReplay
A worked playbook
A new lead gets a first reply with real context about what they asked. Every later message in the thread gets an answer, deduplicated by message id, the CRM is updated, and a person is asked before any pricing exception, promise or legal question. It stops when a person says so.
Trigger
A form, CRM or inbound-email webhook
Deduplicated by
The message id, in skillhook and in the CRM
Asks a person before
Pricing exceptions, promises and legal questions
Hosted URLInboxDeliveriesAlerts
A worked playbook
Every webhook a machine received is on record in the cloud, with the reason when it did not run. Filter them, replay one through the skill as it is now, run its body on another machine or skill, send it to any other location from the CLI, and test a SKILL.md before it is saved.
On record
Every delivery, with its outcome and reason
Body kept
7 to 365 days, by plan
Replay
As the skill is now; force and skip_filters when needed
DeliveriesReplayCLIMCPPlayground
Running something on Skillhook Cloud and willing to be named? Write to support@skillhook.dev. We publish the setup and quote you only in words you approve in writing.