heritage_catalog

Coordinates heritage data ingestion, curation workflows, and AI-driven analytics across multiple sources and locations.

Updated Dec 17, 2025

Search Tags:#discovery #catalog #yaml #metadata #heritage #skill-unit

Ready to run

npx skills add https://github.com/Lrmdom/patrimonio-pwa --skill heritage-catalog

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: heritage_catalog
Source: https://github.com/Lrmdom/patrimonio-pwa/tree/main
Command: npx skills add https://github.com/Lrmdom/patrimonio-pwa --skill heritage-catalog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

heritage_catalog units solve the challenge of organizing, discovering, and leveraging diverse heritage data within a scalable, YAML-frontmatter-driven Skill Unit.

Core Features & Use Cases

Define Skill Unit with mandatory SKILL.md frontmatter (name and description)
Load operational instructions into context from SKILL.md body
Support optional resources (scripts, references, assets) for on-demand tasks

Quick Start

Create a SKILL.md at the root with a YAML frontmatter containing name and description, and optionally configure scripts, references, or assets directories.

Frequently Asked Questions about heritage_catalog

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I catalog heritage data using YAML frontmatter for AI discovery?▼

To catalog heritage data using YAML frontmatter, create a SKILL.md file at the root with mandatory name and description fields to coordinate archival data ingestion and generate AI-driven research summaries.

What is a metadata catalog skill unit and when do I need one?▼

A metadata catalog skill unit is a YAML-driven structure that organizes diverse heritage data for AI discovery. You need one when integrating archival data, research summaries, and curation workflows across multiple locales and data sources.

How do I structure archival data ingestion workflows across multiple locales?▼

Structure archival data ingestion workflows across locales by defining a SKILL.md file with mandatory frontmatter, then organizing optional resources like scripts, references, and assets directories to support curation tasks.

Do I need dependencies to use the heritage catalog skill unit?▼

No, you do not need external dependencies to use the heritage catalog skill unit. It operates independently to enforce mandatory SKILL.md frontmatter and outputs metadata fields like tagline, description, dependencies, and components.

What is the best way to generate AI-driven insights from heritage data?▼

The best way to generate AI-driven insights from heritage data is using a scalable YAML-frontmatter-driven Skill Unit that ingests archival data and enforces metadata curation workflows across diverse data sources.

Can I use optional resources like scripts and references with heritage metadata?▼

Yes, you can use optional resources like scripts, references, and assets with heritage metadata by configuring their directories alongside the mandatory SKILL.md file to support on-demand curation and research tasks.