Ext Ops Panel
Open dashboard
Comparison

channel3-api vs Procurement Tools

channel3-api is a plugin bundle for AI coding tools published by channel3-ai. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Procurement Tools is a plugin bundle for AI coding tools published by danielrosehill. Marketplaces we read that list it: 1 (Community GitHub marketplaces). 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
Marketplacechannel3-apiProcurement Tools
Community marketplace channel3-ai/skills Listed
Version: not stated
Forks (GitHub): 0
Stars (GitHub): 12
Not marked · First seen
Not listed
Community marketplace danielrosehill/claude-code-plugins Not listed Listed
Version: 2.3.0
Forks (GitHub): 0
Stars (GitHub): 2
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

channel3-api vs Procurement Tools
Factchannel3-apiProcurement Tools
Marketplaces that list it11
Stars (GitHub) (differs)12 (better)2 (worse)
Forks (GitHub)00
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
Parts of the bundle (differs)155
Licence (differs)Not statedMIT
Repository (differs)github.com/channel3-ai/skillsgithub.com/danielrosehill/procurement-tools-plugin
Changes in the last 7 days22
First seen2026-10-152026-10-15

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

channel3-api

In its own words, on Community GitHub marketplaces:

Integrate the Channel3 API for product search (text, image, semantic, and agentic), similar-products recommendations, multi-merchant offer comparison, URL lookup, conversational shopping agents, price tracking, click/transaction reporting, and affiliate commissions across TypeScript, Python, and REST — plus a React component library (shadcn registry) for storefront UIs

Procurement Tools

In its own words, on Community GitHub marketplaces:

Product research and procurement skills with a particular focus on technical specification conformance — does this part actually meet the requirement, and can you show your working. Marketplace-agnostic: spec definition from a vague want or a photograph, annotated search vocabulary, versioned spec-as-code, manufacturer datasheet retrieval, cross-region part-number equivalence, conformance evaluation matrices, bills of materials and RFQ packages. Plus the surrounding process: intake, research, compare, evaluate, recommend, market-check, spec-driven market landscape surveys, live price/delivery scanning through your own VPN egress, preference memory and hardware-rig profiling. Hands off to the marketplace-specific plugins (shopping, israel-shopping, amazon, aliexpress-israel-skills) once a question becomes about a particular shop.

How to run each

channel3-api As a Claude Code plugin

Claude Code
/plugin marketplace add channel3-ai/skills
/plugin install channel3-api@channel3

Procurement Tools As a Claude Code plugin

Claude Code
/plugin marketplace add danielrosehill/claude-code-plugins
/plugin install procurement-tools@danielrosehill

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: channel3-api · What it can do: Procurement Tools · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. 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