Babysitter package-publisher

Publish packages to language-specific registries

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/package-publisher" ~/.claude/skills/a5c-ai-babysitter-package-publisher && rm -rf "$T"

manifest: library/specializations/sdk-platform-development/skills/package-publisher/SKILL.md

Package Publisher Skill

Overview

This skill manages SDK package publishing to language-specific registries including npm, PyPI, Maven Central, NuGet, and crates.io with proper signing and verification.

Capabilities

Publish to npm, PyPI, Maven Central, NuGet, crates.io
Implement package signing and verification
Configure CDN distribution for performance
Verify installation across environments
Support pre-release and stable channels
Implement rollback capabilities
Configure scoped/namespaced packages
Generate installation documentation

Target Processes

Package Distribution
SDK Versioning and Release Management
Multi-Language SDK Strategy

Integration Points

npm registry
PyPI (Python Package Index)
Maven Central
NuGet Gallery
crates.io
GitHub Packages

Input Requirements

Target registries
Package metadata
Signing requirements
Distribution channels
Verification requirements

Output Artifacts

Publishing automation scripts
Package signing configuration
Registry configurations
Verification test scripts
Installation documentation
Rollback procedures

Usage Example

skill:
  name: package-publisher
  context:
    packages:
      - registry: npm
        scope: "@myorg"
        access: public
      - registry: pypi
        name: mysdk
      - registry: maven
        groupId: com.myorg
        artifactId: mysdk
    signing:
      enabled: true
      gpg: true
    distribution:
      cdn: true
      mirrors: true
    channels:
      - stable
      - beta
      - alpha

Best Practices

Sign all published packages
Use scoped/namespaced packages
Support multiple distribution channels
Verify installation post-publish
Document installation clearly
Implement rollback procedures