Publisher for Openclaw

Deploy static HTML projects to the cloud and compile them into Android APK packages using automated publishing workflows.

publisher-skill
v0.1.0
Jul 8, 2026
0
332
0

Install & Download

1. ClawHub CLI

The fastest way to install a skill directly from the registry.

npx clawhub@latest install publisher-2

2. Manual Installation

Copy the skill folder to one of these locations

Global
~/.openclaw/skills/
Workspace
<project>/skills/

Priority: Workspace > Local > Bundled

3. Prompt Installation

Copy this prompt to OpenClaw to install it automatically.

Help me install publisher-2 using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).

Prefer to download?

Get the raw skill files in a ZIP archive.

What is Publisher?

The publisher skill is a command-driven extension designed to enable AI coding agents to deploy static HTML frontend applications directly to the cloud and compile them into executable Android APK packages. By leveraging either mounted Model Context Protocol (MCP) tools or direct HTTP fallbacks via curl, this skill simplifies the distribution lifecycle for developers, allowing direct translation of local source directories into shareable links.

This resource integrates natively with Openclaw Skills frameworks to provide interactive publishing pipelines. It coordinates version validation, account provisioning, private asset configuration, and automatic APK builds, enabling developers to streamline the pipeline from raw code to client-ready deliverables without leaving the agent-assisted workspace.

Publisher Use Cases

  • Publishing local HTML, CSS, and JavaScript directories to a cloud-hosted URL for preview or production.
  • Packaging web-based prototypes, games, or apps into native Android APK files for mobile installation.
  • Managing the access control of hosted web assets by toggling visibility between public access and password-protected private status.
  • Listing and monitoring previously published projects directly inside an Openclaw Skills session.
  • Seamless registration and automated token refresh handling across team deployments.

How Publisher Works

  1. Initiation and Version Check: The skill first triggers a non-blocking version check against the central registry to ensure compatibility with other Openclaw Skills.
  2. Credential Verification: It checks for existing session tokens in the local configuration or prompts the user to securely authenticate or register.
  3. Visibility Configuration: The workflow guides the user through selecting a public visibility state or a password-secured private state.
  4. Pre-Publish Validation: The local zip file is scanned to confirm the existence of a valid entry point, such as index.html.
  5. Execution and Build: The project is uploaded via the appropriate API or MCP tool endpoint, optionally triggering an Android SDK compilation sequence to output an installable APK.

Publisher Setup

Configure the local environment by defining credentials in the global configuration directory:

mkdir -p ~/.publisher
cat <<EOF > ~/.publisher/config.json
{
  "baseUrl": "https://ai-pub.pushwebly.com",
  "username": "your_username",
  "password": "your_password"
}
EOF
chmod 600 ~/.publisher/config.json

To verify the configuration and ensure the active version is running, perform a version probe:

curl -s https://ai-pub.pushwebly.com/api/skill/latest-version

Publisher Data Schema & Taxonomy

Configuration and Payload Models

The configuration profile is maintained in the home directory. The schema and API payload structures map as follows:

Attribute Description Location / Context
baseUrl Base URL of the publishing engine config.json
username Plain text username for authentication config.json
password Plain text password for authentication config.json
authorization Active Bearer authentication token Header / Config
visibility Access visibility (public or private) Request Payload
access_password Optional 6-digit access password Request Payload

Publisher Advanced Features

  • Finite-State Machine (FSM) Execution Flow: A multi-step validation sequence preventing misconfigured deployments and ensuring precise access options.
  • Hybrid MCP and HTTP Fallback Engine: Transitions between integrated Model Context Protocol tools and standard curl commands.
  • Automated APK Compilation: Packaging static assets into standard Android packages within minutes using server-side SDKs.
  • Local Credential Protection: Automatic file permission enforcement (chmod 600) on POSIX systems to secure login tokens within the home directory.
  • Adaptive Version Check Alerts: OS-specific update detection providing direct, clickable links matching the user's running platform.

SKILL.md


Loading

Related Openclaw Skills

METADATA

Github Stars: 0
forks: 0

Featured*