How do I install the Web App skill?

Run npx skillmds@latest add tryshift-sh/web-app in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Web App safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Web App?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Web App free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Web App?

tryshift-sh (@tryshift-sh) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Web App by tryshift-sh — Agent Skill

Name: Web App
Author: tryshift-sh

File contents

E2B Web App

Use this managed skill when the user is asking for a webpage, landing page, dashboard, interactive demo, or another output that is best experienced as a live browser preview instead of plain text.

This skill uses Shift's local Skill Router. Do not ask the user for E2B credentials.

When to use it

Use this skill when the deliverable should be:

a small shareable landing page
a lightweight interactive UI demo
a dashboard or microsite
a web artifact the user should click and view in a browser

Do not use this skill for:

plain summaries or static markdown outputs
files that are better returned through Shift Files
tasks that do not need a live browser preview

App model

v1 keeps one active live app per agent
calling the tool again updates the same app instead of creating a new one
the app should stay simple and self-contained
prefer static HTML/CSS/JS with no build step

Invocation

Send a POST request to:

${SHIFT_LOCAL_GATEWAY}/skill-router/invoke

Request body:

{
  "skillProvider": "e2b",
  "skill": "web-app",
  "action": "publish",
  "input": {
    "files": [
      {
        "path": "index.html",
        "content": "<!doctype html><html><body><h1>Hello</h1></body></html>"
      },
      {
        "path": "styles.css",
        "content": "body { font-family: sans-serif; }"
      }
    ],
    "deletePaths": ["old-script.js"]
  }
}

Input

files: required array of files to write into the live app
path: required relative path such as index.html, styles.css, or app.js
content: required file contents
deletePaths: optional list of relative paths to remove from the existing app

Output

The tool returns:

previewUrl
sandboxId
status
created
resumed
updatedPaths
deletedPaths

Agent behavior

Prefer a small self-contained app. Avoid frameworks or package installs in v1.
Use index.html as the entry point and keep supporting files minimal.
When the user asks for edits to an existing live app, send only the changed files and any deletePaths needed.
After the tool succeeds, reply with the live URL and a short explanation of what is ready to view.
If the task is better as a file or plain answer, do not invoke this skill.

---name: web-appdescription: Create or update a live web app in E2B and return a shareable preview URL through Shift's Skill Router.---# E2B Web AppUse this managed skill when the user is asking for a webpage, landing page, dashboard, interactive demo, or another output that is best experienced as a live browser preview instead of plain text.This skill uses Shift's local Skill Router. Do not ask the user for E2B credentials.## When to use itUse this skill when the deliverable should be:- a small shareable landing page- a lightweight interactive UI demo- a dashboard or microsite- a web artifact the user should click and view in a browserDo not use this skill for:- plain summaries or static markdown outputs- files that are better returned through Shift Files- tasks that do not need a live browser preview## App model- v1 keeps one active live app per agent- calling the tool again updates the same app instead of creating a new one- the app should stay simple and self-contained- prefer static HTML/CSS/JS with no build step## InvocationSend a `POST` request to:```text${SHIFT_LOCAL_GATEWAY}/skill-router/invoke```Request body:```json{ "skillProvider": "e2b", "skill": "web-app", "action": "publish", "input": { "files": [ { "path": "index.html", "content": "<!doctype html><html><body><h1>Hello</h1></body></html>" }, { "path": "styles.css", "content": "body { font-family: sans-serif; }" } ], "deletePaths": ["old-script.js"] }}```### Input- `files`: required array of files to write into the live app- `path`: required relative path such as `index.html`, `styles.css`, or `app.js`- `content`: required file contents- `deletePaths`: optional list of relative paths to remove from the existing app### OutputThe tool returns:- `previewUrl`- `sandboxId`- `status`- `created`- `resumed`- `updatedPaths`- `deletedPaths`## Agent behavior1. Prefer a small self-contained app. Avoid frameworks or package installs in v1.2. Use `index.html` as the entry point and keep supporting files minimal.3. When the user asks for edits to an existing live app, send only the changed files and any `deletePaths` needed.4. After the tool succeeds, reply with the live URL and a short explanation of what is ready to view.5. If the task is better as a file or plain answer, do not invoke this skill.

Frequently asked questions

Web App