inspect-agent-package

Inspect .akita-agent package metadata, bundled skills, and validation errors without installing.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inspect a .akita-agent package file without installing it to avoid accidental installs, detect identifier conflicts, and surface validation errors before importing an agent into a workspace.

Core Features & Use Cases

  • Manifest and profile preview: display package metadata and agent configuration for quick verification.
  • Bundled skills enumeration: list and summarize bundled skills so developers can evaluate included capabilities.
  • Validation and conflict reporting: surface validation_errors, id_conflict status, and package_size to support safe import decisions.
  • Use Case: audit third-party agent bundles in CI or locally before adding them to a multi-agent system.

Quick Start

Open the .akita-agent file at /path/to/package.agk and run the inspect-agent-package handler to preview the manifest, profile, bundled skills, validation errors, id conflicts, and package size without installing it.

Frequently Asked Questions about inspect-agent-package

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

FAQPage Schema
How do I inspect a .akita-agent package without installing it?▼

To inspect a .akita-agent package without installing it, open the package file and run the inspect-agent-package handler to preview the manifest, profile, and bundled skills safely.

Can I check for validation errors and id conflicts before importing an agent bundle?▼

Yes, you can check for validation_errors and id_conflict status before importing an agent bundle by previewing the package contents to surface any metadata or identifier conflicts safely.

What is the best way to audit third-party agent bundles in CI pipelines?▼

The best way to audit third-party agent bundles in CI pipelines is to run a package inspection handler that parses the manifest, enumerates bundled skills, and reports validation errors without installation.

Does previewing an agent package show the bundled skills and package size?▼

Yes, previewing an agent package displays the bundled skills enumeration and package_size alongside the manifest metadata, allowing developers to evaluate included capabilities for import decisions.

Why should I preview agent package contents before adding them to a multi-agent system?▼

You should preview agent package contents before adding them to a multi-agent system to avoid accidental installs, detect identifier conflicts, and surface validation errors prior to workspace import.

What metadata is available when inspecting an .akita-agent file?▼

When inspecting an .akita-agent file, the available metadata includes the agent manifest, profile configuration, bundled skills summary, validation state, id conflict status, and overall package size.