Ext Ops Panel
Open dashboard
Comparison

telegram vs nash-webhooks

telegram is a plugin bundle for AI coding tools published by anthropics. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-official). nash-webhooks is a plugin bundle for AI coding tools published by Hookdeck. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-24. 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
Marketplacetelegramnash-webhooks
Claude Code: claude-plugins-official Listed
Version: 0.0.7
Forks (GitHub): 4 643
Stars (GitHub): 44 178
Not marked · First seen
Not listed
Community marketplace hookdeck/webhook-skills Not listed Listed
Version: not stated
Forks (GitHub): 16
Stars (GitHub): 94
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

telegram vs nash-webhooks
Facttelegramnash-webhooks
Marketplaces that list it11
Stars (GitHub) (differs)44 178 (better)94 (worse)
Forks (GitHub) (differs)4 643 (better)16 (worse)
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)3Not published
Licence (differs)Not statedMIT
Repository (differs)github.com/anthropics/claude-plugins-officialgithub.com/hookdeck/webhook-skills
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-21

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

telegram

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

Telegram messaging bridge with built-in access control. Manage pairing, allowlists, and policy via /telegram:access.

nash-webhooks

In its own words, on Community GitHub marketplaces:

Receive and verify Nash (usenash.com, now nash.ai) delivery orchestration webhooks. Nash sends webhooks through Svix, so verify the svix-id, svix-timestamp and svix-signature headers (HMAC-SHA256, base64, over "{svix-id}.{svix-timestamp}.{raw body}" keyed with the endpoint's whsec_ signing secret) with the svix SDK or manually. Use when setting up a Nash webhook handler, debugging Nash signature verification, or handling the { type, event, data } payload for delivery events (dropoff_complete, canceled_by_provider), task events (task.created, task.canceled_by_provider), courier_location.updated, courier_name.updated and shift.dispatched.

How to run each

telegram As a Claude Code plugin

Claude Code
/plugin install telegram@claude-plugins-official

nash-webhooks As a Claude Code plugin

Claude Code
/plugin marketplace add hookdeck/webhook-skills
/plugin install nash-webhooks@webhook-skills

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: telegram · What it can do: nash-webhooks · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/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