eda-system-packager

Package agent and skills infrastructure into a standalone repository-ready bundle.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Biswajit56546/EDAgent --skill eda-system-packager-biswajit56546
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eda-system-packager
Source: https://github.com/Biswajit56546/EDAgent/tree/main/skills/eda-system-packager
Command: npx skills add https://github.com/Biswajit56546/EDAgent --skill eda-system-packager-biswajit56546

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Package the agent+skill infrastructure into a standalone, portable repository-ready bundle with skill-local tool mirrors.

Core Features & Use Cases

  • Exports a portable, repository-ready bundle containing AGENTS.md, skills, core KB/tool docs, and tool registries.
  • Mirrors dependent scripts into each skill's references for portability and offline publication.
  • Produces a standalone, GitHub-ready folder structure including docs and selected scripts.

Quick Start

Run the build script to generate the standalone agent+skill bundle in exports/eda_agent_skill_system.

Frequently Asked Questions about eda-system-packager

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

FAQPage Schema
How do I package agent and skill infrastructure into a portable repository bundle?

To package agent and skill infrastructure, the system exports a standalone bundle containing AGENTS.md, skills, core KB/tool docs, and tool registries into a repository-ready folder structure for portability.

What does it mean to mirror dependent scripts into a skill's references for offline publication?

Mirroring dependent scripts copies required tool scripts directly into each skill's references directory, ensuring the skill remains fully functional and portable for offline publication without external script dependencies.

How do I create a GitHub-ready folder structure for my agent and skills?

Creating a GitHub-ready folder structure involves running the build script to generate a standalone bundle in exports/eda_agent_skill_system, complete with docs, selected scripts, and exported agent infrastructure.

Can I use this packaging workflow to export AGENTS.md and tool registries across multiple repositories?

Yes, the packaging workflow exports AGENTS.md, skills, core KB/tool docs, and tool registries into a standalone bundle designed specifically for portability and mirroring across multiple repositories.

What is included in a repository-ready agent and skill bundle?

A repository-ready agent and skill bundle includes AGENTS.md, the skills directory, core knowledge base documentation, tool registries, and selected mirrored scripts required for infrastructure portability.

Why does my skill packaging need to include mirrored scripts in the references directory?

Skill packaging includes mirrored scripts in the references directory to satisfy script mirroring requirements, ensuring each skill has local copies of dependent scripts for offline portability and standalone operation.