dna-exchange-skill

Export DNA between Ori agents via A2A binary content with inline tarball packaging.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/misunders2d/ori --skill dna-exchange-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dna-exchange-skill
Source: https://github.com/misunders2d/ori/tree/main/skills/dna-exchange-skill
Command: npx skills add https://github.com/misunders2d/ori --skill dna-exchange-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

DNA exchange shares technical improvements (tools/skills) between Ori agents over the A2A connection. It is strictly a communication event — no commits, no reboots, during a transfer.

Core Features & Use Cases

  • Export and import DNA (tools/skills) between Ori agents using inline binary content carried in A2A messages.
  • Includes sandbox isolation, inline tarball packaging, artifact-based verification, and safety guardrails to prevent evolutions or reboots during transfer.
  • Use Case: Seamlessly move code and configurations across agents to accelerate collaboration without disrupting ongoing sessions.

Quick Start

Transfer DNA between Ori agents by packaging selected modules into an in-memory tarball and sending it inline over A2A, ensuring you do not reboot or commit during the transfer.

Frequently Asked Questions about dna-exchange-skill

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

FAQPage Schema
How do I securely transfer code and configurations between Ori agents?

You can securely transfer code and configurations between Ori agents by using A2A binary content to package selected modules into an in-memory tarball. This ensures safe DNA exchange without triggering reboots or evolution events.

Can I share tools between agents without rebooting or committing during the transfer?

Yes, DNA exchange is strictly a communication event that applies safety guardrails to prevent reboots, commits, or evolutions during the transfer. This allows you to move assets across agents without disrupting ongoing sessions.

How does sandbox verification work for A2A binary content transfers?

Sandbox verification for A2A binary content transfers works by enforcing per-transfer sandbox isolation and artifact-based verification. This mechanism validates the in-memory tarball packages before allowing the receiving agent to import the shared tools.

What is the best way to package assets for DNA exchange over A2A connections?

The best way to package assets for DNA exchange is to use inline tarball packaging. This method bundles code, configs, and assets into an in-memory archive sent inline over A2A, ensuring seamless collaboration without session disruption.

Are there limitations on transferring code over A2A during an active agent session?

A key limitation is that you must not reboot or commit during an active DNA transfer over A2A. The process enforces safety guardrails to prevent these evolution triggers, restricting transfers to purely communication events.

Do I need an A2A connection to import DNA and skills across Ori agents?

Yes, an A2A connection is required to export and import DNA between Ori agents. The transfer relies on A2A binary content to carry the in-memory tarball packages securely across the connection.