plugins/marketplace-pro/skills/federation/SKILL.md
Federated registry protocol for multi-source plugin resolution with policy enforcement, lockfile management, and conflict detection across local, team, org, and public registries.
npx skillsauth add markus41/claude federationInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
The Federated Registry Protocol enables plugin resolution across multiple registries with configurable priority, security policies, conflict detection, and deterministic lockfiles. It transforms plugin management from a single-source package manager into an enterprise-grade multi-source orchestration system.
+-----------------+
| RegistryClient | Fetches and caches registry indexes
+--------+--------+
|
+--------v--------+
| RegistryResolver| Resolves plugins across registries
+--------+--------+
|
+--------v--------+
| PolicyEngine | Evaluates allow/deny/require rules
+--------+--------+
|
+--------v--------+
| LockfileManager | Deterministic version pinning
+-----------------+
Loads configuration from .claude/registries.json and fetches plugin indexes from multiple sources. Supports local filesystem directories and remote HTTP(S) URLs.
Key behaviors:
Resolves plugin names across all configured registries in priority order (highest first).
Conflict detection:
highest-priority (default), error, promptEvaluates security rules from .claude/policies/plugins.yaml using short-circuit matching (first match wins).
Rule types:
allow — Permits the plugindeny — Blocks the plugin with a reasonrequire — Warns when mandatory plugins are missingUnless clause: Exempts matching plugins when ALL conditions are met (trust score threshold, signature verification).
Produces plugin-lock.json for reproducible plugin environments.
Capabilities:
Configure registries with priorities:
/mp:registry add local ./plugins --priority 100
/mp:registry add team https://plugins.team.dev/index.json --priority 75
/mp:registry add public https://marketplace.claude.dev/registry.json --priority 0
Define security policy in .claude/policies/plugins.yaml
Sync registry caches:
/mp:registry sync
/mp:lock generate
plugin-lock.json to version controlmp:lock check to verify no driftmp:lock install for reproducible environmentmp:lock diff to review plugin changes.claude/policies/plugins.yaml/mp:policy enforce/mp:policy check <name>| File | Purpose |
|------|---------|
| .claude/registries.json | Registry sources and federation settings |
| .claude/policies/plugins.yaml | Security policy rules |
| plugin-lock.json | Deterministic version lock |
| config/registries.default.json | Default registry configuration |
| config/policies.default.yaml | Default security policy |
| Command | Description |
|---------|-------------|
| /mp:registry add | Add a registry source |
| /mp:registry remove | Remove a registry |
| /mp:registry list | Show configured registries |
| /mp:registry sync | Refresh all caches |
| /mp:policy check | Check a plugin against policy |
| /mp:policy list | Show policy rules |
| /mp:policy enforce | Audit installed plugins |
| /mp:lock generate | Create lockfile from current state |
| /mp:lock check | Verify plugins match lockfile |
| /mp:lock diff | Show changes since last lock |
| /mp:lock install | Install from lockfile |
src/federation/types.tssrc/federation/registry.tsconfig/registries.default.jsonconfig/policies.default.yamltools
Build Teams-native agents with the Teams SDK (formerly Teams AI Library v2) — App class, activity routing, adaptive cards, streaming, AI-generated labels, feedback, message extensions, Teams-as-MCP-server, and the bring-your-own-AI pattern with Agent Framework.
tools
Run agents on Microsoft Foundry (formerly Azure AI Foundry) Agent Service — prompt agents vs hosted agents, threads/runs and the Responses API, built-in tools (Bing grounding, code interpreter, file search, MCP, OpenAPI, A2A), connected agents, Entra agent identity, SDKs, and observability/evaluations.
tools
Build and host custom engine agents with the Microsoft 365 Agents SDK — AgentApplication, the Activity protocol, channel reach via Azure Bot Service, hosting Agent Framework or Semantic Kernel engines, and the Agents Toolkit/Playground workflow. Successor to the Bot Framework SDK.
tools
Design, govern, and extend Microsoft Copilot Studio agents — topics, generative orchestration, knowledge, tools and MCP, agent flows, autonomous triggers, publishing channels, Copilot Credits pricing, and solution-based ALM on Power Platform.