export

Package a running workspace into a portable template with secrets stripped.

Updated Apr 29, 2026
One-click install
npx skills add https://github.com/MantisWare/BizForge --skill export-mantisware
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: export
Source: https://github.com/MantisWare/BizForge/tree/main/library/skills/workspace/export
Command: npx skills add https://github.com/MantisWare/BizForge --skill export-mantisware

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Export a running workspace as a portable template that captures SYSTEM.md, agent definitions, skills, reference files, configuration, seed tasks, and budget defaults, while stripping secrets and environment-specific paths for clean re-import elsewhere.

Core Features & Use Cases

Package a running workspace into a reusable template that can be imported elsewhere. Captures the full workspace definition — agents, skills, configuration, seed tasks, budget defaults — while stripping secrets and environment-specific paths. The exported template is self-contained and portable: anyone with /import can stand up an identical workspace.

Quick Start

Run /export to create a portable template of the current workspace.

Frequently Asked Questions about export

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

FAQPage Schema
How do I export a workspace as a portable template?

Exporting a workspace template captures SYSTEM.md, agent definitions, skills, configuration, seed tasks, and budget defaults while stripping secrets and environment-specific paths for safe, portable re-import elsewhere.

What does workspace templating strip out for safe re-import?

Workspace templating strips secrets and environment-specific paths, logging required variables instead, to ensure the exported template is safe and portable for re-import into a new environment.

Can I share a running workspace configuration across different environments?

Yes, you can share a running workspace configuration across environments by packaging it into a portable template that captures systems, agents, and skills, allowing anyone with /import to stand up an identical setup.

What is the best way to package a workspace definition for replication?

The best way to package a workspace definition for replication is to use templating that captures agents, skills, configuration, and budget defaults into a self-contained format, enabling standardized deployment across multiple instances.

Does workspace export keep my budget defaults and seed tasks?

Yes, workspace export keeps your budget defaults and seed tasks, capturing the full workspace definition including SYSTEM.md, agent definitions, skills, reference files, and configuration into the portable template.

How do I import a workspace template after exporting it?

Importing a workspace template requires the /import command to stand up an identical workspace, reconstructing the systems, agents, skills, and configuration previously packaged during the export process.