crafttable-mcp-client/skills/crafttable/SKILL.md

name, description

name

description

crafttable

Use the configured CraftTable MCP when a task involves project spaces, members, documents, document folders, Markdown content, Kanban work items, workspace knowledge, or AI suggestion cards. Invoke proactively when CraftTable may contain the authoritative project context needed to answer or act, even if the user does not explicitly ask to use CraftTable. Do not invoke for unrelated local-code work.

CraftTable

Use the MCP server named crafttable when it is mounted in the current session. If it is not mounted, use the installed crafttable-mcp-client CLI (or the compatible crafttable-mcp command alias) instead. Do not substitute direct HTTP calls, override the configured server URL, or expose OAuth credentials.

For CLI access, use status to check connectivity, tools or resources to discover the remote surface, call <tool> '<json>' to invoke a tool, and read <uri> for an MCP resource. Run login only when status reports that the user is not logged in.

Workflow

1. Confirm the connection through the mounted MCP server or crafttable-mcp-client status, then call list_spaces when the target space ID is unknown. Match by name and ask only when multiple spaces remain plausible.
2. Read the smallest useful surface before answering or changing data. Prefer overview and list tools, then fetch a specific work item or document.
3. Treat CraftTable as the source of truth for workspace state. Do not infer current members, tasks, document text, or project knowledge from stale conversation context when MCP reads are available.
4. Perform writes only when the user's request authorizes that state change. Keep changes within the named space and object.
5. Before updating Markdown, call get_document and pass its currentRevisionId as baseRevisionId to update_markdown_document.
6. Pass confirm: true to deletion tools only after the user has explicitly confirmed the specific deletion.

Respect membership roles, enabled-plugin checks, and MCP errors. Never try to bypass a denied operation. Do not run configure or unconfigure unless the user explicitly asks to change an agent's MCP registration. If the user is not logged in, ask them to run crafttable-mcp-client login (or crafttable-mcp login); never open a login page from an Agent stdio session.