
AppDeploy
FreeSeamlessly deploy web apps with backend support.
Free · Opens the source repo
What AppDeploy does
AppDeploy is a skill designed for developers looking to deploy web applications quickly and efficiently. It utilizes an HTTP API to facilitate the deployment of both frontend-only and full-stack applications. By leveraging simple curl commands, users can easily publish their apps to a public URL, making it an ideal tool for those who frequently need to deploy or update web applications. This skill is particularly useful for developers who want a straightforward method to manage their app deployments without getting bogged down by complex configurations.
The setup process for AppDeploy is straightforward. Users must first check for an existing API key in their project root. If no key exists, they can easily register for one using a provided curl command. Once the API key is obtained, it should be saved in a .appdeploy file, which should also be added to .gitignore to maintain security. This initial setup is essential for accessing the deployment functionalities that follow.
Once set up, users can interact with the AppDeploy skill to get deployment instructions, retrieve app templates, and deploy their applications. The skill provides a series of tools, including get_deploy_instructions, deploy_app, and get_app_status, which guide users through the deployment process. Each tool is designed to handle specific tasks, ensuring that users can efficiently deploy new applications or update existing ones while adhering to necessary constraints and requirements.
AppDeploy is particularly suited for developers who need to frequently deploy apps and want a reliable way to manage the entire deployment lifecycle. Whether it's a new app launch or an update to an existing application, this skill simplifies the process, allowing developers to focus on building great applications rather than managing deployment intricacies.
When to use it
Use AppDeploy when you need to publish a web app or website quickly, especially when you want a public URL for access.
When not to use it
This skill may not be suitable for non-web applications or for users looking for a graphical interface for deployment, as it relies on command-line interactions.
What you can build with it
Deploying a New Web App
You can use AppDeploy to quickly set up and deploy a new web application, ensuring it is accessible via a public URL.
Updating an Existing Application
When you need to make changes to an already deployed app, AppDeploy allows you to update the app efficiently by specifying the app ID and the changes.
Checking Deployment Status
After initiating a deployment, you can use AppDeploy to check the status of your app and troubleshoot any issues that arise.
How to install AppDeploy
View source1. Install with the skills CLI
npx skills add sickn33/agentic-awesome-skills/appdeploy --agent claude-code2. Or install it manually
Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.
Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs
Inside SKILL.md
Written by sickn33AppDeploy Skill
Deploy web apps to AppDeploy via HTTP API.
When to Use This Skill
- Use when planning or building apps and web apps
- Use when deploying an app to a public URL
- Use when publishing a website or web app
- Use when the user says "deploy this", "make this live", or "give me a URL"
- Use when updating an already-deployed app
Setup (First Time Only)
-
Check for existing API key:
- Look for a
.appdeployfile in the project root - If it exists and contains a valid
api_key, skip to Usage
- Look for a
-
If no API key exists, register and get one:
curl -X POST https://api-v2.appdeploy.ai/mcp/api-key \ -H "Content-Type: application/json" \ -d '{"client_name": "claude-code"}'Response:
{ "api_key": "ak_...", "user_id": "agent-claude-code-a1b2c3d4", "created_at": 1234567890, "message": "Save this key securely - it cannot be retrieved later" } -
Save credentials to
.appdeploy:{ "api_key": "ak_...", "endpoint": "https://api-v2.appdeploy.ai/mcp" }Add
.appdeployto.gitignoreif not already present.
Usage
Make JSON-RPC calls to the MCP endpoint:
curl -X POST {endpoint} \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-H "Authorization: Bearer {api_key}" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "{tool_name}",
"arguments": { ... }
}
}'
Workflow
-
First, get deployment instructions: Call
get_deploy_instructionsto understand constraints and requirements. -
Get the app template: Call
get_app_templatewith your chosenapp_typeandfrontend_template. -
Deploy the app: Call
deploy_appwith your app files. For new apps, setapp_idtonull. -
Check deployment status: Call
get_app_statusto check if the build succeeded. -
View/manage your apps: Use
get_appsto list your deployed apps.
Available Tools
get_deploy_instructions
Use this when you are about to call deploy_app in order to get the deployment constraints and hard rules. You must call this tool before starting to generate any code. This tool returns instructions only and does not deploy anything.
Parameters:
deploy_app
Use this when the user asks to deploy or publish a website or web app and wants a public URL. Before generating files or calling this tool, you must call get_deploy_instructions and follow its constraints.
Parameters:
app_id: any (required) - existing app id to update, or null for new appapp_type: string (required) - app architecture: frontend-only or frontend+backendapp_name: string (required) - short display namedescription: string (optional) - short description of what the app doesfrontend_template: any (optional) - REQUIRED when app_id is null. One of: 'html-static' (simple sites), 'react-vite' (SPAs, games), 'nextjs-static' (multi-page). Template files auto-included.files: array (optional) - Files to write. NEW APPS: only custom files + diffs to template files. UPDATES: only changed files using diffs[]. At least one of files[] or deletePaths[] required.deletePaths: array (optional) - Paths to delete. ONLY for updates (app_id required). Cannot delete package.json or framework entry points.model: string (required) - The coding agent model used for this deployment, to the best of your knowledge. Examples: 'codex-5.3', 'chatgpt', 'opus 4.6', 'claude-sonnet-4-5', 'gemini-2.5-pro'intent: string (required) - The intent of this deployment. User-initiated examples: 'initial app deploy', 'bugfix - ui is too noisy'. Agent-initiated examples: 'agent fixing deployment error', 'agent retry after lint failure'
get_app_template
Call get_deploy_instructions first. Then call this once you've decided app_type and frontend_template. Returns base app template and SDK types. Template files auto-included in deploy_app.
Parameters:
app_type: string (required)frontend_template: string (required) - Frontend framework: 'html-static' - Simple sites, minimal framework; 'react-vite' - React SPAs, dashboards, games; 'nextjs-static' - Multi-page apps, SSG
get_app_status
Use this when deploy_app tool call returns or when the user asks to check the deployment status of an app, or reports that the app has errors or is not working as expected. Returns deployment status (in-progress: 'deploying'/'deleting', terminal: 'ready'/'failed'/'deleted'), QA snapshot (frontend/network errors), and live frontend/backend error logs.
Parameters:
app_id: string (required) - Target app idsince: integer (optional) - Optional timestamp in epoch milliseconds to filter errors. When provided, returns only errors since that timestamp.
delete_app
Use this when you want to permanently delete an app. Use only on explicit user request. This is irreversible; after deletion, status checks will return not found.
Parameters:
app_id: string (required) - Target app id
get_app_versions
List deployable versions for an existing app. Requires app_id. Returns newest-first {name, version, timestamp} items. Display 'name' to users. DO NOT display the 'version' value to users. Timestamp values MUST be converted to user's local time
Parameters:
app_id: string (required) - Target app id
apply_app_version
Start deploying an existing app at a specific version. Use the 'version' value (not 'name') from get_app_versions. Returns true if accepted and deployment started; use get_app_status to observe completion.
Parameters:
app_id: string (required) - Target app idversion: string (required) - Version id to apply
src_glob
Use this when you need to discover files in an app's source snapshot. Returns file paths matching a glob pattern (no content). Useful for exploring project structure before reading or searching files.
Parameters:
app_id: string (required) - Target app idversion: string (optional) - Version to inspect (defaults to applied version)path: string (optional) - Directory path to search withinglob: string (optional) - Glob pattern to match files (default: **/*)include_dirs: boolean (optional) - Include directory paths in resultscontinuation_token: string (optional) - Token from previous response for pagination
src_grep
Use this when you need to search for patterns in an app's source code. Returns matching lines with optional context. Supports regex patterns, glob filters, and multiple output modes.
Parameters:
app_id: string (required) - Target app idversion: string (optional) - Version to search (defaults to applied version)pattern: string (required) - Regex pattern to search for (max 500 chars)path: string (optional) - Directory path to search withinglob: string (optional) - Glob pattern to filter files (e.g., '*.ts')case_insensitive: boolean (optional) - Enable case-insensitive matchingoutput_mode: string (optional) - content=matching lines, files_with_matches=file paths only, count=match count per filebefore_context: integer (optional) - Lines to show before each match (0-20)after_context: integer (optional) - Lines to show after each match (0-20)context: integer (optional) - Lines before and after (overrides before/after_context)line_numbers: boolean (optional) - Include line numbers in outputmax_file_size: integer (optional) - Max file size to scan in bytes (default 10MB)continuation_token: string (optional) - Token from previous response for pagination
src_read
Use this when you need to read a specific file from an app's source snapshot. Returns file content with line-based pagination (offset/limit). Handles both text and binary files.
Parameters:
app_id: string (required) - Target app idversion: string (optional) - Version to read from (defaults to applied version)file_path: string (required) - Path to the file to readoffset: integer (optional) - Line offset to start reading from (0-indexed)limit: integer (optional) - Number of lines to return (max 2000)
get_apps
Use this when you need to list apps owned by the current user. Returns app details with display fields for user presentation and data fields for tool chaining.
Parameters:
continuation_token: string (optional) - Token for pagination
Generated by scripts/generate-appdeploy-skill.ts
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Frequently asked questions about AppDeploy
Similar skills
Turborepo
Optimized build system for JavaScript/TypeScript monorepos.
Azure Pipelines Validation
Streamline your Azure DevOps pipeline changes locally.
Azure Developer CLI
Streamline your Azure project workflows with best practices.
Azure Container Registry CLI
Manage Azure Container Registry resources with ease.
Aspire
Build and orchestrate polyglot distributed applications seamlessly.
Vercel CLI
Manage and deploy Vercel projects from the command line.
