Import/export

Package / Export

Understand .agentkit.zip packages, .onefile.md exports, and when to use each.

Who this is for

Users sharing, storing, installing, or preparing kits for web assistants.

Before you start

  • Validate the kit.
  • Decide who or what will consume the output.
  • Choose package, one-file Markdown, or local agent install.

Step-by-step guide

  1. 1

    Use .agentkit.zip for structured packages that can be imported later.

  2. 2

    Use .onefile.md for web assistants or quick review.

  3. 3

    Choose default export locations or select a destination.

  4. 4

    Share packages safely, especially if references include sensitive context.

  5. 5

    Keep the difference clear: package preserves structure; one-file flattens for portability.

Package / Export
Forge Current step Inputs Output
1
2
Prompt preview

.agentkit.zip and .onefile.md outputs

3

Tips

  • Use packages for reuse.
  • Use one-file Markdown for ChatGPT/Claude web workflows.
  • Check exported content before sharing outside your team.

Common mistakes / troubleshooting

  • Treating one-file Markdown as a full package replacement.
  • Sharing private references unintentionally.
  • Skipping validation before package.

Related guides

Install on Local Agent Export compatible kit content into local agent tools such as Codex and Claude Code. Import Kits Bring kits into Forge from .agentkit.zip files, folders, or Git repositories.