Executor

I built Executor for jobs where the findings belong on your CRM board. Large lists and raw API responses can fill an agent conversation before the results reach the records that need them. Executor handles that transfer on the server, so your agent can coordinate the work and check its progress.

Choose a supported skill with listSkills, then give run a task or board and an explicit source column, such as pending. The server fetches the data, runs the skill, writes findings into OPVS CRM board records and moves cards according to the result. Your agent receives a job ID and checks getStatus every 2–5 minutes.

The skill exposes 4 methods: run, getStatus, cancel and listSkills. Progress includes completed, failed and skipped counts. Cancel stops after the current batch and preserves results already written.

Use Executor when bulk findings can stay on the board. When your agent needs those findings to reason about the next step, bring the relevant data into the conversation. Install @opvs-ai/executor and ask it to enrich a board.