skills.rest
xuezhaojun
xuezhaojunCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

custom-registries

Configure private registries in oyoc.json to share hooks, agents, and skills.

Updated Apr 12, 2026
Search Tags:#hooks#skills#agents#registry#team-workflow#module-registry
One-click install
npx skills add https://github.com/xuezhaojun/oh-your-opencode --skill custom-registries
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: custom-registries
Source: https://github.com/xuezhaojun/oh-your-opencode/tree/main/.opencode/skills/custom-registries
Command: npx skills add https://github.com/xuezhaojun/oh-your-opencode --skill custom-registries

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often need to share and standardize internal modules such as hooks, agents, and skills across projects. Private registries provide a centralized, versioned source of truth to streamline collaboration and governance.

Core Features & Use Cases

  • Registry Format: A registry is a directory (typically a git repo) containing a catalog.json and subdirectories for hooks, agents, and skills, enabling discoverable, reusable modules.
  • Configuration & Discovery: Registries are configured in oyoc.json; the system merges catalogs from built-in and remote registries to surface modules for harness generation.
  • Use Case: A team maintains a private registry to share custom hooks and agents across projects while enforcing internal standards.

Quick Start

Create a new registry repository with a catalog.json at its root, add your hooks, agents, and skills, and configure the registry URL in oyoc.json.

Frequently Asked Questions about custom-registries

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

FAQPage Schema
What is a private registry for team workflow modules?▼

A private team registry is a directory, typically a git repo, containing a catalog.json and subdirectories for hooks, agents, and skills. It provides a centralized, versioned source of truth to standardize internal modules across multiple projects.

What format is required for a custom module registry catalog?▼

A custom module registry requires a catalog.json file at the root directory. This format enforces discoverability and standardization, allowing the system to merge built-in and remote catalogs for module generation.

Does the registry system enforce a specific directory structure for modules?▼

Yes, the registry system enforces a specific directory structure with a catalog.json at the root and separate subdirectories for hooks, agents, and skills to ensure modules are discoverable and reusable.

Can I use a git repository as a shared registry for team skills?▼

Yes, you can use a git repository as a shared registry. Create a repo with a catalog.json at its root, add your team's skills to the designated subdirectories, and configure the registry URL in oyoc.json.

Related Skills

Explore More Software Engineering Skills→
TechDufusTechDufus
173

init-deep

Create nested CLAUDE.md files for per-directory contextual guidance.

Community
Intermediate
Aqsagull99Aqsagull99

nextjs-skill

Build Next.js 16+ apps with App Router, server components, and API routes.

Community
Intermediate
aporto-techaporto-tech

Freeze

Restrict file edits to a designated directory for the session.

Official
Basic
Aurora-AIAurora-AI

master-skill

Automates discovery, installation, and synchronization of Aurora skills across projects via manifests.

Community
Advanced