metaapp-builder

Package MetaApp frontend projects into timestamped ZIP archives.

Updated Jan 29, 2026
One-click install
npx skills add https://github.com/metaid-developers/metaapp-skills --skill metaapp-builder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: metaapp-builder
Source: https://github.com/metaid-developers/metaapp-skills/tree/main/metaapp-builder
Command: npx skills add https://github.com/metaid-developers/metaapp-skills --skill metaapp-builder

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Packages completed MetaApp frontend projects into distributable ZIP archives for deployment, distribution, and archival sharing.

Core Features & Use Cases

  • Automatically detects the MetaApp project structure and validates required files and directories.
  • Packages the project into a timestamped dist-<timestamp>.zip, excluding development artifacts.
  • Produces a usable archive placed at the project root or a specified output path.

Quick Start

Run the packaging script on your MetaApp project root to generate a dist-<timestamp>.zip archive.

Frequently Asked Questions about metaapp-builder

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

FAQPage Schema
How do I package a frontend project into a ZIP archive for distribution?

To package a frontend project into a ZIP archive, the builder validates the MetaApp project structure and generates a timestamped dist-<unix_timestamp>.zip file for deployment and distribution.

What files are required to bundle a MetaApp project for release?

Bundling a MetaApp project requires the frontend project to contain index.html, app.js, app.css, idframework.js, alongside the idcomponents and commands directories for structural validation.

Does the packaging process exclude development artifacts from the ZIP file?

Yes, the packaging process excludes development artifacts when creating the timestamped ZIP archive, ensuring only the validated MetaApp frontend structure is distributed.

Can I specify a custom output path for the generated distribution ZIP?

You can specify a custom output path for the distribution ZIP, or the packaging script will place the generated timestamped archive at the project root by default.

What is the best way to archive a completed MetaApp frontend project?

The best way to archive a MetaApp frontend project is running the packaging script, which validates required files and produces a timestamped ZIP for archival storage and transport.