Tools
This skill connects to a local Flask backend that wraps the Backboard SDK. The backend must be running on http://localhost:5100.
backboard_create_assistant
Create a new Backboard assistant with a name and system prompt.
Parameters:
name (string, required): Name of the assistant
system_prompt (string, required): System instructions for the assistant
Example:
{
"name": "Support Bot",
"system_prompt": "You are a helpful customer support assistant."
}
backboard_list_assistants
List all available Backboard assistants.
Parameters: None
backboard_get_assistant
Get details of a specific assistant.
Parameters:
assistant_id (string, required): ID of the assistant
backboard_delete_assistant
Delete an assistant.
Parameters:
assistant_id (string, required): ID of the assistant to delete
backboard_create_thread
Create a new conversation thread for an assistant.
Parameters:
assistant_id (string, required): ID of the assistant to create thread for
backboard_list_threads
List all conversation threads, optionally filtered by assistant.
Parameters:
assistant_id (string, optional): Filter threads by assistant ID
backboard_get_thread
Get a thread with its message history.
Parameters:
thread_id (string, required): ID of the thread
backboard_send_message
Send a message to a thread and get a response.
Parameters:
thread_id (string, required): ID of the thread
content (string, required): Message content
memory (string, optional): Memory mode - "Auto", "Readonly", or "off" (default: "Auto")
backboard_add_memory
Store a memory for an assistant that persists across conversations.
Parameters:
assistant_id (string, required): ID of the assistant
content (string, required): Memory content to store
metadata (object, optional): Additional metadata for the memory
Example:
{
"assistant_id": "asst_123",
"content": "User prefers Python programming and dark mode interfaces",
"metadata": {"category": "preferences"}
}
backboard_list_memories
List all memories for an assistant.
Parameters:
assistant_id (string, required): ID of the assistant
backboard_get_memory
Get a specific memory.
Parameters:
assistant_id (string, required): ID of the assistant
memory_id (string, required): ID of the memory
backboard_update_memory
Update an existing memory.
Parameters:
assistant_id (string, required): ID of the assistant
memory_id (string, required): ID of the memory
content (string, required): New content for the memory
backboard_delete_memory
Delete a memory.
Parameters:
assistant_id (string, required): ID of the assistant
memory_id (string, required): ID of the memory to delete
backboard_memory_stats
Get memory statistics for an assistant.
Parameters:
assistant_id (string, required): ID of the assistant
backboard_upload_document
Upload a document to an assistant or thread for RAG (Retrieval-Augmented Generation).
Parameters:
assistant_id (string, optional): ID of the assistant (use this OR thread_id)
thread_id (string, optional): ID of the thread (use this OR assistant_id)
file_path (string, required): Path to the document file
Supported file types: PDF, DOCX, XLSX, PPTX, TXT, CSV, MD, PY, JS, HTML, CSS, XML, JSON
backboard_list_documents
List documents for an assistant or thread.
Parameters:
assistant_id (string, optional): ID of the assistant
thread_id (string, optional): ID of the thread
backboard_document_status
Check the processing status of an uploaded document.
Parameters:
document_id (string, required): ID of the document
backboard_delete_document
Delete a document.
Parameters:
document_id (string, required): ID of the document to delete
Instructions
When the user asks about:
Memory Operations
- "Remember that..." or "Store this..." → Use
backboard_add_memory
- "What do you remember about..." → Use
backboard_list_memories or backboard_get_memory
- "Forget..." or "Delete memory..." → Use
backboard_delete_memory
- "Update my preference..." → Use
backboard_update_memory
Document Operations
- "Upload this document" or "Index this file" → Use
backboard_upload_document
- "What documents do I have?" → Use
backboard_list_documents
- "Is my document ready?" → Use
backboard_document_status
Assistant Management
- "Create a new assistant" → Use
backboard_create_assistant
- "List my assistants" → Use
backboard_list_assistants
- "Delete assistant" → Use
backboard_delete_assistant
Conversation Threading
- "Start a new conversation" → Use
backboard_create_thread
- "Show conversation history" → Use
backboard_get_thread
- "Send message to thread" → Use
backboard_send_message
General Guidelines
- Always confirm successful operations with the user
- When creating assistants, suggest meaningful names and system prompts
- For document uploads, verify the file type is supported before attempting
- When using memory, explain what information is being stored
- Thread IDs and assistant IDs should be stored/tracked for the user's context
Examples
Example 1: Store a User Preference
- User: "Remember that I prefer dark mode and Python code examples"
- Action: Call
backboard_add_memory with content "User prefers dark mode interfaces and Python code examples" and metadata {"category": "preferences"}
- Response: "I've stored your preferences. You prefer dark mode and Python code examples."
Example 2: Create an Assistant
- User: "Create a code review assistant"
- Action: Call
backboard_create_assistant with name "Code Reviewer" and system_prompt "You are an expert code reviewer. Analyze code for bugs, performance issues, and best practices. Provide constructive feedback."
- Response: "Created your Code Reviewer assistant (ID: asst_xxx). It's ready to review code and provide feedback."
Example 3: Upload and Query a Document
- User: "Upload my project documentation and then tell me what it covers"
- Action 1: Call
backboard_upload_document with the file
- Action 2: Wait for processing, check status with
backboard_document_status
- Action 3: Use
backboard_send_message with memory="Auto" to query about the document
- Response: "I've uploaded and indexed your documentation. Based on the content, it covers..."
Example 4: Start a Threaded Conversation
- User: "Start a new conversation with my support assistant"
- Action: Call
backboard_create_thread with the assistant_id
- Response: "Started a new conversation thread (ID: thread_xxx). You can now send messages to your support assistant."
Backend Setup
The skill requires a running backend server. To start:
- Set the
BACKBOARD_API_KEY environment variable
- Navigate to the backend directory
- Run
./start.sh
The backend will be available at http://localhost:5100.
API Endpoints Reference
| Endpoint |
Method |
Description |
/health |
GET |
Health check |
/assistants |
GET, POST |
List/create assistants |
/assistants/{id} |
GET, PATCH, DELETE |
Get/update/delete assistant |
/assistants/{id}/threads |
GET, POST |
List/create threads for assistant |
/assistants/{id}/memory |
GET, POST |
List/add memories |
/assistants/{id}/memory/{mid} |
GET, PATCH, DELETE |
Get/update/delete memory |
/assistants/{id}/memory/stats |
GET |
Memory statistics |
/assistants/{id}/documents |
GET, POST |
List/upload documents |
/threads |
GET |
List all threads |
/threads/{id} |
GET, DELETE |
Get/delete thread |
/threads/{id}/messages |
POST |
Send message |
/threads/{id}/documents |
GET, POST |
List/upload thread documents |
/documents/{id}/status |
GET |
Document processing status |
/documents/{id} |
DELETE |
Delete document |
1---2name: backboard3description: Integrate Backboard.io for assistants, threads, memories, and document RAG via a local backend on http://localhost:5100.4---56## Tools78This skill connects to a local Flask backend that wraps the Backboard SDK. The backend must be running on `http://localhost:5100`.910### backboard_create_assistant1112Create a new Backboard assistant with a name and system prompt.1314**Parameters:**15- `name` (string, required): Name of the assistant16- `system_prompt` (string, required): System instructions for the assistant1718**Example:**19```json20{21 "name": "Support Bot",22 "system_prompt": "You are a helpful customer support assistant."23}24```2526### backboard_list_assistants2728List all available Backboard assistants.2930**Parameters:** None3132### backboard_get_assistant3334Get details of a specific assistant.3536**Parameters:**37- `assistant_id` (string, required): ID of the assistant3839### backboard_delete_assistant4041Delete an assistant.4243**Parameters:**44- `assistant_id` (string, required): ID of the assistant to delete4546### backboard_create_thread4748Create a new conversation thread for an assistant.4950**Parameters:**51- `assistant_id` (string, required): ID of the assistant to create thread for5253### backboard_list_threads5455List all conversation threads, optionally filtered by assistant.5657**Parameters:**58- `assistant_id` (string, optional): Filter threads by assistant ID5960### backboard_get_thread6162Get a thread with its message history.6364**Parameters:**65- `thread_id` (string, required): ID of the thread6667### backboard_send_message6869Send a message to a thread and get a response.7071**Parameters:**72- `thread_id` (string, required): ID of the thread73- `content` (string, required): Message content74- `memory` (string, optional): Memory mode - "Auto", "Readonly", or "off" (default: "Auto")7576### backboard_add_memory7778Store a memory for an assistant that persists across conversations.7980**Parameters:**81- `assistant_id` (string, required): ID of the assistant82- `content` (string, required): Memory content to store83- `metadata` (object, optional): Additional metadata for the memory8485**Example:**86```json87{88 "assistant_id": "asst_123",89 "content": "User prefers Python programming and dark mode interfaces",90 "metadata": {"category": "preferences"}91}92```9394### backboard_list_memories9596List all memories for an assistant.9798**Parameters:**99- `assistant_id` (string, required): ID of the assistant100101### backboard_get_memory102103Get a specific memory.104105**Parameters:**106- `assistant_id` (string, required): ID of the assistant107- `memory_id` (string, required): ID of the memory108109### backboard_update_memory110111Update an existing memory.112113**Parameters:**114- `assistant_id` (string, required): ID of the assistant115- `memory_id` (string, required): ID of the memory116- `content` (string, required): New content for the memory117118### backboard_delete_memory119120Delete a memory.121122**Parameters:**123- `assistant_id` (string, required): ID of the assistant124- `memory_id` (string, required): ID of the memory to delete125126### backboard_memory_stats127128Get memory statistics for an assistant.129130**Parameters:**131- `assistant_id` (string, required): ID of the assistant132133### backboard_upload_document134135Upload a document to an assistant or thread for RAG (Retrieval-Augmented Generation).136137**Parameters:**138- `assistant_id` (string, optional): ID of the assistant (use this OR thread_id)139- `thread_id` (string, optional): ID of the thread (use this OR assistant_id)140- `file_path` (string, required): Path to the document file141142**Supported file types:** PDF, DOCX, XLSX, PPTX, TXT, CSV, MD, PY, JS, HTML, CSS, XML, JSON143144### backboard_list_documents145146List documents for an assistant or thread.147148**Parameters:**149- `assistant_id` (string, optional): ID of the assistant150- `thread_id` (string, optional): ID of the thread151152### backboard_document_status153154Check the processing status of an uploaded document.155156**Parameters:**157- `document_id` (string, required): ID of the document158159### backboard_delete_document160161Delete a document.162163**Parameters:**164- `document_id` (string, required): ID of the document to delete165166## Instructions167168When the user asks about:169170### Memory Operations171- "Remember that..." or "Store this..." → Use `backboard_add_memory`172- "What do you remember about..." → Use `backboard_list_memories` or `backboard_get_memory`173- "Forget..." or "Delete memory..." → Use `backboard_delete_memory`174- "Update my preference..." → Use `backboard_update_memory`175176### Document Operations177- "Upload this document" or "Index this file" → Use `backboard_upload_document`178- "What documents do I have?" → Use `backboard_list_documents`179- "Is my document ready?" → Use `backboard_document_status`180181### Assistant Management182- "Create a new assistant" → Use `backboard_create_assistant`183- "List my assistants" → Use `backboard_list_assistants`184- "Delete assistant" → Use `backboard_delete_assistant`185186### Conversation Threading187- "Start a new conversation" → Use `backboard_create_thread`188- "Show conversation history" → Use `backboard_get_thread`189- "Send message to thread" → Use `backboard_send_message`190191### General Guidelines1921. Always confirm successful operations with the user1932. When creating assistants, suggest meaningful names and system prompts1943. For document uploads, verify the file type is supported before attempting1954. When using memory, explain what information is being stored1965. Thread IDs and assistant IDs should be stored/tracked for the user's context197198## Examples199200### Example 1: Store a User Preference201- User: "Remember that I prefer dark mode and Python code examples"202- Action: Call `backboard_add_memory` with content "User prefers dark mode interfaces and Python code examples" and metadata `{"category": "preferences"}`203- Response: "I've stored your preferences. You prefer dark mode and Python code examples."204205### Example 2: Create an Assistant206- User: "Create a code review assistant"207- Action: Call `backboard_create_assistant` with name "Code Reviewer" and system_prompt "You are an expert code reviewer. Analyze code for bugs, performance issues, and best practices. Provide constructive feedback."208- Response: "Created your Code Reviewer assistant (ID: asst_xxx). It's ready to review code and provide feedback."209210### Example 3: Upload and Query a Document211- User: "Upload my project documentation and then tell me what it covers"212- Action 1: Call `backboard_upload_document` with the file213- Action 2: Wait for processing, check status with `backboard_document_status`214- Action 3: Use `backboard_send_message` with memory="Auto" to query about the document215- Response: "I've uploaded and indexed your documentation. Based on the content, it covers..."216217### Example 4: Start a Threaded Conversation218- User: "Start a new conversation with my support assistant"219- Action: Call `backboard_create_thread` with the assistant_id220- Response: "Started a new conversation thread (ID: thread_xxx). You can now send messages to your support assistant."221222## Backend Setup223224The skill requires a running backend server. To start:2252261. Set the `BACKBOARD_API_KEY` environment variable2272. Navigate to the backend directory2283. Run `./start.sh`229230The backend will be available at `http://localhost:5100`.231232## API Endpoints Reference233234| Endpoint | Method | Description |235|----------|--------|-------------|236| `/health` | GET | Health check |237| `/assistants` | GET, POST | List/create assistants |238| `/assistants/{id}` | GET, PATCH, DELETE | Get/update/delete assistant |239| `/assistants/{id}/threads` | GET, POST | List/create threads for assistant |240| `/assistants/{id}/memory` | GET, POST | List/add memories |241| `/assistants/{id}/memory/{mid}` | GET, PATCH, DELETE | Get/update/delete memory |242| `/assistants/{id}/memory/stats` | GET | Memory statistics |243| `/assistants/{id}/documents` | GET, POST | List/upload documents |244| `/threads` | GET | List all threads |245| `/threads/{id}` | GET, DELETE | Get/delete thread |246| `/threads/{id}/messages` | POST | Send message |247| `/threads/{id}/documents` | GET, POST | List/upload thread documents |248| `/documents/{id}/status` | GET | Document processing status |249| `/documents/{id}` | DELETE | Delete document |