community-registry-starter

Validate OpenDesign marketplace search, installation, and provenance flows for community-developed plugins.

93.2k|10.8k|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/nexu-io/open-design --skill community-registry-starter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: community-registry-starter
Source: https://github.com/nexu-io/open-design/tree/main/plugins/community/registry-starter
Command: npx skills add https://github.com/nexu-io/open-design --skill community-registry-starter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the need for developers to verify that their custom plugins correctly integrate with the OpenDesign registry and follow standard installation provenance paths.

Core Features & Use Cases

  • Registry Flow Validation: Exercises the search and discovery mechanisms for community-contributed plugins.
  • Provenance Verification: Ensures that the installation path from 'Available' to 'Installed' functions as expected within the OpenDesign environment.
  • Use Case: Use this plugin as a template to test if your own custom plugin metadata is correctly parsed by the OpenDesign marketplace registry.

Quick Start

Create a compact status card that explains how a community OpenDesign plugin flows from Available to Installed.

Frequently Asked Questions about community-registry-starter

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

FAQPage Schema
How do I test my plugin installation flow?

Use the community-registry-starter as a reference implementation to verify that your plugin metadata and repository structure align with the OpenDesign registry requirements for successful installation.

What is the purpose of the registry starter plugin?

The registry starter plugin serves as a minimal example to validate that the OpenDesign marketplace can correctly discover, search, and install plugins from community-defined sources.

Does this plugin support custom installation paths?

This plugin is designed to exercise the default registry source and provenance path, ensuring compatibility with standard OpenDesign marketplace installation flows.

Why is my plugin not appearing in the registry?

Ensure your plugin metadata follows the required schema and that the repository URL is correctly registered in the OpenDesign marketplace source configuration.