weckr vs langfuse
weckr is a plugin bundle for AI coding tools published by Ghiles Asmani. Marketplaces we read that list it: 1 (Community GitHub marketplaces). langfuse is a plugin bundle for AI coding tools published by langfuse. Marketplaces we read that list it: 3 (Claude Code: claude-plugins-official, Claude: knowledge-work-plugins, Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-14. 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 |  langfuse | |
|---|---|---|
| Community marketplace ghiles3232/weckr-sdks | Listed Version: 0.2.0 Forks (GitHub): 0 Stars (GitHub): 8 Not marked · First seen |
Not listed |
| Claude Code: claude-plugins-official | Not listed | Listed Version: 1.8.1 Forks (GitHub): 39 Stars (GitHub): 303 Not marked · First seen |
| Claude: knowledge-work-plugins | Not listed | Listed Version: 1.8.1 Forks (GitHub): 39 Stars (GitHub): 303 Not marked · First seen |
| Claude Code: claude-plugins-community | Not listed | Listed Version: 1.5.2 Forks (GitHub): 39 Stars (GitHub): 303 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 | weckr | langfuse |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 3 (better) |
| Stars (GitHub) (differs) | 8 (worse) | 303 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 39 (better) |
| Last release | Not published | Not published |
| Where it runs | Installs as a plugin bundle | Installs as a plugin bundle |
| Transport | Not stated | Not stated |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 4 | 1 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/ghiles3232/weckr-sdks | github.com/langfuse/skills |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-13 | 2026-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
weckr
The Weckr cost and margin toolkit for your AI assistant: integrate the SDK, look up current LLM token prices, estimate what an AI feature costs per user before you ship, and audit which pricing plans are unprofitable at today's model prices.
langfuse
Skills for working with Langfuse, the open-source LLM engineering platform for tracing, prompt management, and evaluation.
How to run each
weckr As a Claude Code plugin
/plugin marketplace add ghiles3232/weckr-sdks
/plugin install weckr@weckrlangfuse As a Claude Code plugin
/plugin install langfuse@claude-plugins-officialCommands 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: weckr · What it can do: langfuse · 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-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the public marketplace file https://github.com/anthropics/knowledge-work-plugins/blob/HEAD/.claude-plugin/marketplace.json. 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.