Ext Ops Panel
Open dashboard
Comparison

eterdis-strategy-skills vs Kova

eterdis-strategy-skills is a plugin bundle for AI coding tools published by eterdis. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Kova is an MCP server published by kovatools.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-29. 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
Marketplaceeterdis-strategy-skillsKova
Claude Code: claude-plugins-community Listed
Version: 8bd22e9
Forks (GitHub): 1
Stars (GitHub): 10
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.10.1
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

eterdis-strategy-skills vs Kova
Facteterdis-strategy-skillsKova
Marketplaces that list it11
Stars (GitHub) (differs)10 (better)0 (worse)
Forks (GitHub) (differs)1 (better)0 (worse)
Last release (differs)Not published2026-10-13
Where it runs (differs)Installs as a plugin bundleRemote server (kovatools.com/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)Not statedMIT
Repository (differs)github.com/eterdis/strategy-skillsgithub.com/kovatools/kova-agent-plugin
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 4 days ago, requires a key

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

eterdis-strategy-skills

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

Open strategy frameworks for AI agents — 11 skills that turn any LLM into a strategy thinking partner. Each skill is a structured SKILL.md prompt that guides the AI through a proven strategic framework (VRIO, Wardley Mapping, Playing to Win, Pre-Mortem, and more). Built on 20 years of consulting practice. Three modes per skill: Diagnostic (deep session), Review (periodic check), and Alert Triggers (early warnings). All skills share a company-context.md file for accumulated strategic intelligence. CC BY 4.0 licensed.

Kova

In its own words, on Official MCP Registry:

Saves a declared investment strategy so any agent can check a portfolio against it.

How to run each

eterdis-strategy-skills As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install eterdis-strategy-skills@claude-community

Kova As a remote MCP server

Claude Code
claude mcp add --transport http kova https://kovatools.com/mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Kova 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: eterdis-strategy-skills · What it can do: Kova · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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