Plugin Publish

Name: Plugin Publish
Availability: InStock
Author: epieczko

Publish Betty Framework plugin packages to local, Claude Marketplace, or GitHub Releases.

2|Updated Oct 22, 2025

Search Tags:#plugin #release #publish #marketplace #checksum #gh-release

Ready to run

npx skills add https://github.com/epieczko/betty --skill plugin-publish

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Plugin Publish
Source: https://github.com/epieczko/betty/tree/main/skills/plugin.publish
Command: npx skills add https://github.com/epieczko/betty --skill plugin-publish

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires PyYAML, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the secure distribution of your Betty Framework plugin bundles to local directories, Claude Marketplace endpoints, or GitHub Releases. It ensures package integrity with checksum verification and supports safe testing with dry-run and validation modes.

Core Features & Use Cases

Validates package integrity via MD5/SHA256 checksums
Publishes to local dist/published for testing and archival
Uploads to Claude Marketplace (simulated) with metadata
Creates GitHub Releases automatically via gh CLI
Dry-run and validate-only modes enable safe testing before publishing

Quick Start

Use the plugin publish tool to distribute a prepared plugin package, for example:

Publish a local tarball:
python skills/plugin.publish/plugin_publish.py dist/betty-framework-1.0.0.tar.gz

Frequently Asked Questions about Plugin Publish

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

FAQPage Schema

How do I publish Betty Framework plugin bundles to multiple targets?▼

Publish plugin bundles to local directories, Claude Marketplace, or GitHub Releases using a single command that validates checksums, manages metadata, and supports dry-run testing before committing to distribution.

Can I validate plugin package integrity before publishing?▼

Yes, validate package checksums using MD5 or SHA256 hashing and inspect manifest metadata in validate-only mode to catch integrity issues without publishing.

What's the best way to automate plugin releases in CI/CD pipelines?▼

Integrate plugin publishing into CI/CD by leveraging dry-run modes, automated GitHub Releases via gh CLI, and audit-ready publication records that track every distribution event.

Do I need to manually generate checksums for my plugin packages?▼

No, checksums are automatically validated during publishing; the tool verifies MD5/SHA256 integrity and generates metadata records for governance without manual setup.

Can I test publishing without uploading to the marketplace?▼

Yes, use dry-run and validate-only modes to test the entire publishing workflow locally, verify checksums, and confirm target configurations before actual distribution.

What happens if a plugin package fails integrity checks during publishing?▼

Publishing halts when checksum validation fails, protecting against corrupted or tampered packages reaching distribution targets and maintaining audit compliance.