datagrok-entities
Call datagrok_show_entities after any MCP tool result that returns entity data (files, scripts, queries, connections, projects, spaces, groups, users). Always use the tool — never list entities as pla
SKILL.mdpackages/Grokky/dockerfiles/claude-runtime/plugin/skills/datagrok-entities/SKILL.md
GitHubdatagrok-entities
When an MCP tool result contains entity data, call datagrok_show_entities immediately.
The tool renders interactive cards the user can click to open the entity — always prefer
it over prose.
Tool signature
datagrok_show_entities(entities: EntityRef[])
Supported types
| type | required | optional |
|---|---|---|
file |
connector, path, name |
isDirectory |
script |
id, name |
— |
query |
id, name |
— |
connection |
id, name |
— |
project |
id, name |
— |
space |
id, name |
— |
group |
id, name |
— |
user |
id, name |
— |
Notes
#typepassthrough: MCP results return entities with a#typefield in PascalCase (e.g."FileInfo","DataQuery","UserGroup"). Pass it as-is in the#typefield — the tool normalizes it to the correcttypevalue automatically. You may also pass the normalizedtypestring directly if you already know it.- Pass
idand all other identifying values exactly from the MCP response — never invent. - For files,
connectoris the connection name string (e.g."System:DemoFiles") andpathis the file path relative to the connector root. - For users, use
friendlyNameas thenamefield — users have nonameproperty in the MCP response, onlyfriendlyNameandlogin. - A single call may mix entity types — the renderer handles them.
- After calling the tool, you may add a short prose summary if useful, but the tool call must come first.