Sandbox execution

Skills can declare hosted scripts under scripts/. The runtime (local, sandbox, or container) is derived from the bundle — see how the runtime is chosen. Skillist runs sandbox and container skills in isolated sandboxes on the API worker.

Requirements

• Signed-in Skillist account
• Membership of the org that owns the skill — or, for a public skill, an owner who has opted in to outside runs

Anonymous sandbox runs return 401 Unauthorized.

Running someone else’s public skill

Public governs who can read a skill, not who can run it at the owner’s expense: a run spends the owning org’s run quota and sandbox compute. So by default only that org’s own members and API keys can run its public skills, and everyone else gets 403 Forbidden.

An org can open its public skills to outside callers with Allow other organizations to run this org’s public skills in Settings → execution policy (allowPublicRuns). It is off by default. Turning it on means outside runs draw on your quota, so pair it with the run limits on the same screen.

API keys need the skills:run scope either way; a skills:read key can never trigger a run.

CLI

skillist run skillist/web-perf-audit --script scripts/audit

Web UI

Skill detail pages include a Run card when the skill has sandbox scripts. Sign in to enable the run button.

API

POST https://skillist.io/{org}/{repo}/run
GET  https://skillist.io/{org}/{repo}/scripts
GET  https://skillist.io/{org}/{repo}/runs

Same paths work on api.skillist.io. Requires session auth or API key. See API docs for request body and streaming responses.

See also Delivery URLs for the full apex path map.

Output

Runs stream stdout/stderr over SSE. History is available in the dashboard for authenticated users.

Policy

Org admins can configure execution policy (quotas, allowed runtimes) in governance settings.