Create, modify, debug, test, package, or publish a Kandev runtime plugin in its dedicated repository. Use only when the requested work targets a Kandev plugin implementation or its release and marketplace lifecycle, including fixing a bug in an existing plugin.
SkillScore77Maintained
Automatic
◆Coding pack
Last verified 9/20/2026
What it changes
Passed 15 of 19 test cases with the skill, and 3 of 19 without it.
Without skill18%
With skill77%
Checks it passed that the model alone missed
Call Host.EmitEvent to publish the notification.
Prefix the emitted event name as plugin.<id>.<name>.
Add the repository pointer to plugin-registry/plugins.yaml.
and 13 more in the full report
13 fixed4 passed either way5 still failing0 broke
Pass-rate lift
+59 pp
Tokens
+108%
Agent turns
0%
Response time
-50%
Model gemini-3.6-flashMeasured 9/20/2026v5 · latest is v617 of 22 cases passed with skill · 19 comparable
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
A newer attempt on gemini-3.6-flash on 10/2/2026 did not produce a publishable comparison (not comparable). The snapshot above is the previously measured run.
See it in action
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 13
Prompt
When bootstrapping a new plugin repository from kdlbs/kandev-plugin-template, what relative directory path does go.mod default to for resolving the local pluginsdk dependency before standalone publishing?
What was checked, without and with the skill
Checked
Without skill
With skill
Specify that the default replace path points to ../kandev/apps/backend.
Missed
Passed
case-18 · gemini-3.6-flash · 9/20/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md326 linessingle file
Create Kandev Plugin
Build Kandev runtime plugins from the official template and current public
contracts. Keep plugin source outside the Kandev monorepo and prove the packaged
artifact against a disposable development instance before publishing it.
Start with the canonical plugin authoring guide.
Use this skill for the repository workflow after choosing a recipe there:
choose recipe → edit manifest → implement → validate → package → smoke test.
The guide owns the complete hook/Host matrix; this skill keeps the repository
and verification procedure concise.
Establish The Boundary
Invoke this skill only when the user intends to create, change, fix, test,
package, release, or submit a Kandev runtime plugin. A passing mention of
plugins, a generic extension request, or the presence of plugin host code in
the Kandev monorepo is not sufficient.
Confirm the artifact: a Kandev runtime plugin ships a manifest.yaml, a
platform executable built with the Go pluginsdk, and optionally a native
UI bundle. Agent instruction packages, MCP servers, and other products that
also use the word "plugin" are outside this skill.
Classify the work as a new plugin, an existing plugin change, a Kandev host
or SDK dependency required by the plugin, or a marketplace-only change.
Keep each production plugin in one dedicated repository. For an official
plugin, use a public kdlbs/kandev-plugin-<slug> repository. For a community
plugin, use the author's public repository. Do not add a production plugin
implementation to kdlbs/kandev; the in-tree plugin fixture is test support,
not a starter location.
Keep host API, SDK, registry runtime, and plugin-loader changes in the Kandev
repository. If the plugin needs a missing host capability, treat that as a
separate Kandev change with its own tests and compatibility review.
Resolve The Owning Repository
Resolve the plugin repository before editing, especially for bug reports:
Start with repository information in the request, issue, pull request, or
current task. Otherwise match the manifest id and repo_url against the
official catalog entry or the installed plugin metadata. Do not infer that a