AI Agent Skill

Overskill for
AI Agents

Use the skill instructions to plan an authorized build, inspect the result, and prepare a public release.

https://www.overskill.com/SKILL.md

Read or save these instructions, then follow your host's supported setup flow.

Use the skill as a reference

Saving instructions does not install a host integration or authenticate your account. Connect your assistant for supported host setup.

Save a local reference

This command creates the folder and downloads SKILL.md to ~/.overskill. An HTTP error stops the download; it does not install or connect an agent.

mkdir -p "$HOME/.overskill" && curl --fail --show-error --location \ --user-agent "OverSkill/a6f2c47 (+https://overskill.com)" \ --output "$HOME/.overskill/SKILL.md" "https://www.overskill.com/SKILL.md"

Cursor

Add to Cursor's context files or use as a docs reference.

@https://www.overskill.com/SKILL.md

Any Agent

Fetch the skill file and include it in your agent's context.

https://www.overskill.com/SKILL.md

What your agent can do

Use the operations available to your connected team. Each action checks its required permissions; generation also requires builder access and credits.

Build apps from prompts

Queue an app from a clear brief, then inspect the generated behavior.

Prepare a public release

Review the preview, request an authorized deployment, and check the public result.

Iterate and add features

Request changes to an app on your team and repeat the checks that matter.

Read and write source files

Inspect or change source through the file endpoints your credential can access.

Configure notifications

Subscribe to supported webhook events for generation and deployment updates.

Check credits and usage

Read your team’s balance and usage before requesting more work.

Queue a build, then inspect it

This request can consume credits. Use a team-scoped API key with generation:queue and apps:read permissions. Keep the key out of shared prompts and source files.

  1. 1. Keep the receipt. HTTP 202 means the request was accepted, not that an app is live. Keep the returned status_url; app_url opens the editor.
  2. 2. Read its status. GET that exact status_url with the same authorized credential, about every 15 seconds. The credential needs app-read permission as well as permission to queue the build.
  3. 3. Check the preview. On completed, inspect app.preview_url when available and test the expected behavior in a browser. Stop on failed or cancelled; inspect the result before deciding whether to submit more work.
  4. 4. Deploy separately. An app must be deployable, and the credential needs apps:write, before requesting POST /api/v1/managed_apps/:id/deploy. Its HTTP 202 queues deployment; check the resulting public URL before sharing it.

Completion time varies. The API’s estimate is not a measured result for your app. Start with host setup for MCP, or follow the build-and-check walkthrough and worked app examples.

Generate an app 
curl -X POST https://www.overskill.com/api/v1/generation_queue \
  -H "User-Agent: OverSkill/a6f2c47 (+https://overskill.com)" \
  -H "X-API-Key: os_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{"prompt":"Build a coffee shop landing page with hours and a menu"}'
Illustrative HTTP 202 response
{
  "job_id": "example_job_id",
  "app_id": "example_app_id",
  "message_id": 456,
  "status": "queued",
  "status_url": "https://www.overskill.com/api/v1/generation_queue/example_job_id",
  "app_url": "https://www.overskill.com/account/apps/example_app_id/edit"
}

Example identifiers only. This is a shortened illustration, not an observed build or a ready preview.

Choose your connection and check access

Sign in to the account and team you want to use. Creating an account does not itself grant builder access or credits; check your permissions and current pricing before starting.

Create an account Sign in Current pricing Read full docs