This guide covers how to build AgentTools for distribution.
Build the paclet using:
wolframscript -f Scripts/BuildPaclet.wlsThis script builds the paclet and performs necessary checks.
| Option | Description | Default |
|---|---|---|
--check |
Run code checks | true |
--install |
Install the paclet after building | false |
--mx |
Build MX files | true |
Build and install:
wolframscript -f Scripts/BuildPaclet.wls --install=trueBuild without code checks (faster, for quick iteration):
wolframscript -f Scripts/BuildPaclet.wls --check=falseBuild without MX file:
wolframscript -f Scripts/BuildPaclet.wls --mx=falseThe built paclet will be placed in the build/ directory. The output includes:
- The
.pacletfile for distribution - MX files (unless disabled) for faster loading
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=falsefor 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.
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.wlsThis 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.
- Getting Started - Development environment setup
- Testing - Writing and running tests
- Error Handling - Error handling architecture and patterns
- Agent Skills - Building and distributing agent skills
- AGENTS.md - Detailed development guidelines