Babysitter plugin-registry-manager

Manage SDK plugin discovery and registration

install

source · Clone the upstream repo

git clone https://github.com/a5c-ai/babysitter

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/a5c-ai/babysitter "$T" && mkdir -p ~/.claude/skills && cp -r "$T/library/specializations/sdk-platform-development/skills/plugin-registry-manager" ~/.claude/skills/a5c-ai-babysitter-plugin-registry-manager && rm -rf "$T"

manifest: library/specializations/sdk-platform-development/skills/plugin-registry-manager/SKILL.md

Plugin Registry Manager Skill

Overview

This skill manages SDK plugin ecosystems including discovery, registration, validation, and lifecycle management for extensible SDK architectures.

Capabilities

Design plugin interface contracts
Implement plugin loading and registration
Validate plugin compatibility versions
Document plugin API for developers
Implement plugin discovery mechanisms
Support plugin configuration
Manage plugin lifecycle events
Create plugin development tooling

Target Processes

Plugin and Extension Architecture
SDK Architecture Design
Developer Experience Optimization

Integration Points

Plugin registries (npm, PyPI)
SDK extension points
Configuration systems
Version compatibility checkers
Plugin development CLIs

Input Requirements

Plugin interface requirements
Compatibility rules
Discovery mechanisms
Lifecycle requirements
Documentation needs

Output Artifacts

Plugin interface definitions
Plugin loader implementation
Compatibility validator
Plugin documentation generator
Discovery mechanism
Plugin CLI tools

Usage Example

skill:
  name: plugin-registry-manager
  context:
    pluginInterface:
      version: "1.0"
      hooks:
        - onInit
        - onRequest
        - onResponse
        - onError
    discovery:
      patterns:
        - "@mysdk/plugin-*"
        - "mysdk-plugin-*"
      sources:
        - npm
        - local
    compatibility:
      sdkVersion: "semver"
      nodeVersion: ">=16"
    lifecycle:
      init: true
      shutdown: true

Best Practices

Version plugin interfaces explicitly
Validate compatibility before loading
Support local development plugins
Provide plugin development CLI
Document plugin authoring clearly
Handle plugin failures gracefully