edgeone-pages-deploy

Included with Lifetime

$97 forever

Deploys static HTML to a public URL instantly with no authentication required. Use when asked to "host this", "deploy this site", "get a public link", "share this HTML", "quick deploy", "publish this page", or any request to make an HTML file publicly accessible via URL. Supports self-contained HTML files with inline CSS/JS.

Web Devscripts

What this skill does


# EdgeOne Pages Deploy

Deploy any HTML file or directory to a public URL in seconds. No authentication, no accounts, no configuration.

## Quick Deploy

```bash
# Single HTML file
scripts/deploy.sh path/to/index.html

# Directory containing index.html
scripts/deploy.sh path/to/site/
```

Returns a public URL like `https://mcp.edgeone.site/share/abc123`.

## How It Works

Uses EdgeOne Pages' public MCP endpoint to deploy HTML content via JSON-RPC.

- **Endpoint:** `https://mcp-on-edge.edgeone.app/mcp-server`
- **Method:** `tools/call` → `deploy-html`
- **Auth:** None required

## Manual Deploy (curl)

```bash
HTML=$(python3 -c 'import sys,json; print(json.dumps(sys.stdin.read()))' < index.html)

curl -s -X POST https://mcp-on-edge.edgeone.app/mcp-server \
  -H "Content-Type: application/json" \
  -d "{\"jsonrpc\":\"2.0\",\"id\":1,\"method\":\"tools/call\",\"params\":{\"name\":\"deploy-html\",\"arguments\":{\"value\":$HTML}}}"
```

## Validation

After deploying, SHOULD verify the URL returns HTTP 200:

```bash
curl -s -o /dev/null -w "%{http_code}" <returned-url>
```

## Constraints

- Single HTML file only — multi-file sites with separate CSS/JS/images are NOT supported
- Self-contained HTML works best (inline styles, inline scripts, base64 images)
- No custom domains
- No delete/update — each deploy creates a new URL
- Link persistence depends on EdgeOne's retention policy

## Requirements

- `curl`
- `python3` (for JSON encoding)

Files: 2

Size: 3.2 KB

Complexity: 30/100

Category: Web Dev

Source: https://github.com/0juano/agent-skills/tree/main/edgeone-pages-deploy

Related in Web Dev

generating-lwc-components

Included

Lightning Web Components with PICKLES methodology and 165-point scoring. Use this skill when the user creates or edits LWC components, builds wire service patterns, or writes Jest tests for LWC. TRIGGER when: user creates/edits LWC components, touches lwc/**/*.js, .html, .css, .js-meta.xml files, or asks about wire service, SLDS, or Jest LWC tests. DO NOT TRIGGER when: Apex classes (use generating-apex), Aura components, or Visualforce.

Web Devscripts

tanstack-query

Included

Manage server state in React with TanStack Query v5. Set up queries with useQuery, mutations with useMutation, configure QueryClient caching strategies, implement optimistic updates, and handle infinite scroll with useInfiniteQuery. Use when: setting up data fetching in React projects, migrating from v4 to v5, or fixing object syntax required errors, query callbacks removed issues, cacheTime renamed to gcTime, isPending vs isLoading confusion, keepPreviousData removed problems.

Web Devscripts

document-processor-api

Included

Process documents with Nutrient DWS. Use when the user wants to generate PDFs from HTML or URLs, convert Office/images/PDFs, assemble or split packets, OCR scans, extract text/tables/key-value pairs, redact PII, watermark, sign, fill forms, optimize PDFs, or produce compliance outputs like PDF/A or PDF/UA. Triggers include convert to PDF, merge these PDFs, OCR this scan, extract tables, redact PII, sign this PDF, make this PDF/A, or linearize for web delivery.

Web Devscripts

nutrient-document-processing

Included

Web Devscripts

tanstack-query

Included

Manage server state in React with TanStack Query v5. Covers useMutationState, simplified optimistic updates, throwOnError, network mode (offline/PWA), and infiniteQueryOptions. Use when setting up data fetching, fixing v4→v5 migration errors (object syntax, gcTime, isPending, keepPreviousData), or debugging SSR/hydration issues with streaming server components.

Web Devscripts

accelint-nextjs-best-practices

Included

Next.js performance optimization and best practices. Use when writing Next.js code (App Router or Pages Router); implementing Server Components, Server Actions, or API routes; optimizing RSC serialization, data fetching, or server-side rendering; reviewing Next.js code for performance issues; fixing authentication in Server Actions; or implementing Suspense boundaries, parallel data fetching, or request deduplication.

Web Devscripts