OpenParable
Skip to content
← Back to skills

Package Publisher

DevOps & Security
package-publisher

Package Publisher is an Agent Skill for devops & security published in the a5c-ai/babysitter repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Publish packages to language-specific registries

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/a5c-ai/babysitter/blob/HEAD/library/specializations/sdk-platform-development/skills/package-publisher/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/package-publisher, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

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

  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