event-outbound vs saleshandy
event-outbound is a plugin bundle for AI coding tools published by luminik-io. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). saleshandy is a plugin bundle for AI coding tools published by saleshandy. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-22. 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 |  event-outbound |  saleshandy |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 0.2.5 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 0 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 | event-outbound | saleshandy |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 1 (better) | 0 (worse) |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (mcp.saleshandy.com/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 1 | 5 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/luminik-io/event-outbound-skill | github.com/saleshandy/saleshandy-plugin |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Answered with HTTP 400 (23 h ago) |
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
event-outbound
Create buyer-first email and LinkedIn outreach for B2B trade shows and conferences. Give event details, ICP, target personas, and sender context. event-outbound drafts pre-event, day-of, and post-event touches, then validates each one locally for channel length, subject quality, inbox preview, buyer focus, CTA clarity, forced event phrasing, and common AI-sales cliches. Built by Luminik from 20K+ outbound touches reviewed across 50+ events. Runs inside Claude Code with no extra API key.
saleshandy
Saleshandy prospecting and enrichment for Claude Code — natural-language ICP search and one-shot lead enrichment, wired through the Saleshandy MCP server.
How to run each
event-outbound As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install event-outbound@claude-communitysaleshandy As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install saleshandy@claude-communityCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only saleshandy 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: event-outbound · What it can do: saleshandy · Compare two other plugins
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.