ai-registry-integration

Coordinate content updates across skills, commands, profiles, and harness overrides in ai-registry.

1|Updated Apr 17, 2026
One-click install
npx skills add https://github.com/alexgorbatchev/ai-registry --skill ai-registry-integration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ai-registry-integration
Source: https://github.com/alexgorbatchev/ai-registry/tree/main/skills/ai-registry-integration
Command: npx skills add https://github.com/alexgorbatchev/ai-registry --skill ai-registry-integration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The AI registry is the canonical source of truth for skills, commands, profiles, and harness configurations; this skill streamlines adding or updating that content within ai-registry.

Core Features & Use Cases

  • Centralizes content updates across skills, commands, profiles, harness overrides, vendored skills, and related documentation.
  • Guides teams through safe, consistent changes aligned with repository structure and build rules.
  • Use Case: When onboarding a new skill or updating an existing one, run the integration workflow to register changes in ai-registry and trigger the generation pipeline.

Quick Start

Update the AI registry with your new or modified content by running the integration workflow.

Frequently Asked Questions about ai-registry-integration

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

FAQPage Schema
How do I update the AI registry when onboarding new skills?

You can update the AI registry by running the integration workflow, which coordinates content changes across skills, commands, and profiles. It enforces repository rules and validates changes before regenerating outputs to maintain the registry as the single source of truth.

What is the best way to manage harness overrides and vendored skills in a registry?

The best way to manage harness overrides and vendored skills is through a centralized integration workflow that enforces repository rules and uses canonical path tokens. This validates modifications before applying them, ensuring consistent registry updates.

How does registry validation work before triggering a build?

Registry validation works by enforcing repository rules and checking canonical path tokens before regenerating outputs. The integration process validates all content changes across skills and harness configurations to ensure only safe, consistent updates trigger the build pipeline.

Can I modify profiles and commands directly in the AI registry?

Yes, you can modify profiles and commands by running the integration workflow. This workflow guides teams through safe, consistent changes aligned with repository structure, ensuring all additions or modifications are properly validated before the generation pipeline runs.

Why should I use a centralized workflow for AI registry management?

Using a centralized workflow for AI registry management ensures the registry remains the canonical source of truth. It coordinates updates across skills, commands, and harness configurations while enforcing repository rules and validating changes to prevent inconsistent build outputs.