RepoAI
Browse MCPs

Opensearch

94TrustedInstructions only

Distributed search and analytics setup for KubeSphere environments.

What it does

Opensearch transforms how your assistant handles observability within KubeSphere by providing a structured framework for managing the deployment and configuration of data storage nodes. It assists in setting up the environment for tracking logs, auditing activities, and system events, ensuring the assistant can verify cluster status and apply correct installation parameters.

This skill is designed for administrators who need to manage telemetry storage clusters. It focuses on the technical requirements for deploying the search engine, including identifying valid target clusters, verifying version compatibility, and tailoring component configurations such as master and data nodes.

When it earns its place

Reach for it when…

Apply this skill when preparing to deploy the telemetry storage engine on KubeSphere to ensure persistent logging, auditing, and event monitoring capabilities are correctly provisioned.

Look elsewhere when…

Do not use this for general log analysis or querying data directly from existing indices, as it covers only the deployment and configuration phase of the underlying infrastructure.

What to say to use it

You never invoke a skill directly — the assistant picks it up when your request matches what it covers. These are the kinds of things that do that.

  • install the opensearch extension on my host cluster
  • how do I set up opensearch for logging in kubesphere
  • help me enable the opensearch dashboard in my current cluster
  • check the version and status of my opensearch installation

Install it

Install for all your projects

Copy the skill directory into your personal skills folder. Claude picks it up on its own the next time your request matches what it does — there is nothing to enable.

bash
git clone --depth 1 --branch master https://github.com/kubesphere/kubesphere.git /tmp/kubesphere
mkdir -p ~/.claude/skills
cp -r /tmp/kubesphere/skills/opensearch ~/.claude/skills/opensearch

Install for one project only

Put it in the project's own skills folder instead, so it can be committed and shared with everyone working on that repository.

bash
cp -r /tmp/kubesphere/skills/opensearch .claude/skills/opensearch

If a skill of the same name exists in both places, the personal one wins.

Installing on Claude.ai or through the API instead? The full guide covers every surface.

Pair it with an MCP server

Opensearch changes how the work is done. These servers change what Claude can reach while doing it.

How skills and MCP servers differ →