TechAIDataRegistry

Update JSON/YAML registry files while preserving schema and validating identifiers.

1|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/pagopa/cloud-strategy.github --skill techaidataregistry
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: TechAIDataRegistry
Source: https://github.com/pagopa/cloud-strategy.github/tree/main/.github/skills/tech-ai-data-registry
Command: npx skills add https://github.com/pagopa/cloud-strategy.github --skill techaidataregistry

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the management of structured data files (JSON/YAML) used for registries, ensuring consistency and preventing errors when adding, removing, or modifying entries.

Core Features & Use Cases

  • Update Registries: Safely add, remove, or modify entries in structured files like user lists, team configurations, or policy maps.
  • Maintain Integrity: Enforces rules for unique identifiers, cross-file references, and data format preservation.
  • Use Case: Update the groups.yaml file to add a new team member, ensuring their ID is unique and all required fields are present.

Quick Start

Update the registry file users.yaml to add a new user with id 'test-user', email '[email protected]', and role 'admin'.

Frequently Asked Questions about TechAIDataRegistry

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

FAQPage Schema
How do I safely update a YAML registry file to add a new user entry?

To safely update a YAML registry file, add the new user entry while the skill enforces naming conventions, validates referential integrity, and ensures the user ID is unique. It preserves the existing schema during the modification.

How does referential integrity validation work for JSON configuration registries?

Referential integrity validation for JSON configuration registries works by enforcing cross-file references and ensuring unique identifiers across structured data. It maintains consistency by validating that all referenced entities exist before applying updates.

Can I use this to modify team configurations and policy maps without breaking existing schemas?

Yes, you can modify team configurations and policy maps without breaking existing schemas. The skill preserves data formats and enforces rules for unique identifiers and cross-file references during any registry pattern modifications.

What is the best way to manage structured data files for authorization registries?

The best way to manage structured data files for authorization registries is to use a tool that enforces naming conventions, validates referential integrity, and ensures identifier uniqueness. This prevents errors when adding, removing, or modifying permission map entries.

Why do my JSON registry updates keep failing due to duplicate identifiers?

JSON registry updates fail due to duplicate identifiers because the data lacks proper uniqueness validation. This skill prevents these errors by enforcing unique identifiers and validating referential integrity before safely applying any structural modifications.

Does this approach work for both JSON and YAML data management files?

Yes, this approach works for both JSON and YAML data management files. It safely updates structured registry files for entities like users, groups, and repositories while preserving the existing schema and enforcing referential integrity across both formats.