Agent Skills

AdapTable publishes four Skills: setup, develop, upgrade and debug.

You install them once in the project, then give your agent a command.

The agent opens the Skill that fits and follows it.

Update, remove and share

• npx skills update refreshes the installed Skills; npx skills check says whether an update exists
• The four Skills are published together
• npx skills remove adaptable-setup adaptable-dev adaptable-debug adaptable-upgrade removes them
• Commit the Skills folder and skills-lock.json so the whole team, and CI, gets the same Skills

What you can ask

How a Skill runs

Every Skill follows the same five steps, written once in the files under references/_shared/ that each Skill carries:

1. Find what is installed. adaptable detect reads the AdapTable major and exact version, the AG Grid version, the framework and wrapper package, and every project in a monorepo. Everything after targets what it found — never the newest version the agent remembers
2. Read the docs, don't recall. For the feature at hand the agent looks it up for that version: the feature index (docs list, docs search), the handbook page (docs get), the exact State or Options shape (docs get technical-reference-…), a working demo (docs demo), and the AdapTableQL functions the engine accepts (aql functions). It checks whether AdapTable already has a feature before hand-rolling one
3. Write the code, where it belongs
4. Check and fix. Every Expression goes through check expression for its Module, every Initial State through check state against your columnDefs, any wiring change through check setup. It applies the fix each finding gives and checks again — up to three rounds — then reports what is left word for word, never a false "clean"
5. Ask only at decision points. The Skill tells you what it found and carries on, and asks — then waits — only where a choice is expensive to reverse: licence keys, a ColDef migration, saved State, a package upgrade. Each phase writes its file before the next one starts, so a long task can be resumed from disk

Three guards hold in every Skill:

Inside a Skill

Each Skill is plain markdown you can open and audit.

The same files are published unpacked at https://www.adaptabletools.com/.well-known/skills/.

Published descriptions

What each Skill tells the agent about when it applies — the exact text the agent matches your request against:

adaptable-debug

Use when a running AdapTable grid misbehaves or the user asks what the grid is doing right now: a Layout, Column Filter, Grid Filter, Format Column, Styled Column, Calculated Column or Alert not applied; wrong columns or rows; State not persisting, loading or migrating; AdapTable console errors; or to extract Adaptable State, columns, logs or Grid Info from a page — and, when a problem cannot be resolved, to assemble an anonymised support case or feedback package. Works through window.__ADAPTABLE_DEVTOOLS__ with whatever browser tool is available. Not for compile/type errors or new features (adaptable-dev).

adaptable-dev

Use BEFORE writing or changing any code that imports from @adaptabletools/* — Adaptable Options, Initial State, Layouts, Format or Styled Columns, Alerts, Calculated Columns, Column Filters, Exports, AdapTableQL expressions, Adaptable API calls, custom toolbars, menus, tool panels or settings panels, and the columnDefs, gridOptions and AG Grid modules of a grid AdapTable runs on — and when planning such work. Grounds the code in the installed AdapTable version's docs and demos and validates State, expressions and setup before presenting them. Not for first-time integration (adaptable-setup), a misbehaving running grid (adaptable-debug) or version upgrades (adaptable-upgrade).

adaptable-setup

Use when adding AdapTable to a project for the first time: creating a new AdapTable + AG Grid app from nothing, from a dataset (CSV, Excel, JSON, a REST endpoint) or from a description, or wiring AdapTable onto an existing AG Grid Enterprise grid (including moving ColDef-level layout and styling into AdapTable Initial State). Covers packages, AG Grid modules, licence keys, containers, Adaptable Options, Initial State and a first verified run. Not for upgrades (adaptable-upgrade) or for adding features to an existing AdapTable instance (adaptable-dev).

adaptable-upgrade

Use when moving @adaptabletools/* packages to a newer major (from 21 or later, to 22, 23 or 24 — one step or several), including the coupled AG Grid upgrade, Adaptable State migration, and Adaptable Options, API, object-type, CSS and AdapTableQL changes. Plans first, writing ADAPTABLE_UPGRADE_*.md files; applies the plan in a separate session. Not for persisted-State problems in an otherwise current app (adaptable-debug).