automap

Automate headless AutoMap builds for WebWorks ePublisher projects.

1|Updated Dec 5, 2025
One-click install
npx skills add https://github.com/quadralay/webworks-claude-skills --skill automap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: automap
Source: https://github.com/quadralay/webworks-claude-skills/tree/main/plugins/webworks-claude-skills/skills/automap
Command: npx skills add https://github.com/quadralay/webworks-claude-skills --skill automap

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Automates the repetitive task of building WebWorks ePublisher outputs by orchestrating AutoMap CLI runs.

Core Features & Use Cases

  • Automatic AutoMap installation detection and path normalization
  • Single-target and multi-target builds with safe defaults for CI and local development
  • Job file creation, stationery integration, and deployment orchestration
  • Real-world use case: streamline nightly builds of a multi-format publication with consistent output

Quick Start

Ask Claude Code to run the automap wrapper on your project file to build all targets.

Frequently Asked Questions about automap

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

FAQPage Schema
How do I automate WebWorks ePublisher builds for CI/CD pipelines?

Automate WebWorks ePublisher builds by orchestrating AutoMap CLI runs headlessly. This Skill handles argument wrapping, target selection, and deployment workflows for .wep, .wrp, and .wxsp project files.

Do I need AutoMap CLI installed to run headless ePublisher builds?

AutoMap CLI availability is required to run headless ePublisher builds, but the Skill includes automatic installation detection and path normalization. It safely initializes single-target and multi-target builds with CI-safe defaults.

Can I build specific targets from a WebWorks job file instead of building everything?

Yes, you can build specific targets from a .waj job file. The wrapper-based argument handling enables precise target selection, stationery integration, and deployment orchestration for multi-format publications.

What's the best way to handle errors during automated AutoMap stationery builds?

Handle AutoMap stationery build errors through the wrapper's robust error reporting mechanism. It captures CLI failures during job file creation and target deployment, ensuring consistent output for nightly build workflows.

Does this AutoMap wrapper support both local development and CI environments?

The AutoMap wrapper supports both local development and CI environments by applying safe defaults for build execution. It normalizes installation paths and orchestrates end-to-end builds for .wep, .wrp, and .wxsp project formats.

Why does my headless AutoMap build fail to find the CLI installation path?

Headless AutoMap builds fail when the CLI installation path is not detected correctly. This Skill resolves path normalization issues automatically, applying safe defaults to ensure the wrapper finds and executes the necessary build targets.