upstream-backport vs okl — Observed Knowledge Ledger
upstream-backport is a plugin bundle for AI coding tools published by JZ Loh. Marketplaces we read that list it: 1 (Community GitHub marketplaces). okl — Observed Knowledge Ledger is an MCP server published by emeraldleaf. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-15. 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
| Marketplace |  okl — Observed Knowledge Ledger | |
|---|---|---|
| Community marketplace bitshelf/linux-skills | Not seen in the last pass Version: 1.0.1 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.8.7 Downloads/month (PyPI): 1 293 Downloads/week (PyPI): 1 005 Forks (GitHub): 1 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
| Fact | upstream-backport | okl — Observed Knowledge Ledger |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 0 (worse) | 1 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 1 (better) |
| Last release (differs) | Not published | 2026-10-14 |
| Where it runs (differs) | Remote server (mcp.deepwiki.com/mcp) | On your machine (observed-knowledge-ledger) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Hooks it runs (differs) | 1 | 2 |
| Parts of the bundle (differs) | 8 | 9 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/bitshelf/linux-skills | github.com/emeraldleaf/okl |
| Changes in the last 7 days (differs) | 2 | 4 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 22 h ago | no 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
upstream-backport
免克隆取证 + 五阶段 backport 工作流（Buildroot/Yocto/AOSP/Debian/内核）
okl — Observed Knowledge Ledger
Lessons your coding agent can trust: briefed before each task, proven by checks, flagged on change.
How to run each
upstream-backport As a Claude Code plugin
/plugin marketplace add bitshelf/linux-skills
/plugin install upstream-backport@embedded-backport-toolsokl — Observed Knowledge Ledger As a local MCP server: PyPI package
claude mcp add --transport stdio okl -- uvx --with "mcp>=1.2" observed-knowledge-ledger mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only upstream-backport has a remote endpoint we check. How we check endpoints
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: upstream-backport · What it can do: okl — Observed Knowledge Ledger · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.