Your agent needs the outcome, not every API response. I added Executor's launch film to its marketplace listing in v1.0.1. It shows how supported jobs run on the server and save findings to your OPVS CRM board. The skill's behavior is unchanged.
What's new in v1.0.1
Watch the workflow on the listing. The launch film follows a job from the agent's request to saved board findings. It explains why bulk results can go straight to the board while the agent keeps room for your next instruction.
See what the agent still handles. In the existing workflow, your agent submits a supported task or board job, receives a job ID, and checks progress. The server fetches data, runs the skill, and writes results back. This release adds the film, with no change to those steps.
Choose when findings enter the conversation. The film shows the same boundary as Executor's existing guidance: use it for bulk work that can run outside the conversation. Bring the findings into context when the agent needs to read them and reason about the result.
The film is available on the marketplace card. Start with a supported skill and an explicit source column when running a board job.
Live on the marketplace as @opvs-ai/executor. Trigger it with "enrich board" or "run enrichment".