Publish with Shipvela
Stage a static site or deploy a connected GitHub project through Shipvela, then verify the exact job.
Overview
Publish with Shipvela gives an agent a workflow for choosing a deployment path and checking the result. The skill distinguishes a small prebuilt static upload from building a connected GitHub branch. It tells the agent to identify the intended project, preserve a request identifier on retry and check the provider’s result for that exact deployment before reporting a live URL.
Getting started
Install the named skill in a compatible host and use it with the intended Shipvela account and MCP connection. A GitHub deployment also needs the repository already connected to Shipvela.
Things to know
A static upload has file-count and size limits and requires the owner to review the staged files. The GitHub path builds the remote branch. The skill directs larger local builds to a separate workflow.
Skill instructions
Sources and documentation
Related MCP servers and skills
- Integrate MCP with GitHub CopilotMCP server
- ctx: The missing link between your codebase and your LLM. Context as Code (CaC) tool with MCP server inside.MCP server
- Working With PostHog SkillsAgent skill
- Work With AlloyMCP server
- Source Code to Knowledge Base Generator with MCP ServerAgent skill
- Planning With FilesAgent skill