datopiandatopian/portaljs/skills/portaljs-add-dcat/SKILL.md

portaljs-add-dcat

Skill2.4k starsChanged 12 days agoMITView on GitHub

Make a PortalJS portal harvestable by national/EU/US open-data portals — emit standards-compliant DCAT catalog feeds (DCAT 2/3, DCAT-AP, DCAT-US, national profiles) in JSON-LD, Turtle, and RDF/XML at build, with autodiscovery and per-profile conformance checking. Use when a portal needs to be harvested by data.europa.eu, data.gov, or a national open-data catalog.

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 0 are distinctive, and 6 are very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Very specific:
Ensure the DCAT profile layer is present — dcat-profiles.ts, dcat-rdf.ts, dcat-validate.ts — copying canonical versions from …
line 53
Very specific:
Ensure scripts/generate-dcat.ts is wired to predev/prebuild and emits per-profile x serialization feeds from dcat.config.json.
line 56
Very specific:
Write dcat.config.json with the gathered profiles, publisher, contact, license, themes, and access level.
line 58
Very specific:
Add feed autodiscovery: a <link rel="alternate" type="application/ld+json"> to pages/_document.tsx pointing at /catalog.jsonld.
line 60
Very specific:
Verify the RDF: confirm the JSON-LD parses, and cross-check that JSON-LD, Turtle, and RDF/XML agree.
line 64
Very specific:
Verify the build with npx next build.
line 67

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

PortalJS — Add DCAT

Overview

Turn an existing PortalJS (portaljs-catalog) portal into a harvestable data catalog. PortalJS is Frictionless-native — a dataset is a Data Package (see portaljs-define-schema) — and DCAT is the serialization + harvest layer on top (lib/metadata/dcat.ts + lib/metadata/dcat-profiles.ts). This skill selects one or more DCAT application profiles, maps every dataset's metadata to them, and writes static feed files at build time — JSON-LD, Turtle, and RDF/XML — so external catalogs (data.europa.eu, data.gov, national portals) can harvest the datasets automatically, on any static host, with no runtime.

Prerequisites

A scaffolded PortalJS portal with datasets.json, package.json, and lib/metadata/ (the metadata-profile contract) present.
lib/metadata/dcat.ts (the DCAT-3 core) already in place — profiles augment it.
Node 18+ and npm available in the portal directory.
For DCAT-AP / DCAT-US: a publishing organization (name + homepage) and a contact (name + email) — both profiles require dct:publisher and dcat:contactPoint.
Optional but recommended: network access to run SHACL conformance checks against the official EU ITB validator or pyshacl.

Instructions

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

Gather input from $ARGUMENTS (interview if thin): portal directory (default .), profiles (default ["dcat-3"]), site URL, publisher, contact, license, themes, languages, access level.
Validate the portal directory: confirm datasets.json, package.json, and lib/metadata/ exist; stop with an ERROR: if the metadata contract is missing.
Ensure the DCAT profile layer is present — dcat-profiles.ts, dcat-rdf.ts, dcat-validate.ts — copying canonical versions from examples/portaljs-catalog if the portal predates this skill.
Ensure scripts/generate-dcat.ts is wired to predev/prebuild and emits per-profile x serialization feeds from dcat.config.json.
Write dcat.config.json with the gathered profiles, publisher, contact, license, themes, and access level.
Add feed autodiscovery: a <link rel="alternate" type="application/ld+json"> to pages/_document.tsx pointing at /catalog.jsonld.
Generate the feeds and check conformance: run npm run generate:dcat and surface any missing mandatory fields.
Verify the RDF: confirm the JSON-LD parses, and cross-check that JSON-LD, Turtle, and RDF/XML agree; run SHACL validation (ITB for DCAT-AP, pyshacl for DCAT-US) when network/tooling allow.
Verify the build with npx next build; fix errors before reporting success.
Report the profiles emitted, feed paths, conformance status, and next steps (register with the harvester, run portaljs-deploy).

Output

Created/modified: dcat.config.json (committed config).
Generated (build artifacts, gitignored): public/catalog.jsonld /.ttl/.rdf (canonical feed), public/catalog.<profile>.{jsonld,ttl,rdf} per configured profile, public/catalog-feeds.json (feed index).
Modified: pages/_document.tsx (autodiscovery <link>), package.json (generate:dcat script wired to predev/prebuild).
Verified: feeds are valid JSON-LD/Turtle/RDF-XML, conformance status reported, npx next build passes.

