メニュー
Bump the Kinetica plugin version across all 5 source files (2 SKILL.md frontmatter + 2 JSON configs + README.md version badge) and run build.sh to sync mirrored copies. Accepts patch (default), minor, or major.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Activate when the user is WRITING APPLICATION CODE that programmatically interacts with a Kinetica GPU database — Python or Node apps, microservices, ETL scripts, or streaming data pipelines that import the gpudb SDK, call the Kinetica REST API from app code, or wire up Kinetica connectors (Spark, Kafka, JDBC, Airflow, Flink). Trigger on requests like "write a Python script that ingests this CSV into Kinetica", "build a FastAPI endpoint backed by Kinetica", "set up a Kafka to Kinetica pipeline", "use the gpudb client to upsert records", or any request for source code the user will save, version, and run as part of an application. Do NOT use for ad-hoc SQL, one-off table inspection, schema exploration, admin commands, or map tile rendering — those go to kinetica-execute.
Activate for INTERACTIVE EXPLORATION, QUERYING, and ADMINISTRATION of an existing Kinetica GPU database via its CLI — running SQL queries, inspecting table schemas and row counts, browsing data, one-shot data import/export, graph analytics (shortest path, PageRank, TSP), geospatial filtering, WMS map tile rendering (heatmaps, contours, rasters, class-breaks, labels, isochrones from x/y or WKT data), EXPLAIN plans, system table queries, table monitoring, security configuration, and database administration. Trigger on requests like "what tables are in schema X?", "how many rows in foo?", "show me the schema of bar", "find records where lat is in this bbox", "render a heatmap of column Y", "EXPLAIN this query", or any request where the user wants an answer FROM the database rather than code that talks to it. Activate even for simple tasks like checking table counts or running a quick query. Do NOT use when the user is writing an application, SDK client, or production data pipeline in source code — those go to ki
Activate when the user is WRITING APPLICATION CODE that programmatically interacts with a Kinetica GPU database — Python or Node apps, microservices, ETL scripts, or streaming data pipelines that import the gpudb SDK, call the Kinetica REST API from app code, or wire up Kinetica connectors (Spark, Kafka, JDBC, Airflow, Flink). Trigger on requests like "write a Python script that ingests this CSV into Kinetica", "build a FastAPI endpoint backed by Kinetica", "set up a Kafka to Kinetica pipeline", "use the gpudb client to upsert records", or any request for source code the user will save, version, and run as part of an application. Do NOT use for ad-hoc SQL, one-off table inspection, schema exploration, admin commands, or map tile rendering — those go to kinetica-execute.
Activate for INTERACTIVE EXPLORATION, QUERYING, and ADMINISTRATION of an existing Kinetica GPU database via its CLI — running SQL queries, inspecting table schemas and row counts, browsing data, one-shot data import/export, graph analytics (shortest path, PageRank, TSP), geospatial filtering, WMS map tile rendering (heatmaps, contours, rasters, class-breaks, labels, isochrones from x/y or WKT data), EXPLAIN plans, system table queries, table monitoring, security configuration, and database administration. Trigger on requests like "what tables are in schema X?", "how many rows in foo?", "show me the schema of bar", "find records where lat is in this bbox", "render a heatmap of column Y", "EXPLAIN this query", or any request where the user wants an answer FROM the database rather than code that talks to it. Activate even for simple tasks like checking table counts or running a quick query. Do NOT use when the user is writing an application, SDK client, or production data pipeline in source code — those go to ki
| name | bump-version |
| description | Bump the Kinetica plugin version across all 5 source files (2 SKILL.md frontmatter + 2 JSON configs + README.md version badge) and run build.sh to sync mirrored copies. Accepts patch (default), minor, or major. |
| user-invocable | true |
| argument-hint | [patch|minor|major] |
You are a version-bump automation skill. When invoked, bump the Kinetica plugin version across all canonical source files, then run the build to propagate changes.
The user may pass patch, minor, or major as an argument. Default to patch
if no argument is given or the argument is empty.
Reject any argument that is not one of those three values.
Read plugins/kinetica/.claude-plugin/plugin.json and extract the top-level
"version" field. This is the canonical version string (e.g. "1.0.32").
Parse it into three integers: MAJOR.MINOR.PATCH.
Apply semver rules:
patch → increment PATCH, keep MAJOR and MINORminor → increment MINOR, reset PATCH to 0, keep MAJORmajor → increment MAJOR, reset MINOR and PATCH to 0Use the Edit tool (not Bash sed) to update each file. Match the OLD version string exactly and replace with the NEW version string.
2 SKILL.md files — edit the version: line inside the YAML frontmatter
metadata: block. The line looks like:
version: "OLD_VERSION"
Replace with:
version: "NEW_VERSION"
Files:
skills/kinetica-code/SKILL.mdskills/kinetica-execute/SKILL.mdmarketplace.json — edit ONLY the plugins[0].version field:
"version": "OLD_VERSION",
Replace with:
"version": "NEW_VERSION",
CRITICAL: Do NOT touch "metadata": { "version": "1.0.0" } — that is the
marketplace schema version and must stay at 1.0.0.
plugin.json — edit the top-level version field:
"version": "OLD_VERSION",
Replace with:
"version": "NEW_VERSION",
File: plugins/kinetica/.claude-plugin/plugin.json
README.md — edit the shields.io version badge on line 2. The line looks like:
[](https://github.com/kineticadb/agent-skills)
Replace with:
[](https://github.com/kineticadb/agent-skills)
Match the full version-OLD_VERSION-blue token so you don't accidentally touch
other version numbers that may appear elsewhere in the README (e.g. changelog
entries or dependency mentions).
File: README.md
Execute ./build.sh from the repository root. This syncs the 2 source
SKILL.md files into mirrored copies under plugins/kinetica/skills/.
Note: README.md, plugin.json, and marketplace.json are not mirrored.
Print a summary:
OLD_VERSION → NEW_VERSION/commit or
git commit when ready."Do NOT create a git commit.