checkmk-plugin

Package Checkmk plugins into MKP packages from local repositories.

12|Updated Aug 6, 2025
One-click install
npx skills add https://github.com/oposs/mkp-builder --skill checkmk-plugin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: checkmk-plugin
Source: https://github.com/oposs/mkp-builder/tree/main/skills/checkmk-plugin
Command: npx skills add https://github.com/oposs/mkp-builder --skill checkmk-plugin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers build, upgrade, and package Checkmk plugins (MKP format) for Checkmk 2.3.x, covering agent-based plugins, SNMP, bakery/automation, and metric translation workflows.

Core Features & Use Cases

  • Ensure correct entry-point prefixes (agent_section_, check_plugin_, etc.) for automatic discovery.
  • Provide end-to-end MKP packaging workflows from local repositories, including CI hooks and configuration validation.
  • Support translation-aware renaming to preserve historical data when upgrading plugins.

Quick Start

Run the MKP Builder on your repository to produce a packaged MKP for the Checkmk plugin.

Frequently Asked Questions about checkmk-plugin

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I package Checkmk plugins into MKP files from a local repository?

To package Checkmk plugins into MKP files, you run the mkp-builder on your local repository structure to enforce frontmatter validation, correct directory layout, and output the final MKP artifact.

What's the best way to handle translation-aware renaming when upgrading Checkmk plugins?

For translation-aware renaming when upgrading Checkmk plugins, you should preserve historical data by ensuring correct entry-point prefixes and utilizing the translation workflows provided during the MKP packaging process.

Does Checkmk 2.3 support packaging agent-based, SNMP, and bakery plugins together?

Yes, Checkmk 2.3 supports packaging agent-based, SNMP, and bakery deployment plugins together, validating required fields and correct entry-point prefixes like check_plugin_ for automatic discovery within a single MKP package.

How do I validate frontmatter and directory layout for Checkmk MKP packaging?

You validate frontmatter and directory layout for Checkmk MKP packaging by using the mkp-builder, which enforces required fields, correct structure, and entry-point prefixes before producing the final MKP artifact.

Why does my Checkmk plugin fail automatic discovery after MKP packaging?

Your Checkmk plugin might fail automatic discovery if the MKP packaging did not enforce correct entry-point prefixes, such as agent_section_ or check_plugin_, which are required for Checkmk to detect the plugin properly.