skills.rest
BrainDriveAI
BrainDriveAIOFFICIAL
Explore all skills by this author →
WebsiteGitHub

packaging-rules

Automate BrainDrive plugin ZIP creation, validation, and packaging.

Updated Feb 1, 2026
Search Tags:#validation#build#packaging#plugin#release#distribution#zip
One-click install
npx skills add https://github.com/BrainDriveAI/BrainDrive-Plugin-Builder-ClaudeCode --skill packaging-rules
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: packaging-rules
Source: https://github.com/BrainDriveAI/BrainDrive-Plugin-Builder-ClaudeCode/tree/main/.claude/skills/packaging-rules
Command: npx skills add https://github.com/BrainDriveAI/BrainDrive-Plugin-Builder-ClaudeCode --skill packaging-rules

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

BrainDrive plugin packaging and ZIP-structure standards ensure consistent, distributable plugins and prevent broken deployments.

Core Features & Use Cases

  • Standardized ZIP contents and naming conventions for BrainDrive plugins.
  • End-to-end guidance from build artifacts to final ZIP deployment, including dist/ validation and required files.
  • Real-world workflow examples for validating plugin packages and preventing common packaging mistakes.

Quick Start

Create a production-ready BrainDrive plugin ZIP that conforms to the packaging rules for the specified slug and version.

Frequently Asked Questions about packaging-rules

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

FAQPage Schema
How do I package a BrainDrive plugin into a compliant ZIP archive?▼

To package a BrainDrive plugin, build the dist/ content and required files into a ZIP archive. The packaging rules automate this by validating version consistency, plugin_slug mapping, and ZIP naming conventions for final deployment.

What is included in the validation process for plugin distribution?▼

Plugin distribution validation includes checking dist/ content, verifying required files, and ensuring version consistency. Safety checks are also applied to prevent the inclusion of sensitive data within the final ZIP archive.

Do I need specific build artifacts before creating a plugin ZIP?▼

Yes, you need build artifacts in the dist/ directory before creating a plugin ZIP. The packaging workflow requires these compiled outputs and required files to construct a compliant archive for final deployment.

Why does my BrainDrive plugin ZIP fail the release validation?▼

Plugin ZIP release validation fails when there is version inconsistency, incorrect plugin_slug mapping, or missing required files. The packaging rules enforce strict naming and dist/ content checks to prevent broken plugin deployments.

Can I automate the end-to-end packaging workflow for plugin releases?▼

Yes, you can automate the end-to-end packaging workflow for plugin releases. The rules apply standardized ZIP contents and naming conventions, handling everything from build artifacts to final ZIP deployment automatically.

Related Skills

Explore More Software Engineering Skills→
stahurastahura
19

publish

Automate Domo app build, packaging, and publishing with dist artifacts.

Community
Intermediate
epieczkoepieczko

Plugin Build

Bundle Betty Framework plugin directories into versioned tar.gz or zip archives.

Community
Advanced
ils15ils15
10

quality-gate

Run linters, type-checkers, tests, and build steps before code commits.

Community
Advanced
metaid-developersmetaid-developers

metaapp-builder

Package MetaApp frontend projects into timestamped ZIP archives.

Official
Intermediate