Error Handling

Symptom	Cause	Fix
`NO_METADATA_CONTRACT`	`lib/metadata/` not found	Portal predates the metadata-profile contract; scaffold with `portaljs-new-portal` or add `lib/metadata` first.
`NO_DCAT_CORE`	`lib/metadata/dcat.ts` not found	The DCAT-3 core is missing; update the portal template before adding profiles.
`BAD_CONFIG`	`dcat.config.json` is not valid JSON	Fix the syntax and re-run `npm run generate:dcat`.
`UNKNOWN_PROFILE`	Profile id not in the registry	Use one of `dcat-2`, `dcat-3`, `dcat-ap`, `dcat-us`, `geodcat-ap`, `croissant`, `dcat-ap-se`, `dcat-ap-ch`, `dcat-ap-de`, `dcat-ap-it`, or register a national profile first.
Feed flagged non-conformant	`publisher`/`contactPoint` missing for DCAT-AP or DCAT-US	Ask the user for the publishing organization and contact, add to `dcat.config.json`, regenerate.
DCAT-US SHACL rejects the publisher	Publisher has no IRI (blank node)	Set `publisher.uri` (or `homepage`) in `dcat.config.json`.
`next build` fails after config change	Malformed JSON in `dcat.config.json` or `datasets.json`	Print the build log, fix the JSON, rebuild before reporting success.

Examples

Example 1 — Default DCAT-3 feed, no national harvesting

/portaljs-add-dcat

Emits the canonical public/catalog.jsonld/.ttl/.rdf under the default dcat-3 profile, adds autodiscovery to _document.tsx, and wires generate:dcat into predev/prebuild. No publisher/contact required.

Example 2 — EU harvesting via DCAT-AP

/portaljs-add-dcat profiles=dcat-ap site=https://data.example.org

Prompts for publisher (name + homepage) and contact (name + email) since DCAT-AP requires both, writes them into dcat.config.json, and emits public/catalog.dcat-ap.{jsonld,ttl,rdf} plus the canonical feed with absolute links.

Example 3 — US federal harvesting via DCAT-US

/portaljs-add-dcat profiles=dcat-us site=https://data.example.gov

Requires an IRI-identified publisher (publisher.uri) for SHACL conformance; emits catalog.dcat-us.{jsonld,ttl,rdf} and validates against the DCAT-US 3.0 SHACL shapes with pyshacl when available.

Example 4 — Multiple profiles plus a national extension

/portaljs-add-dcat profiles=dcat-ap,dcat-ap-de site=https://daten.example.de

Emits both catalog.dcat-ap.* and catalog.dcat-ap-de.* feeds from one config; the first profile listed also becomes the canonical, un-suffixed catalog.jsonld/.ttl/.rdf.

Resources

Full workflow: .claude/commands/portaljs-add-dcat.md
Profile registry, serialization formats, and validator details: references/reference.md
Related skills: portaljs-define-schema, portaljs-new-portal, portaljs-deploy, portaljs-migrate
DCAT specification: https://www.w3.org/TR/vocab-dcat-3/

Download now (ZIP)

Mar 17, 2025[feat] support obsidian style wikilinks, backlinks, embeds, graph view — fuma-nama/fumadocs1 reaction · 1 comment
Oct 28, 2026claude-code-marketplaces.github.datopian.portaljs: init at 0-unstable-2026-10-27 — sudosubin/agents.nix0 reactions
Oct 20, 2026agent-skills.github.datopian.portaljs: 0-unstable-2026-10-15 → 0-unstable-2026-10-20 — sudosubin/agents.nix0 reactions
Oct 20, 2026agent-skills.github.datopian.portaljs: 0-unstable-2026-08-20 → 0-unstable-2026-10-15 — sudosubin/agents.nix0 reactions
Oct 3, 2026agent-skills.github.datopian.portaljs: 1.4.0-unstable-2026-08-20 → 0-unstable-2026-08-20 — sudosubin/agents.nix0 reactions

32 more on GitHub

