Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →datopian/portaljs-add-dataset
Add a dataset (CSV, TSV, JSON, or GeoJSON) to an existing PortalJS portal. Appends an entry to datasets.json so the catalog and showcase render it automatically; routes the data by source (local file vs remote URL) — R2 via Git LFS by default, remote URLs by passthrough.
Passed 15 of 19 test cases with the skill, and 5 of 19 without it.
and 17 more in the full report
12 fixed5 passed either way4 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
I have a dataset file `./big_data.parquet` that I want to add directly into my PortalJS catalog under namespace `analytics` and slug `big-data`. Please add it to datasets.json and verify the build.
| Checked | Without skill | With skill |
|---|---|---|
| The request is rejected or paused to request format conversion because parquet is not natively supported for showcase previews. | Missed | Passed |
| Parquet is flagged as unsupported in favor of CSV, TSV, JSON, or GeoJSON formats. | Missed | Passed |
The instructions your model reads when the skill loads.
Register a dataset in a PortalJS (portaljs-catalog) portal. The skill appends one entry to
datasets.json — the single source of truth for the catalog — and routes the underlying
bytes by source first, then size: a local file defaults to R2 via Git LFS, a remote URL
defaults to passthrough (no copy). No per-dataset page is created; the catalog at /search
lists the new entry and the dynamic showcase route pages/[owner]/[slug].tsx renders it
automatically at /@<namespace>/<slug>. Supported formats for the showcase preview: CSV,
TSV, JSON (array), and GeoJSON.
portaljs-new-portal) with datasets.json,
package.json, and pages/[owner]/[slug].tsx present.git and git-lfs installed, and an Arc account token
(or an OSS Giftless key) to mint a push-scoped LFS credential.The canonical, full step-by-step workflow is
.claude/commands/portaljs-add-dataset.md —
the single source of truth. Read and follow it when executing. Summary:
$ARGUMENTS — source (file path or URL), portal directory (default
.), dataset name/slug, description, namespace. If the source is missing, interview the
user; never dead-end.datasets.json, package.json, and
pages/[owner]/[slug].tsx exist.Content-Type header
(CSV, TSV, JSON array, or GeoJSON); reject anything else and ask for a conversion.public/data/ (fenced exception for
bundled samples or an OSS-no-R2 fallback).datasets.json — slug, namespace, name, description, file
(the routed path/URL), format — keeping (namespace, slug) unique.npx next build; fix errors (commonly malformed JSON) beforetest cases passed, vs 5 / 19 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.