Claude Code and GitHub Copilot

Your team’s Claude Code and GitHub Copilot get a harness engineered for your codebase: instructions with your conventions, skills for recurring work, a subagent for each domain, MCP servers to your systems and hooks that enforce your rules. Both tools read the same skills and agents, so every developer works the same way.

Plugins for the Whole Team

The harness is bundled into plugins, so every developer installs the same skills, agents, hooks and MCP servers. The plugins of this practice reach your team through a partner marketplace. Your partner key opens the plugin list and the downloads granted to your team, every plugin in the release that is running.

Skill Catalogue over MCP

Skills are served from one MCP server behind an Entra ID sign-in. Each group sees exactly the skills granted to that group. A skill runs in the conversation with a form for its required inputs and every step marked as it completes. One access view shows every grant beside the usage of each skill over 30 days.

Your Team's Harness

Claude Code and GitHub Copilot 3 steps
01

One Harness for Both Tools

Skills, agents and instructions sit in folders that Claude Code and GitHub Copilot read alike, so a team working with both tools keeps one set of rules. The instructions carry the conventions of the codebase, with rules of their own for each part of it.
02

Skills, Subagents and MCP Servers

The domain knowledge of the business and its recurring work become skills with their own scripts and references, each tested on the requests meant to start it. Every domain of the codebase gets a subagent with its own model and tools. MCP servers connect the agents to the systems the team builds against.
03

Guardrails and Tracing

Each agent works with the permissions its task needs, behind hooks that stop a tool call breaking a house rule before it runs. Content from MCP servers stays in quarantine against prompt injection. Tracing through OpenTelemetry shows the cost and the failures of every session.
Plugins for the Whole Team 3 steps
04

The Harness as Plugins

The skills, agents, hooks and MCP configurations of the repositories become plugins for Claude Code and GitHub Copilot, so every developer of the team who installs one works with the same harness.
05

Partner Marketplace

The plugins of this practice reach your team through a partner marketplace. Your team's own partner key opens the plugin list and the downloads granted to it.
06

Releases and Grants

Teams download the plugins of the running release, so all developers install the same version. A plugin grant brings every skill packed inside the plugin. Grants are set and withdrawn per team, plugin by plugin.
Skill Catalogue over MCP 3 steps
07

Entra ID and Groups

Every person signs in with Entra ID. The catalogue then lists the skills granted to their group, one skill or a whole plugin at a time. It opens as a view in the chat, with a search and a button that loads a skill into the conversation.
08

Skill Runs in the Chat

A skill opens as a run card: a form for the inputs it needs, with proposed defaults, and the list of its steps. The person checks the inputs and presses Start. Each step then shows whether it is open, running, done or failed.
09

Access and Usage

One view shows which group may use which skill and which plugin, with a switch for each grant, and how often each skill was used over the last 30 days.

Frequently Asked Questions

What is harness engineering?
Harness engineering builds the tools, knowledge and interfaces a coding agent acts through: the instructions, skills, subagents, MCP servers, hooks and permissions around Claude Code or GitHub Copilot. The agent then works by the conventions of the team and of the codebase. Bundled as plugins, the harness reaches every developer of the team in the same release.
What are Claude skills?
A skill is a folder with the instructions for one kind of task, along with the scripts, references and assets the task needs. The same skill folder serves Claude Code and GitHub Copilot, where it runs as an agent skill. Each skill is tested on the requests meant to start it. The catalogue over MCP serves it to every group it is granted to.
What are Claude Code plugins?
A Claude Code plugin bundles skills, agents, hooks and MCP configurations behind one manifest, so a team installs the whole set together. Plugins are published in a marketplace. A plugin can switch on its default agent as it loads. GitHub Copilot has agent plugins of its own, published through a marketplace in the same way.
Can Claude Code and GitHub Copilot share one harness?
For the most part, yes. GitHub Copilot reads skills from the same folders as Claude Code, picks up agents from the Claude Code agents folder and reads CLAUDE.md beside its own instructions. Hooks in the Claude Code settings count as Copilot hooks. Plugins have a format for each tool, so each tool gets its own plugin, built from the same skills and agents.