Ext Ops Panel
Open dashboard
Comparison

gia-prospecting-engine vs event-outbound

gia-prospecting-engine is a plugin bundle for AI coding tools published by knowledgepa3. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). 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). As of our marketplace pass on 2026-10-17. 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
Marketplacegia-prospecting-engineevent-outbound
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Listed
Version: 0.2.5
Forks (GitHub): 0
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

gia-prospecting-engine vs event-outbound
Factgia-prospecting-engineevent-outbound
Marketplaces that list it11
Stars (GitHub)11
Forks (GitHub)00
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 bundle11
LicenceMITMIT
Repository (differs)github.com/knowledgepa3/gia-prospecting-enginegithub.com/luminik-io/event-outbound-skill
Changes in the last 7 days00
First seen2026-10-112026-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

gia-prospecting-engine

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

AI-powered lead generation and outreach automation for Claude Code and Cowork. Find companies hiring in your target market, research prospects, and draft personalized cold emails — all in parallel. Powered by GIA governance.

event-outbound

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

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.

How to run each

gia-prospecting-engine As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install gia-prospecting-engine@claude-community

event-outbound As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install event-outbound@claude-community

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: gia-prospecting-engine · What it can do: event-outbound · 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.

Where the data comes from: how the catalog is built