Ext Ops Panel
Open dashboard
Comparison

workflow-toolkit vs han-linear

workflow-toolkit is a plugin bundle for AI coding tools published by dougwithseismic. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). han-linear is a plugin bundle for AI coding tools published by testdouble. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-11-09. 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
Marketplaceworkflow-toolkithan-linear
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Not listed
Community marketplace testdouble/han Not listed Listed
Version: 1.1.2
Forks (GitHub): 28
Stars (GitHub): 342
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

workflow-toolkit vs han-linear
Factworkflow-toolkithan-linear
Marketplaces that list it11
Stars (GitHub) (differs)1 (worse)342 (better)
Forks (GitHub) (differs)0 (worse)28 (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)7Not published
Parts of the bundle (differs)301
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/dougwithseismic/workflow-toolkitgithub.com/testdouble/han
Changes in the last 7 days (differs)02
First seen (differs)2026-10-122026-11-08

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

workflow-toolkit

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

Get up to speed in any codebase, any size. Non-opinionated workflow plugin with session journaling, local task tracking, GitHub issue sync, knowledge base generation, and lifecycle hooks. All backed by SQLite, all local.

han-linear

In its own words, on Community GitHub marketplaces:

Linear-facing extensions to the Han suite. Adds work-items-to-linear, which creates one Linear issue per slice from a work-items file. Works through the Linear MCP server and requires it to be configured. Depends on no other Han plugin. Opt-in: installed on its own, not pulled in by the han meta-plugin.

How to run each

workflow-toolkit As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install workflow-toolkit@claude-community

han-linear As a Claude Code plugin

Claude Code
/plugin marketplace add testdouble/han
/plugin install han-linear@han

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: workflow-toolkit · What it can do: han-linear · 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 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