idmp-plugin — Claude Code plugin: TDengine IDMP skills
A Claude plugin bundling TDengine IDMP skills for connection checks, schema inspection and careful operational work through idmp-cli.
/plugin install idmp-plugin@claude-plugins-official
/plugin marketplace add anthropics/claude-plugins-officialWhat idmp-plugin does
The plugin ships a set of TDengine IDMP skills: discovering what is available, inspecting schema, and running workflows where mistakes cost time. The agent calls them by name, for instance idmp-plugin:idmp-shared and idmp-plugin:idmp-element.
Nothing connects to your IDMP server on its own. You need idmp-cli first: npm install -g @tdengine/idmp-cli, then a profile and a login — idmp-cli config init --profile default --server http://your-idmp:6042 --username [email protected] --password-stdin, or the API key variant with --api-key-stdin. Node.js 16+, npm/npx and network access to your IDMP environment are the baseline. Credentials are either a username and password or a key issued in advance.
Running more than one environment? Keep separate profiles: idmp-cli config init --profile staging --server http://staging-idmp:6042 --username [email protected], then idmp-cli profile use staging. If the profile is already saved and the session expired, idmp-cli auth login is enough. Installing the plugin does not install idmp-cli or log you in — those stay your steps.
What it helps with
- verify the IDMP connection before touching data
- list the root elements available to you
- read the schema before writing queries
- run an IDMP operation without breaking the environment
- switch between production and staging profiles
Example prompts for the agent
- Use
idmp-plugin:idmp-sharedto check my IDMP connection and list the root elements - Inspect the element schema with
idmp-plugin:idmp-element - Set up a
stagingprofile and switch to it
How to install idmp-plugin
Plugin marketplace
/plugin install idmp-plugin@claude-plugins-official/plugin marketplace add anthropics/claude-plugins-officialStep by step, with commands for each platform: Claude Code plugins: marketplaces, installing, and building your own
Questions about idmp-plugin
How do I install idmp-plugin in Claude Code?
Add the marketplace first: /plugin marketplace add anthropics/claude-plugins-official. Then install the plugin: /plugin install idmp-plugin@claude-plugins-official.
What does idmp-plugin do?
It adds TDengine IDMP skills to Claude: connection checks, schema inspection and operational workflows that stay on the safe side.
What do I need before installing?
idmp-cli with Node.js 16+ and npm/npx, network access to your IDMP environment, and either a username/password or an API key. The plugin installs neither idmp-cli nor a login session.
Source text
idmp-plugin · MIT
# TAOS Data Agent Skills Marketplace Reusable **TDengine IDMP** skills for AI agents. Use this repository together with `idmp-cli`. ## Prerequisites Before installing these skills, make sure you have: - Node.js **16+** - `npm` / `npx` - network access to your TDengine IDMP environment - either a username/password or a pre-issued API key ## Step 1: Install `idmp-cli` ```bash npm install -g @tdengine/idmp-cli idmp-cli --version ``` ## Step 2: Configure the IDMP server and log in Create the default profile and persist a session in one command: ```bash printf '%s\n' "$IDMP_PASSWORD" | idmp-cli config init --profile default --server http://your-idmp:6042 --username [email protected] --password-stdin # or printf '%s\n' "$IDMP_API_KEY" | idmp-cli config init --profile default --server http://your-idmp:6042 --api-key-stdin idmp-cli config show idmp-cli auth check ``` ## Step 3: Add and switch another address when needed If you use multiple environments, save them as separate profiles: ```bash idmp-cli config init --profile staging --server http://staging-idmp:6042 --username [email protected] idmp-cli profile use staging idmp-cli config show ``` ## Step 4: Re-authenticate later when needed Use `auth login` when the saved profile already exists and you only need a new session: ```bash printf '%s\n' "$IDMP_PASSWORD" | idmp-cli auth login --username [email protected] --password-stdin printf '%s\n' "$IDMP_API_KEY" | idmp-cli auth login --api-key-stdin idmp-cli auth check ``` ## Step 5: Install the plugin for Claude Code First add the TAOS Data marketplace: ```bash claude plugin marketplace add taosdata/agent-skills ``` Then install `idmp-plugin`: ```bash claude plugin install idmp-plugin@taosdata ``` `idmp-plugin` already bundles the matching skills. If you are using Claude Code, you do not need to install or copy the packaged skills again. ## Step 6: Install the plugin for OpenAI Codex Use a Codex version that supports `codex plugin` (validated with Codex CLI 0.156.1). After the repository is published, add the GitHub marketplace: ```bash codex plugin marketplace add taosdata/agent-skills codex plugin add idmp-plugin@taosdata codex plugin list ``` When validating an unpushed local checkout, use `codex plugin marketplace add .` instead. Start a new Codex thread to load the packaged skills. For a read-only smoke test, ask: "Use idmp-plugin:idmp-shared and idmp-plugin:idmp-element to check my IDMP connection and list the available root elements." Codex must be able to run `idmp-cli` and access the configured IDMP server. Plugin installation does not install `idmp-cli` or log in to IDMP for you. Claude Code and Codex share the same packaged skills; no separate copy is needed. The plugin follows the [portable Agent Plugins format](https://developers.openai.com/plugins/build/plugins#plugin-structure): root `plugin.json` declares the schema and package identity, OpenAI presentation metadata lives under `extensions.com.openai.interface`, and skills are discovered from `skills/`. For OpenAI's Claude plugin submission portal, upload an archive of `plugins/idmp-plugin/`, not the repository root. The archive root must contain `.claude-plugin/plugin.json` and `skills/<skill-name>/SKILL.md`; the repository root is the marketplace source used by `codex plugin marketplace add taosdata/agent-skills`. Build the archives locally with `make codex` or `make claude`; both write the resulting ZIP files to `dist/`. ## Step 7: Reuse the packaged skills for other agents This repository does not publish a separate top-level standalone `skills/` bundle. If another agent supports filesystem-based skills, copy the packaged plugin skills directly: ```bash mkdir -p /path/to/other-agent/skills cp -R plugins/idmp-plugin/skills/* /path/to/other-agent/skills/ ``` If the target agent does not support a dedicated skills directory, import the relevant `SKILL.md` files and their sibling `references/` directories into that agent's reusable prompt or instruction system manually. ## Repository layout ```text . ├── .agents/plugins/ │ └── marketplace.json ├── .claude-plugin/ │ └── marketplace.json └── plugins/ └── idmp-plugin/ ├── .claude-plugin/ │ └── plugin.json ├── plugin.json └── skills/ ``` This repository is the source of truth for: - Claude Code marketplace metadata - Claude Code plugin metadata - Codex marketplace and plugin metadata - `plugins/idmp-plugin/skills/` as the packaged skills bundle shipped with the plugin
© TaosData · MIT · taosdata/agent-skills