OpenParable
Skip to content
← Back to skills

Repl Eca Development

Testing & Quality
repl-eca-development

Repl Eca Development is an Agent Skill for testing & quality published in the editor-code-assistant/eca repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

MANDATORY - Load this skill to learn how to use repl in eca project to manual test ECA behavior in a running ECA session. Useful to know how providers behave or do a end to end test.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/editor-code-assistant/eca/blob/HEAD/.eca/skills/repl-eca-development/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/repl-eca-development, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

REPL ECA Development

Requisites

  • Load any other repl skill if not loaded yet to know how to eval Clojure code.

Context

There is a running JVM ECA process running with a nrepl server available which is tied to the repl you have access, this is powerful to eval anything from eca project and see lively changing in that eca session. Use this when you need to understand how a provider behaves or part of the ECA code. When testing stuff, call high level functions which simulates a user interacting with ECA, so for example always use eca.features.chat/prompt to simulate chat talks.

Components

To access eca components to pass to functions during manual eval, you can:

  • db*: eca.db/db*
  • db: @eca.db/db*
  • config: (eca.config/all db)
  • messenger (-> db :dev :components :messenger)
  • metrics (-> db :dev :components :metrics)
  • server (-> db :dev :components :server)