⛏️ OVOS Klondike Mercantile

Every OVOS skill, plugin, addon or tool we could dig up across GitHub.
Found automatically · tested on testing, alpha and stable · reported by maintainers and users

ℹ️ How it works

What you see comes from three sources, and each is shown as such:

  • 🔎 What we found: GitHub is searched every few hours (code, topics, repo names) and each repo is checked against PyPI, its GitHub releases and OVOS's own upcoming Skill Store. That gives the badges such as Looks Complete. They describe the repo, not whether it works.
  • 🧪 What we tested: every Looks Complete skill and pipeline plugin is installed and started on each OVOS release channel, next to the OVOS installer's default skills, and its own sentences are sent to it. How the tests work
  • 🙋 What people reported: a maintainer's test on a real device, and reports from users' own setups, shown next to our result, never as it. Maintainer and user reports

The release channels, each with its own label on every card:

  • testing: what the OVOS installer installs by default, so what most users run. Weighs most in the Recommended order.
  • alpha: the newest versions; the installer's other choice.
  • stable: the last stable release; changes rarely.

The versions in each channel move over time, so every result is tied to the channel's live version list, and a skill is tested again when that list or the skill's own release changes.

Maintainer? Add the ovos topic to get found, a skill.json to get classified, a PyPI package and a GitHub release to reach Looks Complete and get tested. 📖 Guide for maintainers · 📊 Test overview by install profile

Why "Klondike"? A hand-built list once tried to catalog the Mycroft/OVOS skills; it went stale and is gone. This one digs itself. Release notes · Suggest an idea

🏷️ What do the labels and badges mean?

Each card has one small label per tested release channel: testing (the installer's default), alpha and stable, followed by a quality label when the skill's own sentences reach it: 🎯 Routes, or ⛏ Klondike Gold when they still do on a well-equipped install. The coloured badges describe the repo itself. 🧪 How skills are tested · 🙋 Maintainer and user reports

🧪 What we tested (one label per channel, then Routes or Klondike Gold)

🔎 What we found (badges)

Looks Complete
Has a proper skill.json/entry-point declaration, is published on PyPI, and has a GitHub release - OR is already listed in OVOS's own upcoming Skill Store (not yet officially launched; a stronger signal on its own, since that store doesn't require PyPI or a release either). Not the same as confirmed working: see What we tested above.
Incomplete
Has a skill.json, but is missing a PyPI release and/or a GitHub release.
Inferred, Unconfirmed
No skill.json found. The repo tags itself as OVOS-related and its code shows real signs of being a skill, but everything shown is guessed from the repo's own description/topics - treat it as a lead, not a confirmed listing.
Works Offline
The skill's own description states it needs no internet connection.
LAN Only
Uses local networking (device discovery, mDNS, etc) but not the internet - a different thing from "Works Offline" (no networking at all).
Offline + Online
Works offline, with an optional online component (e.g. a fallback for content the offline data doesn't cover).
Needs Internet (WAN)
Fetches content from the internet to function.
OVOS Store
Also listed in OVOS's own upcoming Skill Store (not yet officially launched).
API key
Requires an API key or similar credential to configure.
Not on PyPI / No release / No license
Exactly what it says - shown as a plain fact, not a reason to exclude the skill.
📊 Ecosystem stats

Loading…