Ext Ops Panel
Open dashboard
Comparison

skills-for-copilot-studio vs Support Agent Admin by Nova (CIVAI)

skills-for-copilot-studio is a plugin bundle for AI coding tools published by microsoft. Marketplaces we read that list it: 1 (Copilot CLI: github/awesome-copilot). Support Agent Admin by Nova (CIVAI) is an MCP server published by nova.civai.co. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-24. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplaceskills-for-copilot-studioSupport Agent Admin by Nova (CIVAI)
Copilot CLI: github/awesome-copilot Listed
Version: 1.0.11
Forks (GitHub): 103
Stars (GitHub): 482
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.1.0
No figure published
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

skills-for-copilot-studio vs Support Agent Admin by Nova (CIVAI)
Factskills-for-copilot-studioSupport Agent Admin by Nova (CIVAI)
Marketplaces that list it11
Stars (GitHub) (differs)482No figure on GitHub
Forks (GitHub) (differs)103No figure on GitHub
Last release (differs)2026-10-23Not published
Where it runs (differs)Installs as a plugin bundleRemote server (nova.civai.co/mcp/agents/support-agent-admin)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)2Not published
Parts of the bundle (differs)36Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/microsoft/skills-for-copilot-studioNot stated
Changes in the last 7 days (differs)20
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkNot responding since 2026-10-24

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

skills-for-copilot-studio

In its own words, on Copilot CLI: github/awesome-copilot:

Microsoft Copilot Studio YAML authoring toolkit. Create, edit, validate, and test Copilot Studio agents using YAML files.

Support Agent Admin by Nova (CIVAI)

In its own words, on Official MCP Registry:

I manage your Support Agent CRM, pipeline analytics, follow-ups, Leads Discovery, and workspace out…

How to run each

skills-for-copilot-studio

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Support Agent Admin by Nova (CIVAI) As a remote MCP server

Claude Code
claude mcp add --transport http support-agent-admin https://nova.civai.co/mcp/agents/support-agent-admin

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Support Agent Admin by Nova (CIVAI) has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: skills-for-copilot-studio · What it can do: Support Agent Admin by Nova (CIVAI) · Compare two other plugins

Data comes from the public marketplace file https://github.com/github/awesome-copilot/blob/HEAD/.github/plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built