Use AG Grid MCP-style docs search, version detection, examples, definitions, and upgrade guidance through a lightweight local CLI wrapper. Use when working on AG Grid integration or migration tasks.
Use this skill when you need AG Grid documentation, examples, API references, version detection, or migration guidance, but you want a local CLI workflow instead of the AG Grid MCP server.
This CLI is modeled after the official AG Grid MCP server documentation:
search_docsdetect_versionset_versionlist_versionsquick-startupgrade-gridarticles, definitions, and examplesReference:
The AG Grid MCP server gives LLMs framework-specific and version-specific AG Grid context. ag-grid-cli exposes the same practical capabilities as terminal commands so an agent can fetch the same class of information directly.
This skill is designed for zero-build consumption after install.
npm installPrimary invocation:
node <skill-dir>/bundle/ag-grid-cli.cjs <command> [args...]
This is the default command agents should use after the skill is installed.
Do not assume ag-grid-cli is on PATH.
If the agent knows the installed skill path, run the sibling bundle directly.
Optional shortcut when available:
ag-grid-cli <command> [args...]
Portable fallback on any OS:
node <skill-dir>/bundle/ag-grid-cli.cjs <command> [args...]
Platform wrappers:
<skill-dir>/ag-grid-cli.sh<skill-dir>\\ag-grid-cli.cmd<skill-dir>\\ag-grid-cli.ps1Launcher behavior:
ag-grid-cli on PATH is only an optional conveniencenpm install at runtimeThis keeps usage simple for agents embedded in another project: the user can add this skill folder, and the agent can run the committed bundle immediately.
Naming:
ag-grid-cli./ag-grid-cli.shag-grid-cli.cmdag-grid-cli.ps1node bundle/ag-grid-cli.cjsAfter skill install, prefer the sibling bundle in the installed skill directory:
node <skill-dir>/bundle/ag-grid-cli.cjs ...Only use ag-grid-cli ... if you already know the binary is available on PATH.
If a prerequisite is missing, say it explicitly before continuing:
Node.js is required to run ag-grid-cli.Do not silently try to compile or install dependencies inside the installed skill directory.
Do not run npm install from the skill folder as a bootstrap step.
Official MCP concept -> CLI equivalent
detect_version -> ag-grid-cli detect-versionset_version -> ag-grid-cli set-version --version <semver> --framework <framework>list_versions -> ag-grid-cli list-versionssearch_docs -> ag-grid-cli search-docs "<query>"articles resource -> ag-grid-cli articles list|getdefinitions resource -> ag-grid-cli definitions list|getexamples resource -> ag-grid-cli examples list|getquick-start prompt -> ag-grid-cli quick-startupgrade-grid prompt -> ag-grid-cli upgrade-grid --to <semver>When working in an AG Grid repo, do this first:
node <skill-dir>/bundle/ag-grid-cli.cjs detect-versionnode <skill-dir>/bundle/ag-grid-cli.cjs set-version --version 35.1.0 --framework vuenode <skill-dir>/bundle/ag-grid-cli.cjs search-docs "cell renderer"node <skill-dir>/bundle/ag-grid-cli.cjs articles get <slug>node <skill-dir>/bundle/ag-grid-cli.cjs definitions get <apiName>node <skill-dir>/bundle/ag-grid-cli.cjs examples get <articleSlug> <exampleSlug>detect-version before search-docs.node <skill-dir>/bundle/ag-grid-cli.cjs ... as the default invocation.ag-grid-cli on PATH unless the environment already indicates it exists.latest, let the CLI normalize it.--json when you need machine-readable output for chaining or parsing.--plain when you need stable line-based output for shell pipelines.--framework and --version overrides in monorepos or mixed-framework repos.upgrade-grid and follow one major at a time.Use natural language queries, same style as the MCP docs:
node <skill-dir>/bundle/ag-grid-cli.cjs search-docs "column sorting"node <skill-dir>/bundle/ag-grid-cli.cjs search-docs "cell renderers" --framework vuenode <skill-dir>/bundle/ag-grid-cli.cjs search-docs "server side row model filtering" --version 34.3.0node <skill-dir>/bundle/ag-grid-cli.cjs search-docs "data grid performance" --framework react --limit 3When search results surface an API name or article slug, follow up with:
node <skill-dir>/bundle/ag-grid-cli.cjs definitions get <name>node <skill-dir>/bundle/ag-grid-cli.cjs articles get <slug>List articles:
node <skill-dir>/bundle/ag-grid-cli.cjs articles list --framework vue
Read one article:
node <skill-dir>/bundle/ag-grid-cli.cjs articles get component-cell-renderer --framework vue
List API definitions:
node <skill-dir>/bundle/ag-grid-cli.cjs definitions list --version 35.1.0
Read one definition:
node <skill-dir>/bundle/ag-grid-cli.cjs definitions get cellRenderer
List examples:
node <skill-dir>/bundle/ag-grid-cli.cjs examples list --framework vue --language typescript
Read one example:
node <skill-dir>/bundle/ag-grid-cli.cjs examples get row-ids row-data --framework vue --language typescript
Quick start plan:
node <skill-dir>/bundle/ag-grid-cli.cjs quick-start --framework vue --typescript --feature pagination --feature row-grouping
Upgrade plan:
node <skill-dir>/bundle/ag-grid-cli.cjs upgrade-grid --to 35.1.0
Explicit upgrade path:
node <skill-dir>/bundle/ag-grid-cli.cjs upgrade-grid --from 33.2.0 --to 35.1.0 --framework react
--json: structured stdout.--plain: stable tab-separated or raw content output.Implement a feature:
node <skill-dir>/bundle/ag-grid-cli.cjs detect-versionnode <skill-dir>/bundle/ag-grid-cli.cjs search-docs "set filter tree list" --framework vuenode <skill-dir>/bundle/ag-grid-cli.cjs definitions get ISetFilterParamsnode <skill-dir>/bundle/ag-grid-cli.cjs examples list --framework vue --language typescriptPlan an upgrade:
node <skill-dir>/bundle/ag-grid-cli.cjs detect-versionnode <skill-dir>/bundle/ag-grid-cli.cjs list-versionsnode <skill-dir>/bundle/ag-grid-cli.cjs upgrade-grid --to 35.1.0node <skill-dir>/bundle/ag-grid-cli.cjs articles get upgrading-to-ag-grid-34node <skill-dir>/bundle/ag-grid-cli.cjs articles get upgrading-to-ag-grid-35