walrus-sites

Publish and update decentralized static websites on Walrus Sites with a testnet portal.

10|5|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/MystenLabs/skills --skill walrus-sites
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: walrus-sites
Source: https://github.com/MystenLabs/skills/tree/main/walrus-sites
Command: npx skills add https://github.com/MystenLabs/skills --skill walrus-sites

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Walrus Sites complex publishing and troubleshooting for decentralized web frontends, including testnet portal setup, SPA routing issues, and site lifecycle problems like expired blobs or broken deployments.

Core Features & Use Cases

  • Deploy and update decentralized websites: Publish a built frontend to Walrus Sites, update an existing deployment in place, configure resource routing, and manage site object lifecycle (update, destroy, extend storage).
  • Run a local portal for testnet: Self-host the Walrus Sites portal, configure the required original_package_id correctly, and resolve portal 404s and startup issues like port conflicts.
  • Debug reliability failures: Diagnose common failures such as blob expiration (leading to 404), incorrect portal configuration, SPA client-side routing misconfiguration, and resource listing/expiration via sitemap.

Quick Start

Run the local portal for testnet after publishing, then open your site URL and verify resources load correctly.

Frequently Asked Questions about walrus-sites

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

FAQPage Schema
How do I deploy a decentralized static website to Walrus Sites?

To deploy a decentralized static website to Walrus Sites, use site-builder to publish your built frontend with appropriate epochs and configure ws-resources.json. Manage the site object lifecycle to update, destroy, or extend storage as needed.

Why does my Walrus Sites portal return a 404 error?

Walrus Sites portal 404 errors are typically caused by blob expiration, incorrect original_package_id configuration for site::Site, or SPA routing misconfiguration. Diagnose the issue by verifying portal configuration and checking resource expiration via the sitemap.

How do I configure SPA client-side routing for a decentralized web frontend?

SPA client-side routing for decentralized web frontends is configured within the ws-resources.json file. Proper configuration ensures the Walrus Sites portal correctly resolves client-side routes and serves appropriate headers without 404 errors.

How do I run a local portal for Walrus Sites testnet debugging?

Run a local portal for Walrus Sites testnet debugging by self-hosting the portal and configuring the correct original_package_id. This testnet-ready environment allows you to verify that resources load correctly and resolve startup issues like port conflicts.

How does portal URL resolution work for Walrus site object IDs?

Portal URL resolution for Walrus site object IDs works by converting the site object ID into a base36 format. This base36 representation is used by the portal to resolve and serve the correct decentralized website.

What causes blob expiration in Walrus Sites and how do I fix it?

Blob expiration in Walrus Sites occurs when the storage epoch for a published resource expires, leading to 404 errors. Fix it by using site-builder to update the deployment with appropriate extended epochs to restore resource availability.