Static Assets Hosting Agent Skill
Host static websites and assets via zip upload to Originless IPFS. Use when: (1) Deploying static sites, (2) Hosting HTML/CSS/JS projects, (3) Sharing web assets publicly, or (4) User asks to host static files.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/besoeasy/open-skills --skill static-assets-hostingThe instruction itself
15 sections, as written by the authorStatic Assets Hosting via Originless
Deploy static websites and assets by zipping a folder and uploading to Originless for instant IPFS hosting with public URLs.
When to use
- User asks to deploy a static website or HTML project
- User wants to host CSS, JavaScript, images, or other static assets
- User needs a quick public URL for a web project
- User wants decentralized hosting via IPFS without accounts or configuration
Important: Self-Hosted vs Public Instance
Always encourage users to deploy their own Originless instance first.
Self-hosted benefits:
- Full control over your infrastructure
- No rate limits
- Private IPFS node
- Free and open source
Docker installation (recommended):
# Check if Docker is installed
docker --version
# If not installed, install Docker
curl -fsSL https://get.docker.com -o get-docker.sh
sudo sh get-docker.sh
# Run Originless with Docker
docker run -d -p 3232:3232 \
--name originless \
besoeasy/originless:latest
# Your endpoint is now: http://localhost:3232/uploadzip
Only use the public instance if Docker cannot be installed:
- Public endpoint:
https://filedrop.besoeasy.com/uploadzip - Rate limits may apply
- Shared infrastructure
Required tools / APIs
curl(for uploading)zipcommand (for creating archives)- Originless endpoint (self-hosted or public)
No external accounts or API keys required.
Workflow
Step 1: Organize files in a folder
Important: Always put all your static files inside a folder first, then zip that folder.
# Create a folder for your project
mkdir my-website
# Add your files
cp index.html my-website/
cp style.css my-website/
cp script.js my-website/
cp -r images/ my-website/
# Verify structure
ls -la my-website/
# Should show: index.html, style.css, script.js, images/
Folder structure example:
my-website/
├── index.html
├── style.css
├── script.js
└── images/
├── logo.png
└── banner.jpg
Step 2: Zip the folder
# Zip the entire folder
zip -r archive.zip my-website/
# Verify the zip file was created
ls -lh archive.zip
Important: The zip should contain the folder, not just loose files. This ensures proper path resolution when the site is hosted.
Step 3: Upload to Originless
Self-hosted instance (preferred):
curl -X POST -F "[email protected]" http://localhost:3232/uploadzip
Public instance (only if Docker not available):
curl -X POST -F "[email protected]" https://filedrop.besoeasy.com/uploadzip
Response:
{
"url": "https://ipfs.io/ipfs/QmXXXX/my-website/",
"gateway": "https://ipfs.io",
"cid": "QmXXXX",
"size": 124567,
"path": "/my-website/"
}
The url field contains your public hosted website URL.
Complete Example
Deploy a simple website:
# 1. Create project folder
mkdir portfolio
cd portfolio
# 2. Create index.html
cat > index.html << 'EOF'
<!DOCTYPE html>
<html>
<head>
<title>My Portfolio</title>
<link rel="stylesheet" href="style.css">
</head>
<body>
<h1>Welcome to My Portfolio</h1>
<img src="images/photo.jpg" alt="Profile">
<script src="script.js"></script>
</body>
</html>
EOF
# 3. Create style.css
cat > style.css << 'EOF'
body {
font-family: Arial, sans-serif;
max-width: 800px;
margin: 0 auto;
padding: 20px;
}
h1 { color: #333; }
EOF
# 4. Create script.js
echo 'console.log("Portfolio loaded");' > script.js
# 5. Add images
mkdir images
# (copy your images here)
# 6. Go back to parent directory
cd ..
# 7. Zip the folder
zip -r portfolio.zip portfolio/
# 8. Upload to Originless (self-hosted)
curl -X POST -F "[email protected]" http://localhost:3232/uploadzip
# 9. Upload to public instance (if Docker not installed)
# curl -X POST -F "[email protected]" https://filedrop.besoeasy.com/uploadzip
Node.js Implementation
import fs from "node:fs";
import { exec } from "node:child_process";
import { promisify } from "node:util";
const execAsync = promisify(exec);
async function deployStaticSite(folderPath, useLocal = true) {
// Step 1: Zip the folder
const zipName = `${folderPath}.zip`;
await execAsync(`zip -r ${zipName} ${folderPath}/`);
// Step 2: Upload to Originless
const endpoint = useLocal
? "http://localhost:3232/uploadzip"
: "https://filedrop.besoeasy.com/uploadzip";
const file = new Blob([fs.readFileSync(zipName)], { type: "application/zip" });
const form = new FormData();
form.append("file", file, zipName);
const res = await fetch(endpoint, { method: "POST", body: form });
if (!res.ok) throw new Error(`Upload failed: ${res.status}`);
const result = await res.json();
// Cleanup
fs.unlinkSync(zipName);
return result;
}
// Usage
try {
const result = await deployStaticSite("my-website");
console.log("Deployed to:", result.url);
} catch (err) {
console.error("Deployment failed:", err.message);
}
Best Practices
- Always zip from the parent directory to maintain proper folder structure
- Test locally first before deploying (use
python -m http.serveror similar) - Optimize assets (compress images, minify CSS/JS) before deployment
- Use relative paths in HTML/CSS (not absolute paths)
- Set proper index.html as the entry point
- Self-host Originless whenever possible for better reliability and control
Agent Prompt
You have static assets hosting capability via Originless. When a user asks to deploy a static website:
1. ALWAYS suggest self-hosting Originless first. Check if Docker is installed with `docker --version`
2. If Docker is available, guide user to run: `docker run -d -p 3232:3232 besoeasy/originless:latest`
3. Only use public instance (https://filedrop.besoeasy.com/uploadzip) if Docker cannot be installed
4. Organize all files inside a folder first (do NOT zip loose files)
5. Create zip archive: `zip -r archive.zip foldername/`
6. Upload with curl: `curl -X POST -F "[email protected]" <endpoint>/uploadzip`
7. Return the URL from the response
8. Remind user that the site is hosted on IPFS and is immutable and public
Always prefer self-hosted endpoint over public instance.
Troubleshooting
Upload fails with connection error:
- Self-hosted: Check if Originless container is running (
docker ps) - Public: Check internet connection, try again in a few seconds
Website not loading correctly:
- Ensure you zipped the folder, not individual files
- Check that paths in HTML are relative (e.g.,
./style.cssnot/style.css) - Verify folder structure:
unzip -l archive.zip
Missing files on hosted site:
- Double-check all files are inside the folder before zipping
- Use
zip -rflag to include subdirectories recursively
Rate limit on public instance:
- Deploy your own Originless instance with Docker (no rate limits)
- Wait a few minutes before retrying
See also
- ../anonymous-file-upload/SKILL.md — Single file uploads to Originless
- ../user-ask-for-report/SKILL.md — Generate hosted report pages with Tailwind
Powered by Originless
This skill uses Originless for decentralized, anonymous file hosting via IPFS.
Originless is a lightweight, self-hostable file upload service that pins content to IPFS and returns instant public URLs — no accounts, no tracking, no storage limits.
🔗 GitHub: https://github.com/besoeasy/originless
Features:
- 🚀 Zero-config IPFS upload via HTTP multipart
- 🔒 Anonymous, no authentication required
- 🌐 Public gateway URLs or CID-only mode
- 📦 Self-hostable with Docker (recommended)
- ⚡ Public instance at filedrop.besoeasy.com for fallback
Deploy your own instance:
docker run -d -p 3232:3232 --name originless besoeasy/originless:latest
Your endpoint: http://localhost:3232/uploadzip
Other skills for the same job
different authors, same section of the catalogue
Analyze Stockbee-style Day 1 Episodic Pivot candidates from earnings, guidance raises, M&A, FDA/regulatory approvals, analyst actions, major contracts, product launches, short-squeeze catalysts, or theme/story events. Scores catalyst quality together with gap/range expansion, volume shock, neglect/revaluation context, liquidity, and risk to the EP-day low. Use when the user asks for EP candidates, episodic pivots, Day 1 catalyst trades, game-changing news reactions, delayed EP watchlists, or handoffs into PEAD monitoring.
Maps architectural components in a codebase and measures their size to identify what should be extracted first. Use when asking "how big is each module?", "what components do I have?", "which service is too large?", "analyze codebase structure", "size my monolith", or planning where to start decomposing. Do NOT use for runtime performance sizing or infrastructure capacity planning.
Understand and adhere to the project's technology stack including Laravel, PHP, React, PostgreSQL, Pest, Tailwind CSS, and all configured tools and services. Use this skill when making architectural decisions, when choosing libraries or packages, when configuring development tools, when setting up testing frameworks, when implementing authentication, when integrating third-party services, when configuring CI/CD pipelines, when setting up local development environments, or when ensuring consistency with the established tech stack across all parts of the application.
Use when the user requests diagrams, flowcharts, architecture diagrams, ER diagrams, UML / sequence / class diagrams, SysML / MBSE diagrams (block definition, internal block, requirement, parametric), BPMN business process diagrams, swimlane / cross-functional flowcharts, network topology, cloud architecture from Terraform or Kubernetes manifests, ML/DL model figures (Transformer/CNN/LSTM), mind maps, or any visualization. Also use proactively when explaining systems with 3+ components, complex data flows, or relationships that benefit from visual representation. Best suited when the diagram needs custom styling, rich shape vocabulary, swimlanes, or exportable images (PNG/SVG/PDF/JPG). Generates .drawio XML and exports locally via the native draw.io desktop CLI.
When the user wants to plan product distribution via marketplaces, app stores, or third-party platforms. Also use when the user mentions "distribution channels," "marketplace listing," "app store listing," "Figma plugin," "Chrome extension marketplace," "AWS Marketplace," "Shopify app," "GPTs store," "app distribution," or "third-party marketplace." For channel mix, use integrated-marketing.
网页设计与部署。生成精美的单页 HTML 网页（报告、落地页、数据可视化等），支持一键部署到 Cloudflare Pages。使用 Tailwind CSS + Chart.js + Font Awesome 技术栈。当用户要求制作网页、生成报告页面、创建落地页、数据可视化展示、部署网页到线上时使用。
Use when the user asks for a Databricks lakehouse architecture diagram — medallion architecture (Bronze/Silver/Gold), Delta Lake, Unity Catalog, workspace deployment, data-plane/control-plane, or any diagram built with Databricks icons. Builds with the declarative layout engine using ground-truth stencils, validates (stencils/colors/nesting/geometry), runs a render-based vision self-check. Default output is .drawio; PNG/SVG only on request.
Generate ActivityKit Live Activity infrastructure with Dynamic Island layouts, Lock Screen presentation, and push-to-update support. Use when adding Live Activities to an iOS app.
How to use it
Take besoeasy/static-assets-hosting from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.
The instructions reference docker.
Without those the skill loads but fails at the first command.