By kernoio
Give Claude the local validation and CI feedback loop it needs to verify and fix its work in context, and ship code that works as part of your system.
Install Kerno CLI, start the agent on this workspace, register MCP, and connect your editor
Verify Kerno MCP connectivity (healthcheck, get_applications, optional endpoint listing)
Set up the environment (compose plan approval gate, then start_environment; handles needs_user_feedback)
Show Kerno MCP setup pointers, job semantics, and reference links
Author or refresh Kerno HTTP scenario tests via kerno_plan_baseline and kerno_implement_baseline (async jobs + scopes)
Installs and connects Kerno for a project — CLI, login, local agent bound to the workspace, host MCP registration, verification, and next-step handoff. Use when the user runs /install-kerno, says "set up Kerno", "install Kerno", "configure Kerno MCP", "connect Kerno", or first-time Kerno onboarding.
This skill should be used when the user asks about Kerno async jobs, kerno_job wait semantics, kerno_cancel, or debugging long-running MCP work. Explains launch plus kerno_job, client-side per-tool-call limits, and sparse polling to avoid token spam.
This skill should be used when the user asks to bootstrap Kerno MCP, verify connectivity, or runs /kerno-bootstrap. Guides healthcheck, get_applications, and optional endpoint discovery. For environment bring-up use kerno-environment-setup.
This skill should be used when the user asks to set up the environment, start the stack, bring up services, bootstrap the env, or run /kerno-env. Enforces the compose-plan user approval gate and handles needs_user_feedback as a hard stop before calling kerno_start_environment.
This skill should be used when the user wants to author or refresh Kerno HTTP scenario tests via MCP (kerno_plan_baseline and kerno_implement_baseline), or asks about scopes, plan_review_instructions, workspace_id, or async completion. Planning does not require a running stack; implement requires ready_for_validation.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Markdown-only plugin: slash commands, skills, and rules that guide use of the Kerno MCP tools. The agent runtime is not included here — install and start it with @kerno/cli.
Source: github.com/kernoio/kerno-mcp-plugin
From your project root (or use -g for a user-wide install), install the plugin skills into the agents the CLI detects (Cursor, Claude Code, Codex, and others):
npx skills add kernoio/kerno-mcp-plugin
Then run /install-kerno (or @install-kerno in Codex) in that workspace to install @kerno/cli, start the agent with kerno mcp -w, and register MCP.
To refresh after upstream changes:
npx skills update kernoio/kerno-mcp-plugin
Useful flags: -g / --global, -a cursor (or claude-code, codex, …), -y to skip prompts. See vercel-labs/skills.
Marketplace install is not available yet — use the GitHub repo directly (npx skills add or clone). This path installs skills (procedures). Slash commands, Cursor rules, and full plugin manifests still use the per-client install steps below if you need them.
Paste one prompt below into your assistant (Agent chat, Claude Code, Codex, etc.). It installs skills from the GitHub repo, then runs install-kerno to install the CLI, start the agent, and connect MCP for your workspace. Do not use plugin marketplaces.
| Tool | Copy-paste prompt |
|---|---|
| Claude Code | prompts/install-claude.md |
| Cursor | prompts/install-cursor.md |
| Codex | prompts/install-codex.md |
Install and set up Kerno MCP for this workspace using https://github.com/kernoio/kerno-mcp-plugin.
Do not use any plugin marketplace — Kerno is not published to marketplaces yet.
1. Run `npx skills add kernoio/kerno-mcp-plugin -y` from the project root to install Kerno skills on this machine.
For slash commands too: clone the repo to ~/.kerno/mcp-plugin and restart Claude with `claude --plugin-dir ~/.kerno/mcp-plugin` (see claude/README.md). Do not use `/plugin marketplace`.
2. Run the install-kerno skill (/install-kerno) to install @kerno/cli, log in, start the agent with kerno mcp -w on this project, and register MCP.
3. Verify kerno_get_applications works for this workspace path.
Work in this repository root unless I specify another path.
Open in Cursor: use the link under the prompt block, or copy the text below.
Install and set up Kerno MCP for this project using https://github.com/kernoio/kerno-mcp-plugin.
Do not use any plugin marketplace — Kerno is not published to marketplaces yet.
1. Run `npx skills add kernoio/kerno-mcp-plugin -y` from the project root to install Kerno skills.
For slash commands, rules, and full plugin: clone to ~/.kerno/mcp-plugin and symlink into ~/.cursor/plugins/local/kerno, then reload Cursor (see cursor/README.md).
2. Run /install-kerno to install @kerno/cli, bind the agent to this workspace with kerno mcp -w, and register MCP with the URL from CLI output.
3. Confirm Kerno MCP tools are available in this project folder.
Work in this repository root unless I specify another path.
npx claudepluginhub kernoio/kerno-mcp-plugin --plugin kernoBeta MCP skills from Docker
Centralized Claude Code configuration: Docker-first guards, permissions, MCP gateway, and workflow skills
No description provided.
Model Context Protocol Mcp Expert subagent
Agent configuration utilities - project assimilation, config auditing, teammate definitions, MCP management, and hooks configuration
Manage MCP servers - discover, analyze, execute tools/prompts/resources. Use for MCP integrations, capability discovery, tool filtering, programmatic execution, or encountering context bloat, server configuration, tool execution errors.