Wrap a skill in a URL
Build-along · ~15 min at your own keyboard
A skill on your laptop helps you; a skill behind a URL helps your whole crew. Serverless platforms (Modal and friends) turn a script into a web endpoint in minutes — the course demo wrapped a lead-scraper into a form URL returning a CSV. A URL is reachable by anyone who finds it, so decide who may use it BEFORE you deploy: what data it touches, who gets access and how, and a limit on how often it can be called. Test with made-up data first.
The long version: Skills as web endpoints ↗
Do this
0/4Checkpoints
- ▸You should now see a written access plan before you deploy.
- ▸You should now see your script deployed as an endpoint with a URL and an access check.
- ▸You should now see the output arriving in your phone's browser.
- ▸You should now see the endpoint refuse a call without access.
The three ways this goes wrong
- The endpoint returns a server error. — Open the platform's function log and read the last error. Paste it to Claude.
- It works locally and not when deployed. — A file or package is missing from the deploy. Ask Claude to list what the function needs.
- Anyone who finds the link can run it. — Take it down until access is in place. A key typed into a web page can be read by anyone who opens the page — use the platform's login, or check the key on the server.
Share what happened
Paste your access plan, the endpoint's job, proof of a phone-side call with made-up data, and the result of the no-access test.
Strip API keys, passwords, and tokens before you paste. Swap them for [KEY].
🔒 Don't paste confidential, personal-health, or payment info.