ls-agentq-transport

Coordinate bidirectional PRD and artifact transport via file_drop and mail protocols.

3|2|Updated Dec 25, 2025
One-click install
npx skills add https://github.com/CruxExperts/localsetup --skill ls-agentq-transport
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ls-agentq-transport
Source: https://github.com/CruxExperts/localsetup/tree/main/_localsetup/skills/ls-agentq-transport
Command: npx skills add https://github.com/CruxExperts/localsetup --skill ls-agentq-transport

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enables reliable, bidirectional transport of PRDs and artifacts between agents using file_drop (shared folders with ready markers) or mail (policy-gated) with optional strict gpg pre-encryption, while validating trusted registries and schemas.

Core Features & Use Cases

  • Bidirectional transfer via file_drop and mail workflows with policy gating.
  • Registry validation, queue management, and archive pruning to ensure integrity and traceability.
  • CLI-driven control via the agentq_transport_client tool, supporting on-prem and local-repo workflows.

Quick Start

Run the agentq transport CLI to ship a PRD between Agent A and Agent B using the file_drop workflow.

Frequently Asked Questions about ls-agentq-transport

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

FAQPage Schema
How do I transport PRDs between agents using a shared folder?

Transport PRDs between agents via shared folders by writing sealed manifests with ready markers using the file_drop workflow, validating the agent_trust_registry.yaml and manifest.schema.json before the receiving agent ingests the artifacts.

What is the best way to securely ship artifacts between agents via mail?

Shipping artifacts between agents via mail requires policy-gated workflows with optional strict gpg pre-encryption, validating trusted registries and schemas to ensure integrity and traceability during the bidirectional transfer.

Do I need a configured trust registry before transferring PRDs between agents?

A configured trust registry is required before transferring PRDs, as the transport client validates agent_trust_registry.yaml and manifest.schema.json to ensure sealed manifests are securely exchanged between trusted agents.

How do I update agent_trust_registry.yaml when ingesting new PRDs?

Update agent_trust_registry.yaml during PRD ingestion by running the agentq transport client CLI, which validates the incoming sealed manifest against the schema and applies registry updates across configured paths.

Can I use gpg pre-encryption for file_drop workflows?

Strict gpg pre-encryption can be applied to file_drop workflows to securely seal PRD manifests before writing them to shared folders, ensuring artifacts remain encrypted until the destination agent ingests them.

Why does my agentq transport CLI fail to validate the manifest schema?

Manifest schema validation fails when the sealed manifest does not conform to manifest.schema.json or the agent_trust_registry.yaml lacks the required trust entries, preventing untrusted agents from ingesting artifacts.