import-agent

Import .akita-agent packages, validate format, and install bundled skills.

9|2|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/AllBeingsFuture/AllBeingsFuture --skill import-agent-allbeingsfuture
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: import-agent
Source: https://github.com/AllBeingsFuture/AllBeingsFuture/tree/main/electron/embedded-assets/skills/system/import-agent
Command: npx skills add https://github.com/AllBeingsFuture/AllBeingsFuture --skill import-agent-allbeingsfuture

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Importing and installing third-party or exported Agent packages can be error-prone and manual, requiring validation of package contents, installation of bundled skills, and creation of agent profiles across different environments.

Core Features & Use Cases

  • Package Validation: Verifies .akita-agent package format and basic security before installation.
  • Skill Installation: Installs bundled skills into the local skills/custom/ directory for immediate use.
  • Agent Profile Creation: Creates a custom Agent profile (type forced to custom) and resolves ID conflicts with optional force overwrite.
  • Use Case: Migrate an exported agent with its skills from one workstation to another or install community-shared agent bundles.

Quick Start

Use the import-agent skill to install the .akita-agent package at /path/to/agent-package.asakita-agent into the local system and add its bundled skills.

Frequently Asked Questions about import-agent

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

FAQPage Schema
How do I install a .akita-agent package into my local system?

To install a .akita-agent package, you import it to validate the package format, install bundled skills into skills/custom/, and create a custom agent profile in the local system.

What happens when I import an agent package with conflicting skill IDs?

When importing an agent package with conflicting IDs, the process respects existing identifiers unless the force option is enabled, which allows the operation to overwrite conflicting IDs during profile creation.

Why does agent package installation fail without format validation?

Agent package installation fails without validation because the system must verify the .akita-agent package format and basic security checks before installing bundled skills and creating local agent profiles.

Can I migrate bundled skills from one workstation to another using .akita-agent files?

Yes, you can migrate bundled skills between workstations by importing the exported .akita-agent package, which installs the contained skills into the local skills/custom/ directory on the new environment.

Do I need to manually set up an agent profile after importing a package?

No, manual profile setup is not needed because importing the .akita-agent package automatically creates a custom agent profile, forcing the type to custom and resolving any ID conflicts during installation.