Async Repl Protocol
- 459 installs
- 3.9k repo stars
- Updated January 26, 2026
- parcadei/continuous-claude-v3
async-repl-protocol is an agent skill that enforces Agentica async REPL harness rules—awaiting Future-returning tools and keeping compute-and-return logic in a single executable code block per response.
About
async-repl-protocol is a Claude Code skill from parcadei/continuous-claude-v3 for correct usage of Agentica's async REPL testing harness. The skill requires await on Future-returning tools like view_file and ask_memory, and mandates a single Python code block per response because only the first block executes—split blocks leave later statements unreachable. Developers reach for async-repl-protocol when Agentica REPL tests silently skip logic, async file reads return coroutine objects, or multi-block responses fail to run follow-up computations during harness-driven agent validation.
- async-repl-protocol
Async Repl Protocol by the numbers
- 459 all-time installs (skills.sh)
- +2 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #905 of 4,347 Backend & APIs skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/parcadei/continuous-claude-v3 --skill async-repl-protocolAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 459 |
|---|---|
| repo stars | ★ 3.9k |
| Last updated | January 26, 2026 |
| Repository | parcadei/continuous-claude-v3 ↗ |
How do you use Agentica async REPL tools correctly?
Use async-repl-protocol for development tasks
Who is it for?
Developers writing or debugging Agentica async REPL harness tests that call view_file, ask_memory, or similar Future tools.
Skip if: Synchronous scripts outside the Agentica async REPL harness should skip async-repl-protocol.
When should I use this skill?
Agentica REPL harness tests skip code, coroutines are not awaited, or only the first of multiple code blocks executes.
What you get
Correctly awaited tool calls, single-block REPL responses, and reliable harness test execution
- Correct async REPL test patterns
Files
Async REPL Protocol
When working with Agentica's async REPL harness for testing.
Rules
1. Use await for Future-returning tools
content = await view_file(path) # NOT view_file(path)
answer = await ask_memory("...")2. Single code block per response
Compute AND return in ONE block. Multiple blocks means only first executes.
# GOOD: Single block
content = await view_file(path)
return any(c.isdigit() for c in content)
# BAD: Split blocks (second block never runs)
content = await view_file(path)
Related skills
Lark Openapi ExplorerInstantly explore, test, and generate calls against the full Lark (Feishu) OpenAPI surface without leaving their agent workflow.493k
Lark EventConsume real-time events from Lark/Feishu as structured NDJSON streams inside AI agent workflows.387k16kLark Openapi ExplorerWhen an existing Lark/Feishu skill or CLI command cannot fulfill a specific requirement and they need to discover and invoke the exact native OpenAPI endpoint.386k16k
Just ScrapeQuickly search, crawl, extract structured JSON, or monitor web pages without writing custom scraping code.245k41Lark AppsQuery the current visibility and permission scope of a Lark (Feishu) app without writing HTTP client code.235k16k
Design An InterfaceGenerate multiple radically different interface or API designs in parallel before committing to one.188k198kHow it compares
Use async-repl-protocol alongside agentica-prompts when failures stem from REPL execution rules, not prompt wording.
FAQ
Why must async-repl-protocol use a single code block?
async-repl-protocol states Agentica's async REPL executes only the first code block per response. Additional blocks never run, so compute-and-return logic must live in one block.
Which Agentica tools require await?
async-repl-protocol requires await on Future-returning tools such as view_file and ask_memory. Calling them without await returns coroutines that never resolve in harness tests.