Skip to content

Latest commit

 

History

History
79 lines (50 loc) · 2.38 KB

File metadata and controls

79 lines (50 loc) · 2.38 KB

Building the Paclet

This guide covers how to build AgentTools for distribution.

Basic Build

Build the paclet using:

wolframscript -f Scripts/BuildPaclet.wls

This script builds the paclet and performs necessary checks.

Build Options

Option Description Default
--check Run code checks true
--install Install the paclet after building false
--mx Build MX files true

Examples

Build and install:

wolframscript -f Scripts/BuildPaclet.wls --install=true

Build without code checks (faster, for quick iteration):

wolframscript -f Scripts/BuildPaclet.wls --check=false

Build without MX file:

wolframscript -f Scripts/BuildPaclet.wls --mx=false

Build Output

The built paclet will be placed in the build/ directory. The output includes:

  • The .paclet file for distribution
  • MX files (unless disabled) for faster loading

MX Files

MX files are pre-compiled versions of the paclet that load faster. During the MX build, error handling tags are also rewritten to include source file locations for easier debugging (see Error Handling - Modified Definition).

During development, you may want to:

  • Disable MX building with --mx=false for faster build iterations
  • Delete existing MX files (Kernel/64Bit/AgentTools.mx) when testing source changes

See Getting Started for more details on MX files during development.

Building Agent Skills

Agent skills are built separately from the paclet. The build script generates .wls scripts from MCP tool definitions and distributes them to skill directories:

wolframscript -f Scripts/BuildAgentSkills.wls

This generates scripts, copies shared references, updates version numbers in SKILL.md frontmatter and .claude-plugin/marketplace.json, and cleans up temporary files.

See agent-skills.md for full details on the agent skills system and build process.

See Also