datalion

DataLion

Use this skill for DataLion project, project-settings, data-import, codebook, chart-table, report, report-tab, dashboard, and export workflows.

In DataLion, "tab" and "dashboard" are used interchangeably for the report subpages managed under a report.

Default Strategy

1. Verify the datalion MCP server is enabled and inspect which datalion__* tools are actually available in the current session.
2. Use MCP first for supported actions.
3. Do not invent Datalion MCP tools. If a matching tool is missing, switch to a REST or browser/UI path from references/setup-and-capabilities.md.
4. Read first, write second. Restate the exact target object and proposed mutation before calling a write path.

Setup

• Run HybridClaw in host sandbox mode for this local Node-based MCP server.
• Install the bridge dependencies before first use: npm --prefix <path-to-your-datalion-repo>/mcp install
• Keep DATALION_API_TOKEN inside MCP server config env, never in tracked files or chat.
• Use the MCP server name datalion so tools appear as datalion__....
• For hybridclaw gateway mcp add ..., pass the JSON config as one quoted shell argument. In zsh, unquoted {...} and [...] will be expanded before HybridClaw sees them.
• See references/setup-and-capabilities.md for ready-to-paste CLI and TUI examples, dependency notes, and ability requirements.

Working Rules

• Always state whether you are using MCP, REST API, or browser/UI automation.
• Resolve the exact project, report, dashboard, export, or chart before mutating anything.
• The current bridge directly supports project listing, project reads, project creation, project settings updates, data source listing, CSV upload, full Excel/CSV import, report list/create and tab CRUD, chart-table reads, and codebook list, download, generation, deletion, and upload.
• The bridge also exposes 4 browser URL helpers for project/report/dashboard opening and widget insertion.
• The current bridge tool surface has 22 tools total: 18 backend MCP actions and 4 browser URL helpers.
• Prefer datalion__list_projects and datalion__read_project before writes when the exact target project is not already pinned down.
• Treat datalion__upload_data as a data-import tool, not a generic project-update tool.
• Treat datalion__edit_project as a defsettings merge tool. It updates only the keys you pass and keeps the existing settings for all other keys.
• Use datalion__list_data_sources to inspect what is already loaded into a project before uploading or troubleshooting data.
• Prefer datalion__import_excel_data when the source is an .xlsx workbook or when you want Datalion's full import pipeline, including optional codebook generation during import.
• Use datalion__list_codebook when the user needs a question-level inventory; use datalion__download_codebook for the tree structure.
• For workbook imports, prefer an absolute localPath so the bridge can read the file directly.
• For uploads, confirm filename, header and delimiter assumptions, data source name if relevant, and whether existing rows should be truncated.
• For import_excel_data, confirm projectId, file path or base64 file content, filename if you are not using localPath, whether you want the default main data source (useDefaultDataSource=true) or a named data source, and whether replaceData, runCalculations, convertComma, skipLines, comment, and createCodebook should be enabled.
• For project settings edits, confirm the target projectId and the exact defsettings keys and values before calling.
• For chart-table reads, confirm projectId, chartId, and any filter string before calling.
• For codebook uploads, confirm projectId, CSV filename, import mode, and whether any explicit column mapping is needed. The current backend expects columnMapping as an array aligned to the CSV header order.
• For reports, prefer direct MCP coverage first.
• For dashboard and export tasks without direct MCP coverage, inspect the local Datalion repo and its OpenAPI or route definitions before choosing a fallback path.
• Keep tokens, auth headers, and exported files out of logs unless the user explicitly asks for them.