Skip to main content
Copilot has two extension surfaces, and they install Cekura differently. Pick the one you’re setting up:

​
Copilot CLI

1

Install the CLI and sign in

Run copilot once and complete the sign-in prompt. Requires a Copilot licence (Pro, Pro+, Business, or Enterprise).
2

Add the Cekura marketplace

browse should list one plugin, cekura. If it doesn’t, the marketplace isn’t registered — nothing below will work.
3

Install the plugin

In an interactive session, use /plugin marketplace add cekura-ai/cekura-skills then /plugin install cekura@cekura-skills.
4

Confirm Skills and MCP loaded

mcp list should show cekura with Source: Plugin and the installed plugin version — that’s the plugin’s MCP config being picked up, not a hand-written one.
5

Sign in to MCP

Nothing to configure. The first Cekura tool call opens a browser for OAuth; no API key is stored.
Copilot plugins carry no slash commands, and Copilot only discovers subagents named *.agent.md — so the plugin gives you Skills and MCP. The Skills cover the same workflows and activate by context.

​
Repository surfaces

The coding agent, code review, and the IDE extensions ignore CLI plugins. They read Skills from .github/skills/ in the repository they’re working in:
Commit the result and everyone working in that repo gets the Cekura playbook, including code review on pull requests.
These surfaces don’t support OAuth-authenticated remote MCP. For live Cekura tools, register https://api.cekura.ai/mcp in the repository’s Copilot MCP configuration with an X-CEKURA-API-KEY header — see API-key setup. Copilot CLI needs no key.

​
Verify setup

Start Copilot from your agent repo and ask:
Copilot should name real agents from your workspace and reason in Cekura terms — evaluators, metrics, test profiles, run results. Generic voice-testing advice means the Skills or MCP aren’t loaded.

​
Keep it updated

Copilot has no auto-update hook, so run this when you want the latest version; copilot plugin list shows what’s installed. When a release adds a brand-new Skill, re-add the marketplace first to refresh the snapshot, then update. For .github/skills/, re-run the npx skills add command above.

​
Troubleshooting

copilot plugin marketplace list should include cekura-skills, and copilot plugin marketplace browse cekura-skills should list cekura. Re-add with copilot plugin marketplace add cekura-ai/cekura-skills.
Confirm the plugin is installed (copilot plugin list), then ask something explicitly Cekura-shaped — Skills load by matching your request against their descriptions, so a generic prompt may not trigger one.
Check copilot mcp list shows cekura, then update the CLI (npm install -g @github/copilot) — plugin-provided MCP servers and their OAuth flow need a current release. Fallback: add the server yourself in ~/.copilot/mcp-config.json, or use API-key auth.
Those surfaces need the API-key credential, not OAuth — see the warning above.

​
No plugin?

Set up Skills + MCP manually, or use the behavior preset fallback.