PinMe — zero-config IPFS uploads and full-stack deploys
Deploy without config — upload static files to IPFS, or scaffold and ship full-stack projects (React+Vite frontend, Cloudflare Worker backend, D1 database, R2 storage, email via the platform API) with single-command deploys
- What
- Deploy without config — upload static files to IPFS, or scaffold and ship full-stack projects (React+Vite frontend, Cloudflare Worker backend, D1 database, R2 storage, email via the platform API) with single-command deploys
- Cost
- Free
- Needs
- a PinMe account (login with `pinme login` or `pinme set-appkey <AppKey>` before uploads/deploys), Node.js with npm to install the CLI (`npm install -g pinme`)
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @glitternetwork's PinMe skill: zero-config deployment driven by the `pinme` CLI. Two paths — Path 1 uploads files or static sites to IPFS (`pinme upload ./dist`, optional subdomain binding, CAR import/export, upload history); Path 2 scaffolds full-stack projects (React+Vite frontend on IPFS, Cloudflare Worker backend at `{name}.pinme.pro`, D1 SQLite database, project R2 bucket) with single-command deploys (`pinme save` for everything, `update-worker`/`update-web`/`update-db` for targeted updates), worker code patterns (CORS, JSON APIs, parameterized D1 queries, email sending via the PinMe platform API), SQLite migration conventions, and a strict never-upload list (`node_modules/`, `.env`, `.git`, sources). Honest caveats: requires a PinMe account — login or `pinme set-appkey <AppKey>` before any upload or deploy; the agent always returns the full final URL including hash fragments, never truncated. MIT licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: a PinMe account (login with `pinme login` or `pinme set-appkey <AppKey>` before uploads/deploys), Node.js with npm to install the CLI (`npm install -g pinme`) Install "PinMe — zero-config IPFS uploads and full-stack deploys" for me. It gives my agent @glitternetwork's PinMe workflow: check and update the pinme CLI, authenticate, then either upload files/static sites to IPFS (pinme upload, optional subdomain binding, full final URL returned including hash fragments) or scaffold and deploy full-stack projects (React+Vite frontend, Cloudflare Worker backend, D1 SQLite database, R2 storage, email via the PinMe platform API) with pinme save / update-worker / update-web / update-db — never uploading node_modules/, .env, .git or sources, storing secrets only in secrets, never in config files. MIT-licensed. Repository: https://github.com/glitternetwork/pinme/blob/main/skills/pinme/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code — auth goes through `pinme login` / AppKey in the environment, never committed. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "pinme". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. install the pinme CLI, log in to my PinMe account — that's on me). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.