Author a mode:code_execution automation — a single-file TypeScript handler (entrypoint:worker), the cheapest way to add selective LLM calls plus deterministic logic and writes to the org database, a scripted browser job (worker + capabilities:["browser"] +…
Cynap-ai/cynap-operator-plugin
- Latest recorded source activity
- SkillsMP catalog refreshed
- skills collected
- 15
- GitHub stars
- 0
- GitHub forks
- 0
Install with an AI assistant
Copy this prompt into the AI assistant you're using.
Follow https://skillsmp.com/skill-install/prompt.md to install Agent Skills from https://github.com/Cynap-ai/cynap-operator-plugin.Loading the repository README…
Skills in this repository
Showing 15 of 15 collected skills.
Diagnose why an automation run failed, using only the read tools an operator seat holds. Use when a run did not finish, ended failed, or a browser job with an `org:<id>` provider did not log in.
Read before authoring anything for a Cynap org — the compiles-but-breaks constraints that every automation, handler, flow, and schema change must satisfy regardless of mode.
Route an authoring task to the correct one of Cynap's 3 live automation modes (code_execution/flow/deterministic) before writing anything — the wrong mode fails config validation or wastes runtime budget.
Author a customer surface with its route and tool manifests, look at it with /cynap-render before pushing, then build it through the operator commit gate.
Author a conversational bot (WhatsApp/Slack/Roam DM) as a Flow-Runner config — the canonical path for all new conversational automations. Use after choose-the-right-mode routes here.
Use when an org automation, operation, Actor, flow, or code-execution handler needs text generation, structured extraction, classification, or a JEV evaluation.
Author a fixed-step scheduled sync, reconciler, or ETL automation with no agentic loop. Use after choose-the-right-mode routes here.
Author an aggregate saved query (analytics/saved-queries/*.sql) that an operator seat can read with operator_saved_query_run. Use when you need a count, total or breakdown of the org's data from an operator session.
Add an entity or admitted additive fields and annotations in a customer org's schema.json. Applies regardless of automation mode.
Map each operator scope to the workflows it unlocks and the tools each workflow uses. Use when a tool call is refused for scope, or before planning work, to see what your seat can do.
Compose the change_overview argument for workspace_commit — the structured AI-overview the owner sees on their review pane. Use this immediately before every workspace_commit call, after you finish authoring a change.
See what a Surface looks like before pushing it. Use whenever you author, restyle or change a Surface, or the human asks to see, preview or screenshot a page — /cynap-render builds it on the platform, writes nothing, and serves it locally on invented sample…
Put a customer's website chat widget live — author the webchat bot, its page-origin binding file and a guest-safe flow, activate them, then hand the customer the one-line install snippet (direct paste or a tag manager).
Right after you claim a build Request and before you author anything, call request_discover once to get ranked Cynap Apps and this org's own artifacts that may already cover the Request, and record your intended approach first.