Sep 30, 2026docs: fix typos and a stale CKAN example link — olitreadwell/portaljs0 reactions
Sep 26, 2026agent-skills.github.datopian.portaljs: init at 1.4.0-unstable-2026-08-20 — sudosubin/agents.nix0 reactions
Sep 26, 2026[Candidate] datopian/portaljs/skills/portaljs-add-dataset - portaljs-add-dataset — ProSkillsMD/proskills0 reactions · 2 comments
Sep 26, 2026[Candidate] datopian/portaljs/skills/portaljs-add-chart - portaljs-add-chart — ProSkillsMD/proskills0 reactions · 2 comments
Sep 26, 2026[Candidate] datopian/portaljs/skills/arcgis-to-portaljs - arcgis-to-portaljs — ProSkillsMD/proskills0 reactions · 1 comment
Aug 12, 2026fix(ckan): make Pagination page buttons readable by screen readers — olitreadwell/portaljs0 reactions
Aug 12, 2026fix(ckan-api-client-js): restore validation error fallback message — olitreadwell/portaljs0 reactions
Aug 12, 2026fix(create-portaljs): make the scaffold template source repo-aware — olitreadwell/portaljs0 reactions
Jul 8, 2026Add charts to the homepage — datopian/portaljs-research0 reactions · 2 comments
Jul 7, 2026Add PortalJS plugin (datopian/portaljs) — tmcpa/claudedirectory0 reactions · 1 comment
Jun 25, 2026Improve ui/ux — datopian/portaljs-research0 reactions · 2 comments
Mar 24, 2026content: migrate two legacy Flowershow tutorials from portaljs.com — flowershow/flowershow0 reactions · 2 comments
Dec 12, 2025Consolidate datahubio repos into datasets org — datasets/collective0 reactions
Nov 21, 2025Added scope organization param into MCP URL to allow specific organizations — datopian/portaljs-mcp-server0 reactions · 2 comments
Oct 29, 2025[BUG Fix] Pagination and table — datopian/portaljs-frontend-starter0 reactions · 2 comments
Oct 19, 2025[BUG FIX] Frontend table preview — datopian/portaljs-frontend-starter0 reactions · 2 comments
Oct 19, 2025[Bug Fix] Table Preview Frontend issues — datopian/portal-lcc0 reactions · 2 comments
Oct 9, 2025preview data table tool — datopian/portaljs-mcp-server0 reactions · 1 comment
Oct 7, 2025[IMPLEMENTING] Auth for portalJS key — datopian/portaljs-mcp-server0 reactions · 2 comments
Sep 18, 2025Dataverse Harvester Implementation — datopian/harvesterjs0 reactions · 1 comment
Jul 6, 2025Move all flowershow stuff from portaljs and add redirects — flowershow/flowershow0 reactions · 1 comment
May 9, 2025Enable Iframe previews — datopian/portaljs-frontend-starter0 reactions · 2 comments
Dec 28, 2023Transfer here "create a simple catalog of anything using markdown" — flowershow/wayofmarkdown0 reactions · 8 comments
Dec 14, 2023Migrate content from portaljs.org/guide to this site — flowershow/wayofmarkdown0 reactions · 6 comments
Oct 23, 2023[DO-NOT_MERGE] Improvement suggestions — flowershow/flowershow0 reactions · 1 comment
Sep 20, 2023When I have a remote content e.g. https://github.com/datasets/awesome-data I want to load and render that (statically) so that i can author content in another repo but render it here — Valecia2023/caring.net0 reactions
Jun 12, 2023Setup auto-publishing to npm — flowershow/markdowndb0 reactions
May 26, 2023Turn this repo into core template and move core lib to portaljs repo — flowershow/flowershow0 reactions · 2 comments
May 17, 202317 consolidate gitignore and expand its entries — hackforla/accessthedata-ckan0 reactions
May 16, 2023[EPIC] Editor guide: how to contribute content and datasets — flowershow/wayofmarkdown0 reactions · 2 comments
Apr 28, 2023[epic] MarkdownDB site (landing page) and "launch" — flowershow/markdowndb0 reactions · 6 comments
Oct 30, 2022Analytics other than Google Analytics (and switch to pliny model) — flowershow/flowershow0 reactions · 2 comments

On Hacker News · 1

Jul 15, 2026Show HN: PortalJS – AI-native, open-source framework for data portals10 points · 1 comment

In this repository16 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- site/CLAUDE.mdCLAUDE.md
- arcgis-to-portaljsSkill
- portaljs-add-chartSkill
- portaljs-add-datasetSkill
- portaljs-add-geoSkill
- portaljs-add-mapSkill
- portaljs-add-resourceSkill
- portaljs-architectSkill
- portaljs-check-data-qualitySkill
- portaljs-connect-ckanSkill
- portaljs-define-schemaSkill
- portaljs-deploySkill
- portaljs-migrateSkill
- portaljs-new-portalSkill

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free