portaljs-define-schema

by datopian2.4k

Install

The skill file stays in the publisher's repository.

Paste the copied command in a terminal. It installs this SKILL.md into that agent.

npx skills add datopian/portaljs --skill portaljs-define-schema -a cursor -y

Download skill skills/portaljs-define-schema/SKILL.md on GitHub

Related skills

View all

Define a dataset's metadata profile — infer a Frictionless Table Schema from its data, add Data Package metadata (license, sources, keywords), and write it into datasets.json so the showcase renders a typed field table. Extend or customize via the L0-L3 profile ladder. Use when a registered dataset needs field types, constraints, or catalog metadata before publishing.

Questions

How do I install portaljs-define-schema?: Download skills/portaljs-define-schema/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
Where does portaljs-define-schema live?: The publisher keeps it at https://github.com/datopian/portaljs.
Which agents can use portaljs-define-schema?: Claude, Cursor, and Codex can read a SKILL.md you add from the publisher's repository.

name: portaljs-define-schema description: Define a dataset's metadata profile — infer a Frictionless Table Schema from its data, add Data Package metadata (license, sources, keywords), and write it into datasets.json so the showcase renders a typed field table. Extend or customize via the L0-L3 profile ladder. Use when a registered dataset needs field types, constraints, or catalog metadata before publishing. allowed-tools: Read, Write, Edit, Bash(npx:), Bash(head:*) version: 1.0.0 author: Datopian license: MIT compatibility: Claude Code with PortalJS portals (Next.js 14, React 18, Node 18+). Runs from any project via the plugin, a personal ~/.claude/commands install, or a portaljs clone. tags:

Level	What it is	When
L0	Default `frictionless-tabular` profile; declare schema + metadata.	Default. Standard tabular CSV/TSV.
L1	L0 plus extra descriptive package fields.	Extra metadata, standard validation is fine.
L2	Fully custom profile (own schema template + `validate()`).	A dataset type needing custom validation rules.
L3	Multiple registered profiles, resolved per dataset.	A portal mixing dataset types.

Symptom	Cause	Fix
Dataset not found in `datasets.json`	Wrong slug or missing `namespace/` prefix	List available slugs and re-prompt.
`lib/metadata/` missing	Portal predates the metadata-profile contract	Proceed anyway — schema fields are optional and ignored by older showcases.
No `fields` schema produced	Dataset is JSON/GeoJSON, not tabular	Expected — capture Data Package metadata only.
Validation reports type errors	Sampled values don't coerce to the inferred type	Relax the `type` or drop the offending `required`/`pattern` constraint.
`next build` fails on `datasets.json`	Stray comma or a type outside `FieldType`	Fix the JSON/type and rebuild before reporting success.

portaljs-define-schema

Install

Related skills

Questions

PortalJS — Define Schema

Overview

Prerequisites

Instructions

Output

Error Handling

Examples

Example 1 — Default L0 schema for a CSV dataset

Example 2 — Metadata only for a GeoJSON dataset

Example 3 — Custom L2 profile with its own validation

Resources