How do I install the Dust Call Agent skill?

Run npx skillmds@latest add tomevault-io/dust-call-agent in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Dust Call Agent safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Dust Call Agent?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Dust Call Agent free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Dust Call Agent?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Dust Call Agent by tomevault-io — Agent Skill

Name: Dust Call Agent
Author: tomevault-io

Dust Call Agent

Call a Dust agent to get information (read a slack thread, a notion URL, a google drive document...), perform an action (post a message to slack, create a calendar event, ...), provide context on any topic regarding Dust (the company, current discussions, customers...) or in general have the Dust agent perform a given task. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

Access Dust agents that have context on all the company, e.g. recent projects, engineering, sales, marketing, etc., via the Dust CLI non-interactively, e.g.: $ dust chat -a issueBot -m "create an issue for this: ..." $ dust chat -a deep-dive -m "Research all info we have on kubernetes probe failures in recent weeks."

A conversation with an agent can be continued after the first message using the argument -c CONVERSATION_STRING_ID. The conversation id will be returned in the JSON result from the initial call. $ dust chat -a issueBot -c 'TdWyn4aDt1' -m "also add a subsequent issue about this: ..."

Use --projectName or --projectId to create the conversation inside a specific project (space). These cannot be used with -c (only for new conversations): $ dust chat -a prea --projectName "Engineering" -m "summarize recent incidents" $ dust chat -a prea --projectId "abc123" -m "summarize recent incidents"

Use -d / --details to get detailed message information in the output (raw event stream, tool actions, and full agent message payload): $ dust chat -a prea -d -m "what's the status of project X?"

If the CLI errors because login is needed, ask the user to perform it manually.

An agent may take long to answer. Avoid repeating an agent call if possible, especially if it timed out without a clear error, because:

the agent call may not be idempotent, e.g. when creating an issue, if the conversation on Dust has been started, repeating will create two issues;
multiple conversations are created in the user's Dust workspace, which bloats their conversation history.

If the CLI timed out but returned a conversationId and messageId, you can safely fetch the result without side effects: $ dust chat -c <conversationId> --messageId <messageId>

Otherwise, wait for a clear answer. If you decide to time out with no conversation ID, make no assumption on success or failure; report back to the user.

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: dust-call-agentdescription: Call a Dust agent to get information (read a slack thread, a notion URL, a google drive document...), perform an action (post a message to slack, create a calendar event, ...), provide context on any topic regarding Dust (the company, current discussions, customers...) or in general have the Dust agent perform a given task. Use when this capability is needed.---Access Dust agents that have context on all the company, e.g. recent projects, engineering, sales, marketing, etc., via the Dust CLI non-interactively, e.g.:`$ dust chat -a issueBot -m "create an issue for this: ..."``$ dust chat -a deep-dive -m "Research all info we have on kubernetes probe failures in recent weeks."`A conversation with an agent can be continued after the first message using the argument `-c CONVERSATION_STRING_ID`. The conversation id will be returned in the JSON result from the initial call.`$ dust chat -a issueBot -c 'TdWyn4aDt1' -m "also add a subsequent issue about this: ..."`Use `--projectName` or `--projectId` to create the conversation inside a specific project (space). These cannot be used with `-c` (only for new conversations):`$ dust chat -a prea --projectName "Engineering" -m "summarize recent incidents"``$ dust chat -a prea --projectId "abc123" -m "summarize recent incidents"`Use `-d` / `--details` to get detailed message information in the output (raw event stream, tool actions, and full agent message payload):`$ dust chat -a prea -d -m "what's the status of project X?"`If the CLI errors because login is needed, ask the user to perform it manually.An agent may take long to answer. Avoid repeating an agent call if possible, especially if it timed out without a clear error, because:- the agent call may not be idempotent, e.g. when creating an issue, if the conversation on Dust has been started, repeating will create two issues;- multiple conversations are created in the user's Dust workspace, which bloats their conversation history.If the CLI timed out but returned a `conversationId` and `messageId`, you can safely fetch the result without side effects:`$ dust chat -c <conversationId> --messageId <messageId>`Otherwise, wait for a clear answer. If you decide to time out with no conversation ID, make no assumption on success or failure; report back to the user.---> Converted and distributed by [TomeVault](https://tomevault.io/claim/dust-tt) — claim your Tome and manage your conversions.

Frequently asked questions