neynar-deploy

Deploys tar.gz archives as Turso-backed apps with a single API call.

10|1|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/neynarxyz/neynar-deploy --skill neynar-deploy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: neynar-deploy
Source: https://github.com/neynarxyz/neynar-deploy/tree/main
Command: npx skills add https://github.com/neynarxyz/neynar-deploy --skill neynar-deploy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the friction of publishing and updating websites by turning a project archive into a live, versioned deployment with minimal setup. It is designed for fast website launches, safe updates, instant rollbacks, and lightweight operational checks without relying on git workflows or a dashboard.

Core Features & Use Cases

  • Single-call deployment: Upload a tar.gz archive and publish static sites, Vite apps, Hono apps, or Next.js apps to a live URL.
  • Versioned hosting: Every deploy gets a version history, making it easy to inspect prior releases and roll back when something breaks.
  • Operational visibility: Retrieve project context, deployment status, logs, analytics, and source archives for ongoing maintenance.
  • Use case: A developer or AI agent can ship a new landing page, update an existing app, and confirm the canonical host.neynar.app URL is live in one workflow.

Quick Start

Ask the agent to package your site, deploy it as a named project, and return the live host.neynar.app URL.

Frequently Asked Questions about neynar-deploy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy a Next.js or Vite app to a live URL without using git workflows?

Deploy a static site, Vite, Hono, or Next.js app by uploading a tar.gz archive via a single API call to generate a live hosted URL. The system polls the build status until the deployment is ready or encounters an error.

Can I roll back a website deployment to a previous version through an API?

Yes, every deployment is versioned, allowing you to inspect prior releases and execute an instant rollback via API when a site update breaks. This removes the friction of manual recovery operations.

What is the best way to package a web project for API-driven hosting?

The best way to package a web project for API-driven hosting is to compress it into a tar.gz archive. You must then deploy this archive as a named project to generate a live canonical host.neynar.app URL.

Does API-driven deployment support operational checks like retrieving deployment logs and analytics?

Yes, API-driven deployment supports operational visibility by allowing you to retrieve project context, deployment status, logs, analytics, and source archives. This provides lightweight operational checks for ongoing maintenance.

How do AI agents handle autonomous website publishing and build status polling?

AI agents handle autonomous website publishing by making a single API call with a tar.gz archive to deploy a named project. The system automatically polls the build status until the canonical URL is ready or an error occurs.