Agent skill · Data & Analytics

portaljs-architect

Recommend a data-portal architecture (storage, compute, catalog, access, hosting, metadata) from stated needs, then hand off to the build skills. The advisory entry point. Use when starting a new data-portal project and the underlying architecture has not yet been decided.

datopiangithub.com/datopianGitHub ↗
claude-codecan modify filesMIT
Install
npx skills add datopian/portaljs --skill portaljs-architect --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 6 KB
Bundled scripts: none
Version: 1.0.0
Declared author: Datopian <hello@datopian.com>
Allowed tools: ReadWriteBash(du:*)Bash(wc:*)Bash(ls:*)Bash(head:*)
Requires: Claude Code with PortalJS portals (Next.js 14, React 18, Node 18+). Runs from any project via the plugin, a personal…
Path: skills/portaljs-architect/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 2,337
Language: TypeScript
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# PortalJS — Architect ## Overview The advisory entry point for a PortalJS project. Before anything gets scaffolded, this skill works out what to build: given the kind of portal, the shape of the data, and its purpose, it fills six architecture slots (storage, catalog, compute, access, hosting, metadata), resolves two build-time knobs (per-dataset data tier and the portal-wide `DATA_QUERY` mode), and hands off to the concrete build skills. It decides; it does not build. When the brief is thin it interviews in short rounds and never dead-ends — every question has a sensible default, reachable by replying "use defaults." ## Prerequisites - A rough idea of the portal's purpose and data (exact numbers are not required — the interview supplies defaults for anything missing). - Optional: local files or a directory of sample data to inspect for size and shape. - No PortalJS project needs to exist yet; this skill runs before scaffolding. ## Instructions The canonical, full step-by-step workflow lives in [`.claude/commands/portaljs-architect.md`](https://github.com/datopian/portaljs/blob/main/.claude/commands/portaljs-architect.md) — that file is the single source of truth. Follow it when e

What's inside
Steps it walks through
  1. Overview
  2. Prerequisites
  3. Instructions
  4. Output
  5. Error Handling
  6. Examples
  7. Example 1 — National statistics office, DCAT-AP harvesting
  8. Example 2 — Small nonprofit, no arguments given
  9. Example 3 — Internal catalog with restricted datasets
  10. Resources
Ships with 1 file
  • references/reference.md
More from portaljs
All skills →
About this skill
What does the portaljs-architect skill do?

Recommend a data-portal architecture (storage, compute, catalog, access, hosting, metadata) from stated needs, then hand off to the build skills. The advisory entry point. Use when starting a new data-portal project and the underlying architecture has not yet been decided.

How do I install it?

Run `npx skills add datopian/portaljs --skill portaljs-architect --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From datopian/portaljs, a repository with 2,337 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going