create-kandev-plugin

Create, test, package, and publish Kandev runtime plugins from the official template.

733|110|Updated Jan 9, 2026
One-click install
npx skills add https://github.com/kdlbs/kandev --skill create-kandev-plugin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-kandev-plugin
Source: https://github.com/kdlbs/kandev/tree/main/.agents/skills/create-kandev-plugin
Command: npx skills add https://github.com/kdlbs/kandev --skill create-kandev-plugin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Building a Kandev runtime plugin requires coordinating a dedicated repository, a manifest, a Go pluginsdk executable, optional UI bundles, and marketplace publishing rules, and mistakes in any step produce broken or unpublishable artifacts.

Core Features & Use Cases

  • Repository Resolution and Setup: Locates the owning plugin repository for bug fixes or bootstraps a new one from the kdlbs/kandev-plugin-template with synchronized manifest id, Go module, and release naming.
  • Contract-Grounded Implementation: Enforces the authoritative hook, Host API, capability, and manifest contracts from the public authoring docs, pluginsdk, and gRPC proto before writing code.
  • Artifact Verification and Publishing: Packages the tarball, smoke tests it on a disposable Kandev instance across lifecycle, events, webhooks, and UI, then guides release tagging and marketplace catalog submission.
  • Use Case: A developer asked to fix a bug in an existing Kandev plugin uses this Skill to resolve the correct plugin repository, reproduce and fix the issue there, rebuild the package, and verify the artifact on a disposable instance before release.

Quick Start

Create a new Kandev plugin called kandev-plugin-slack that reacts to task events and package it for a dev instance.

Frequently Asked Questions about create-kandev-plugin

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

FAQPage Schema
How do I create a new Kandev plugin?

Create a repository from the kdlbs/kandev-plugin-template, derive a lowercase plugin id, and keep the manifest id, Go module, binary name, and release asset name synchronized. Implement behavior with the Go pluginsdk, then package and smoke test on a disposable Kandev instance.

How do I fix a bug in an existing Kandev plugin?

Resolve the owning plugin repository by matching the manifest id and repo_url against the catalog or installed metadata, never assuming the Kandev monorepo owns the bug. Reproduce and fix the issue in that repository, then rebuild and verify the packaged artifact.

Can Kandev plugins live inside the kdlbs/kandev monorepo?

No, production plugins must live in their own dedicated repository, such as kdlbs/kandev-plugin-<slug> for official plugins. The in-tree plugin fixture in the monorepo is test support only, not a starter location.

How are Kandev plugin webhooks authenticated?

API v2 webhook routes require a real Kandev caller identity by default, and undeclared keys are rejected. Only mark a webhook public for genuine third-party ingress, and validate the method and provider signature inside your own handler before side effects.

Why does reinstalling a Kandev plugin fail?

Kandev rejects reinstalling the same plugin id and version. Bump the manifest version or uninstall the existing version before reinstalling the package.

When should I not use this plugin skill?

Do not use it for agent skills, MCP servers, general integrations, or Kandev host, SDK, loader, and registry changes that do not also change a plugin. Those belong to separate workflows in the Kandev repository.