package-publisher

Publish packages to language-specific registries

509 stars

Best use case

package-publisher is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Publish packages to language-specific registries

Teams using package-publisher should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/package-publisher/SKILL.md --create-dirs "https://raw.githubusercontent.com/a5c-ai/babysitter/main/library/specializations/sdk-platform-development/skills/package-publisher/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/package-publisher/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How package-publisher Compares

Feature / Agentpackage-publisherStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Publish packages to language-specific registries

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# 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

```yaml
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

1. Sign all published packages
2. Use scoped/namespaced packages
3. Support multiple distribution channels
4. Verify installation post-publish
5. Document installation clearly
6. Implement rollback procedures

Related Skills

swift-package-manager-config

509
from a5c-ai/babysitter

Configure Swift Package Manager with platform-specific dependencies and build settings

msix-package-generator

509
from a5c-ai/babysitter

Generate MSIX packaging configuration with manifest, assets, and signing for Windows applications

deb-package-builder

509
from a5c-ai/babysitter

Build Debian packages with proper control files, dependencies, and maintainer scripts

bentoml-model-packager

509
from a5c-ai/babysitter

BentoML skill for model packaging, serving, and containerization.

chocolatey-package-generator

509
from a5c-ai/babysitter

Generate Chocolatey package for Windows CLI distribution.

process-builder

509
from a5c-ai/babysitter

Scaffold new babysitter process definitions following SDK patterns, proper structure, and best practices. Guides the 3-phase workflow from research to implementation.

Workflow & Productivity

babysitter

509
from a5c-ai/babysitter

Orchestrate via @babysitter. Use this skill when asked to babysit a run, orchestrate a process or whenever it is called explicitly. (babysit, babysitter, orchestrate, orchestrate a run, workflow, etc.)

yolo

509
from a5c-ai/babysitter

Run Babysitter autonomously with minimal manual interruption.

user-install

509
from a5c-ai/babysitter

Install the user-level Babysitter Codex setup.

team-install

509
from a5c-ai/babysitter

Install the team-pinned Babysitter Codex workspace setup.

retrospect

509
from a5c-ai/babysitter

Summarize or retrospect on a completed Babysitter run.

resume

509
from a5c-ai/babysitter

Resume an existing Babysitter run from Codex.