List browser skills
well_list_browser_skillsList the user's own saved browser tasks: the website tasks they saved after a run so Well can do them again (a bank statement to download, the invoices of a supplier's portal). Call it when the user asks to see, edit, unpublish, republish or delete their saved tasks ("mes tâches enregistrées", "show my saved tasks"), and before well_update_browser_skill or well_delete_browser_skill when no list was read in this conversation.
Each saved task has its name, its version, its status (published or draft, which is unpublished) and the site it runs on. Show them as a numbered list, one line each, and never show browser_skill_id. The list only reads: it changes nothing, and each change is its own call.
Only the user's own saved tasks are listed; another member's are never visible. An empty list means the user saved none.
When the token authorizes one workspace, call this directly — no workspace call is needed first. When it authorizes several, this read will not guess which one you mean: pass workspace_id on the call.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| workspace_id | No | Target workspace. Omit when the token authorizes one workspace. Required when it authorizes several: this read reports one workspace's own figures and will not choose which. | |
| conversation_id | No | The conversation id returned by the previous Well result, in its meta under well/conversation_id, in its structuredContent, or in its JSON text block. Pass it back on every call in the same conversation, including a call a card makes, so the chosen workspace and the earlier answers still apply. It decides the conversation on its own: nothing the host states about the session replaces it. Omit it only on the first call of a conversation. | |
| workspace_scope | No | Restrict this call to the family: the token's primary workspace plus the company workspaces under it that you are a member of. Unrelated authorized workspaces drop out of the read; row reads merge across the family, while a per-workspace figure still reports exactly one workspace. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| error | No | ||
| total | No | How many saved tasks the person has, listed or not. | |
| success | Yes | ||
| saved_tasks | No | The person's own saved browser tasks, the most recently changed first. Absent on failure. | |
| conversation_id | No | The conversation this result belongs to. Pass it back as the conversation_id argument on every later Well call in the same conversation. | |
| newly_connected | No | Tools that connected to this workspace since the last result and that no session was told about yet, oldest first. Present only when at least one tool is new. The connected-line rule says when to tell an entry; when it does, one line per entry, in the person's language: "<name> is connected.". Never fold several entries into one sentence. Each entry comes back once, on one result only: never repeat its line later. | |
| resolved_workspace | No | The workspace that answered, when the caller named none and the token authorizes several. | |
| conversation_id_note | No | Present only when the server opened a fresh lane, stating that no choice recorded earlier was read. | |
| conversation_id_source | No | Where the conversation id came from: the host's own request meta, the caller's argument, or a fresh lane the server opened. |