Ext Ops Panel
Open dashboard
Comparison

architecture-studio vs microsoft-365-agents-toolkit

architecture-studio is a plugin bundle for AI coding tools published by AlpacaLabsLLC. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). microsoft-365-agents-toolkit is a plugin bundle for AI coding tools published by microsoft. Marketplaces we read that list it: 1 (Copilot CLI: github/copilot-plugins). As of our marketplace pass on 2026-10-16. 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
Marketplacearchitecture-studiomicrosoft-365-agents-toolkit
Claude Code: claude-plugins-community Listed
Version: 1.4.1
Forks (GitHub): 81
Stars (GitHub): 381
Not marked · First seen
Not listed
Copilot CLI: github/copilot-plugins Not listed Listed
Version: 1.1.0
Forks (GitHub): 143
Stars (GitHub): 1 033
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

architecture-studio vs microsoft-365-agents-toolkit
Factarchitecture-studiomicrosoft-365-agents-toolkit
Marketplaces that list it11
Stars (GitHub) (differs)381 (worse)1 033 (better)
Forks (GitHub) (differs)81 (worse)143 (better)
Last releaseNot publishedNot published
Where it runsInstalls as a plugin bundleInstalls as a plugin bundle
TransportNot statedNot stated
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)4Not published
Parts of the bundle (differs)63Not published
LicenceMITMIT
Repository (differs)github.com/alpacalabsllc/skills-for-architectsgithub.com/microsoft/work-iq
Changes in the last 7 days00
First seen2026-10-112026-10-11

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

architecture-studio

In its own words, on Claude Code: claude-plugins-community:

Description: Architecture Studio is a Claude plugin system for architects, designers, and AEC professionals. It includes 7 autonomous agents, 36 skills, 6 rules, and 3 hooks organized into 9 installable plugins — covering site research, NYC property due diligence, zoning envelope analysis, workplace programming, CSI specifications, sustainability (EPD parsing and comparison), FF&E product research, and presentation generation. A single entry point (`/studio`) routes users to the right agent or skill based on natural language. Agents orchestrate multiple skills, exercise judgment, and hand off to each other across the project lifecycle. Skills ship with bundled reference data — NYC Zoning Resolution chapters, IBC occupancy load factors, workplace benchmarks, and Uruguay zoning regulations. Key features: - `/studio` smart router — describe your task, get routed automatically - 7 agents with handoff logic (site planner → zoning expert → workplace strategist → materials researcher → FF&E designer → sustainability

microsoft-365-agents-toolkit

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

Toolkit for building Microsoft 365 Copilot declarative agents — scaffolding, JSON manifest development, and capability configuration.

How to run each

architecture-studio As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install architecture-studio@claude-community

microsoft-365-agents-toolkit

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

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

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: architecture-studio · What it can do: microsoft-365-agents-toolkit · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the public marketplace file https://github.com/github/copilot-plugins/blob/HEAD/.github/plugin/marketplace.json. 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