playbooks

home / skills / dust-tt / dust / dust-call-agent

dust-call-agent skill

/.claude/skills/dust-call-agent

This skill helps you access Dust agents to read, create, and manage information and tasks across projects, Slack, Notion, or Drive.

npx playbooks add skill dust-tt/dust --skill dust-call-agent

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
1.5 KB
---
name: dust-call-agent
description: 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.
---

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 tool errors because login is needed, ask the user to perform it manually.

Overview

This skill lets you call a Dust agent from the command line to fetch context, perform actions, or run tasks using company-wide knowledge. It integrates with Dust agents that have access to Slack threads, Notion pages, Google Drive docs, and internal Dust context. Use it to query, summarize, automate, or continue existing agent conversations non-interactively.

How this skill works

You invoke the Dust CLI with the chat command and specify an agent (-a) and a message (-m). For new conversations, you may scope the request to a project using --projectName or --projectId. To continue an existing conversation, pass the conversation id with -c returned in the initial JSON. Add -d / --details to return full event streams, tool actions, and raw agent payloads.

When to use it

  • Summarize threads, documents, or project state from company sources non-interactively.
  • Create or update artifacts (issues, calendar events, Slack posts) via an agent action.
  • Query Dust-specific context like recent projects, customers, or discussions.
  • Continue a multi-step agent interaction using a conversation id.
  • Collect detailed tool and event traces for debugging with --details.

Best practices

  • Start new workflows with a clear, specific prompt to the agent and include relevant context or links.
  • Use --projectName or --projectId when the task should be performed inside a specific project space.
  • Use -c with the conversation id to keep multi-step interactions coherent and maintain state.
  • Add -d only when you need debugging info or complete agent traces to avoid noisy output.
  • If a tool errors saying login is required, ask the user to sign in manually before retrying.

Example use cases

  • Create an issue: dust chat -a issueBot -m "create an issue for this: ..."
  • Research a topic: dust chat -a deep-dive -m "Research all info we have on kubernetes probe failures in recent weeks."
  • Project summary in a space: dust chat -a prea --projectName "Engineering" -m "summarize recent incidents"
  • Continue a conversation: dust chat -a issueBot -c 'TdWyn4aDt1' -m "also add a subsequent issue about this: ..."
  • Get full traces: dust chat -a prea -d -m "what's the status of project X?"

FAQ

How do I continue an existing conversation?

Use -c CONVERSATION_STRING_ID returned in the initial JSON response to continue the same agent conversation.

How do I scope a request to a project?

For new conversations, include --projectName or --projectId. These flags cannot be used with -c for continuing conversations.

What does --details (-d) return?

--details returns raw event streams, tool actions taken by the agent, and the full agent message payload for debugging and audit.