القائمة
Save, create, attach to, or share a Datagrok project. Each step has a trigger phrase; run only the triggered step, then stop.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use whenever you need the Datagrok browser to actually execute JavaScript — adding viewers, filtering, modifying the view, or returning a result widget to the chat. Open this skill before calling the datagrok_exec tool.
Filter rows of a Datagrok DataFrame inside a datagrok-exec block through the Filters panel — by range, equals/contains/in-set, multi-value, boolean, free-text row expressions, or substructure (SMILES / SMARTS / molblock). Also covers clearing, inverting, the show-only-filtered vs destructive-drop split, and the filter event lifecycle (onRowsFiltering / onFilterChanged / onRowsFiltered). Use whenever the user says "filter", "show only", "hide rows where", "narrow to subset", "find rows that", "contains", "substructure search", "categorical filter", "range filter", "invert", "clear the filter", "clear filters", "drop rows", or asks for the filtered subset as a new table. Does NOT cover selection (separate skill) or generic DataFrame cloning (datagrok-df-and-columns).
Add a calculated, formula-based column to a dataframe inside a datagrok-exec block. Use whenever the user asks to compute, derive, add, or create a new column from existing columns — LipE, ratios, log/round, heavy atom count, any expression in the Datagrok formula DSL. Replaces hand-written addNewFloat/addNewInt + for-loop with a single formula-attached column that recomputes when source columns change.
Find, describe, add, remove, rename, clone, or set metadata on columns of a Datagrok DataFrame inside a datagrok-exec block. Use whenever the user asks to locate "the X column", summarize a column, add a typed/empty/values-filled/virtual column, set semantic type / units / format / friendly name, apply linear or categorical or conditional color coding, drop or rename columns, or copy a DataFrame. Covers everything in DataFrame.columns and Column.meta — but not row filtering/selection (datagrok-filtering, datagrok-selection) and not formula-only columns (datagrok-calc-column).
Sort, hide, show, reorder, resize, pin, format, and color-code columns in a Datagrok TableView grid from a datagrok-exec block. Use whenever the user asks to sort by a column (any direction), multi-sort, hide / show / reorder / pin / resize columns, freeze the first N columns, change number-format display, color-code cells (defaults and grid-only tint here; full per-type reference in datagrok-df-and-columns), set row height, or reset the grid back to defaults. Distinct from datagrok-df-and-columns (which owns column-level data metadata like semType, units, friendlyName, and is also where canonical color-coding lives) and from datagrok-viewers (which owns scatter plot / histogram / etc.). Does NOT cover filtering (`datagrok-filtering`), selection (`datagrok-selection`), custom cell renderer authoring (`create-cell-renderer`), saving / restoring layouts, or grid event handlers.
Add a viewer, configure a viewer, change viewer options, find viewer, close viewer, view a scatter plot, bar chart, histogram, line chart, box plot, pie chart, heat map, correlation plot, 3D scatter, trellis, density plot, statistics, on a Datagrok TableView inside a datagrok-exec block. Use whenever the user asks to plot, chart, visualize, show a graph, draw a distribution, color by a column, swap a viewer's axis, toggle a legend / regression line / log scale, replace one viewer with another, close every chart, reset the view to just the grid, or find an existing viewer by type. Plugin viewers like "Chem space", "sequence space", "activity cliffs" are NOT viewer types — they're registered functions — route those to `grok.functions.call`. Does NOT cover filtering (separate skill `datagrok-filtering`), selection (`datagrok-selection`), grid cell rendering (`datagrok-grid-customization`), layout save/restore, or custom-viewer authoring.
| name | datagrok-projects |
| description | Save, create, attach to, or share a Datagrok project. Each step has a trigger phrase; run only the triggered step, then stop. |
Run only the triggered step. Never chain ahead or infer the next step.
| Trigger | Run |
|---|---|
| "save the/my project / save my work" (no "new") | Step 1 |
| explicit "create / make / new project" | Step 2 |
| "attach the (current) table / view" | Step 3 |
| "share the project / with " | Step 4 |
Step 1 returned onServer: false | Step 2 + Step 3 |
"Save" never means create — a new project on a "save" request is a clone; the original stays unsaved.
Allowed chains only: Step 1 → Step 2 + Step 3 on onServer: false; Step 2 → Step 3 when the
same message says "with the current table/view/dataframe". Otherwise stop after the step.
datagrok_exec:
// Save the LIVE workspace project — a fresh DG.Project.create() would be a clone
// (public repo: UsageAnalysis TestTrack/Charts/radar-save-reopen-bug-spec.ts)
const project = grok.shell.project;
if (!project.isOnServer)
return {onServer: false};
// Persistence sequence per Bio/src/tests/projects-tests.ts saveAndOpenProject()
const tableInfo = t.getTableInfo();
const viewInfo = view.getInfo();
await grok.dapi.tables.uploadDataFrame(t);
await grok.dapi.tables.save(tableInfo);
await grok.dapi.views.save(viewInfo);
await grok.dapi.projects.save(project);
return {projectId: project.id, name: project.friendlyName, updated: true};
DG.Project.create() or create_project here; no addChild — the entities already belong to the project.Result:
updated: true → show the project with datagrok_show_entities, confirm saved. Stop.onServer: false → workspace is the local scratchpad; nothing to update. Ask for a project
name if the user gave none, then run Step 2 (create) + Step 3 (attach).create_project(name) once → keep returned id as projectId. Stop (unless chaining per Routing).
Requires projectId. datagrok_exec (substitute projectId):
const project = await grok.dapi.projects.find('<projectId>');
const tableInfo = t.getTableInfo();
await grok.dapi.tables.uploadDataFrame(t);
await grok.dapi.tables.save(tableInfo);
const viewInfo = view.getInfo();
await grok.dapi.views.save(viewInfo);
project.addChild(tableInfo);
project.addChild(viewInfo);
await grok.dapi.projects.save(project);
return {projectId: project.id, ok: true};
share_project(projectId, groups, access) — access "View"|"Edit", default "View". No group named → ask.
create_project on "save" while a server project is open — update in place (Step 1).view.saveLayout() / grok.dapi.layouts.save() — reopens as bare grid.datagrok_exec — use MCP tools.create_project twice.datagrok_exec fallback.