async-repl-protocol

Enforces await usage and single code blocks for Agentica's async REPL harness testing.

8|1|Updated Jan 4, 2026
One-click install
npx skills add https://github.com/scooter-lacroix/Maestro --skill async-repl-protocol
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: async-repl-protocol
Source: https://github.com/scooter-lacroix/Maestro/tree/main/maestro/skills/async-repl-protocol
Command: npx skills add https://github.com/scooter-lacroix/Maestro --skill async-repl-protocol

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides essential rules and guidelines for effectively using Agentica's asynchronous REPL harness during testing, ensuring correct execution of asynchronous operations.

Core Features & Use Cases

  • await keyword enforcement: Ensures that functions returning Futures are properly awaited.
  • Single code block execution: Guarantees that all computation and return statements are contained within a single, executable block.
  • Use Case: When developing and testing asynchronous agents, this Skill ensures that your test scripts correctly handle await calls and that each test step executes as a single, atomic unit.

Quick Start

Follow the rules outlined in this Skill to correctly test your asynchronous agent code.

Frequently Asked Questions about async-repl-protocol

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

FAQPage Schema
How do I test asynchronous agents that return Futures in a REPL?

Testing asynchronous agents in a REPL requires enforcing the `await` keyword for all Future-returning tools to ensure correct execution. This protocol mandates that functions returning Futures are properly awaited before proceeding.

Why does my async testing script fail when execution spans multiple code blocks?

Asynchronous testing scripts fail across multiple blocks because the protocol enforces single code block execution. All computation and return statements must be contained within a single, executable block to guarantee atomic unit execution.

What are the rules for deterministic task execution in an async testing framework?

Deterministic task execution in an async testing framework requires using the `await` keyword for Future-returning tools and consolidating all computation into a single code block per response for correct execution.

Can I execute multiple code blocks sequentially when testing async agents?

Executing multiple code blocks sequentially when testing async agents is not supported. The protocol mandates a single code block per response to ensure all computation and return statements execute as a single, atomic unit.

Do I need to use await for every tool call when testing asynchronous agents?

Using `await` for every tool call is required when testing asynchronous agents. The protocol enforces the `await` keyword specifically for functions returning Futures to ensure proper execution and deterministic results.

What is the best way to ensure correct execution of asynchronous operations during testing?

Ensuring correct execution of asynchronous operations during testing requires enforcing `await` for Future-returning tools and containing all computation within a single code block per response for atomic execution.