Portaljs deploy

Skill jeremylongshore/claude-code-plugins-plus-skills/plugins/community/portaljs/skills/portaljs-deploy

425 plugins, 2,810 skills, 200 agents for Claude Code. Open-source marketplace at tonsofskills.com with the ccpi CLI package manager.

Install

npx -y skills add jeremylongshore/claude-code-plugins-plus-skills --skill portaljs-deploy

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its author says it does

Copied from the file, not written here

Deploy a PortalJS portal to PortalJS Arc — Datopian-managed static hosting on Cloudflare. Builds a static export, uploads it, and returns a live SLUG.arc.portaljs.com URL. One command, one target. Use when a portal is ready to publish or redeploy to a live URL.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

5.3 KB, ~1.2k tokens by cl100k_base, as published. Nobody here has run it

PortalJS — Deploy

Overview

Publish an existing PortalJS portal to PortalJS Arc — Datopian's managed static hosting on Cloudflare. Build a static export, upload it to the Arc API, and print a live https://SLUG.arc.portaljs.com URL. Re-running redeploys the same portal (idempotent on the slug). This is a single-target skill — it deploys to Arc only. For self-hosting, run npm run build and upload out/ to any static host; no skill required for that path. Arc serves static exports only — SSR is not hosted on Arc yet.

Prerequisites

A PortalJS portal directory with a package.json that lists next as a dependency.
Node 18+ and npm on PATH (the Arc device-login flow uses Node's global fetch).
curl and tar available for packaging and upload.
A PortalJS Arc token — read from PORTALJS_TOKEN, or ~/.portaljs/credentials ({"token":"…"}). If neither exists, the skill signs in on demand via a device-code flow; no manual token copying required.
If the portal stores large data in Git LFS/R2, do not run git lfs pull before deploying — large datasets are served from Cloudflare R2 via absolute URLs in datasets.json, not copied into the export.

Instructions

The canonical, full step-by-step workflow is .claude/commands/portaljs-deploy.md — the single source of truth. Read and follow it when executing. Summary:

Gather input — portal directory (default .) and slug (default from package.json name or directory name, slugified). Confirm the directory is a Next.js project; reject reserved slugs (www, api, admin, staging, arc).
Resolve the Arc token: read PORTALJS_TOKEN, else ~/.portaljs/credentials; if missing, run the device-authorization sign-in flow and save the returned token.
Ensure next.config.js sets output: 'export' and images: { unoptimized: true }, then run npm run build; stop if the build fails.
Verify the export carries no dataset bytes — run npm run check-export (or scripts/check-export.mjs) to catch Git LFS pointer leaks and oversized data files.
Tar the out/ directory and POST it to $PORTALJS_ARC_API/v1/deploy?slug=<slug> with the bearer token; handle 200/401/409/400/413 responses distinctly.
Report the live URL, file count, upload size, and R2-vs-inline dataset counts.

Output

Modified (if needed): next.config.js — adds output: 'export' and images: { unoptimized: true } when absent, preserving the rest of the config.
Created (on first sign-in): ~/.portaljs/credentials (mode 0600).
Verified: npm run build exits 0, out/index.html exists, the export-hygiene check passes.
Result: the portal is live at https://SLUG.arc.portaljs.com; re-running updates the same slug in place.

Error Handling

Symptom	Cause	Fix
`NOT_A_PORTAL` error	No `next` dependency found in `PORTAL_DIR/package.json`	Run from a valid portal directory, or pass the correct path.
Slug rejected	Derived slug is reserved (`www`, `api`, …) or not a valid DNS label	Pass an explicit `--slug <name>`.
Build fails (non-zero exit)	App/config error surfaced in `npm run build`	Print the log, fix the error, never deploy a failing build.
`check-export` fails	Git LFS pointer leaked into `out/`, or a data file exceeds the size budget	Reference large data by absolute R2 URL via `portaljs-add-dataset`; don't `git lfs pull` before building.
`401` on upload	Token invalid, expired, or revoked	Re-run the device sign-in flow once, retry the upload; stop if it 401s again.
`409` on upload	Slug already taken by another account	Choose a different `--slug`.
`400` / `413` on upload	Malformed slug or export too large	Read the JSON `error` field and address the specific cause.

Examples

Example 1 — Deploy the current directory with the default slug

/portaljs-deploy

Example 2 — Deploy with an explicit slug

/portaljs-deploy --slug my-open-data

Example 3 — Non-interactive deploy from CI with a token env var

export PORTALJS_TOKEN=arc_live_xxxxxxxx
/portaljs-deploy ./portals/city-budget --slug city-budget

Resources

Full workflow: .claude/commands/portaljs-deploy.md
Deploy internals reference: references/reference.md
Related skills: portaljs-new-portal, portaljs-add-dataset, portaljs-connect-ckan
PortalJS Arc dashboard (sign in, manage tokens): https://arc.portaljs.com

Gives 0 of the 12 instructions most ship operate skills give in ~1.2k tokens

Counted across 779 of the 1,178 authors here whose files we hold, read 2026-08-07

document a rollback plan before deploymentin 41 of 779, across 22 files
update the changelogin 21 of 779, across 19 files
Run the test suitein 20 of 779
create an annotated git tagin 20 of 779
clean up feature flags after full rolloutin 18 of 779, across 10 files
verify deployment health after launchin 18 of 779, across 10 files
test both feature flag statesin 17 of 779, across 9 files
verify the working tree is cleanin 17 of 779
make database migrations backward-compatiblein 16 of 779, across 8 files
set up error monitoring before launchin 15 of 779, across 7 files
monitor metrics at each rollout stagein 14 of 779, across 5 files
create a github releasein 14 of 779

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.