Ext Ops Panel
Open dashboard
Comparison

Emboss vs worker-k

Emboss is a plugin bundle for AI coding tools published by Edwin Orange. Marketplaces we read that list it: 1 (Community GitHub marketplaces). worker-k is a plugin bundle for AI coding tools published by WeiKhjan. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-13. 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
MarketplaceEmbossworker-k
Community marketplace getemboss-ai/emboss-claude-plugin Listed
Version: 1.7.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Not listed Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 1
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

Emboss vs worker-k
FactEmbossworker-k
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)1 (better)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Remote server (api.getemboss.ai/mcp)Installs as a plugin bundle
Transport (differs)Streamable HTTPNot stated
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)68
LicenceMITMIT
Repository (differs)github.com/getemboss-ai/emboss-claude-plugingithub.com/weikhjan/worker-k
Changes in the last 7 days (differs)20
First seen (differs)2026-10-132026-10-12
Endpoint at the last check (differs)not checked yetno remote endpoint we check

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

Emboss

In its own words, on Community GitHub marketplaces:

Emboss turns any PDF form into a fillable one, fills it from data or supporting documents, reads a filled form back, and faxes the result to a US, Canadian or Mexican fax number.

worker-k

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

AI workforce skills for office automation — Excel, Word, PDF, research, bank reconciliation, and more. Built for accounting and professional service firms. 8 specialized skills that turn Claude Code into a capable office assistant: create and analyze spreadsheets, generate Word documents, extract data from PDFs, conduct structured research on tax/audit/regulatory topics, automate bank reconciliations, parse claim forms, and update audit letters.

How to run each

Emboss As a Claude Code plugin

Claude Code
/plugin marketplace add getemboss-ai/emboss-claude-plugin
/plugin install emboss@getemboss

worker-k As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install worker-k@claude-community

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: Emboss · What it can do: worker-k · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-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