import

Import workspace templates from local files, URLs, or GitHub repositories with collision handling and secret prompts.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Stand up a workspace from an exported template with collision awareness, preview, and secret prompts.

Core Features & Use Cases

  • Preview templates before provisioning to see created files, agents, and budgets.
  • Resolve conflicts using rename, skip, replace, or interactive prompts.
  • Import templates from local files, URLs, or GitHub repositories and provision the workspace.

Quick Start

Run the import command with a path to a template to provision a new workspace.

Frequently Asked Questions about import

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

FAQPage Schema
How do I import a workspace template without overwriting existing files?

You can import a workspace template safely by using collision handling strategies like rename, skip, replace, or interactive prompts to prevent overwriting existing files during the provisioning process.

Can I preview files and agents before provisioning a workspace template?

Yes, you can run a dry-run preview before provisioning a workspace template to see exactly which files, agents, and budgets will be created without making any actual changes to your environment.

Does workspace template provisioning work with GitHub repositories and URLs?

Workspace template provisioning works directly with local files, remote URLs, and GitHub repositories, allowing you to pull templates from external sources and automatically provision the workspace.

How do I manage secrets and environment variables when importing a workspace?

When importing a workspace, the process supports secret tracking and environment prompts, interactively asking you to provide required secrets during the launch phase of the provisioning workflow.

What is the best way to resolve file collisions when standing up a workspace?

The best way to resolve file collisions when standing up a workspace is using an acquire-preview-resolve workflow, letting you choose to rename, skip, or replace conflicting files interactively.

Do I need to install dependencies before importing a workspace template?

No dependencies are required to import a workspace template, as the Skill operates independently to acquire templates from local files, URLs, or GitHub repositories and provision them with targeted installation.