publisher profilecommunity

tag-assistant

tag-assistant publishes 6 tracked skills in DriftBot.

Catalog decision: Review-first publisher: this catalog currently carries failed runtime rows or high-risk labels, so inspect individual skills before trusting the brand halo.

6

indexed skills

53

average score

0

manual reviews

1

high-risk labels

catalog evidence snapshotbaseline-v3 coverage 2/6functionality-v2 coverage 2no manual reviews yet1 high-risk label

Read this row as a catalog snapshot: runtime coverage, deeper follow-on coverage, human review presence, and high-risk concentration before you compare individual skills.

📊 Runtime quality summary

Runtime read: stronger publisher evidence means more than broad coverage — look for low current failure pressure, some functionality depth, and stale-runtime counts that stay under control.

eligible runtime skills: 6latest touch: 20h agono current regressions

Baseline coverage

233% of eligible skills have baseline-v3 receipts

Baseline pass rate

100%2 passed · 0 currently failing

Functionality coverage

2100% of baseline-cleared skills have functionality-v2

Fixture-backed rate

0%0 functionality-v2 rows have richer fixture/example proof

Stale baseline rows

0baseline receipts older than 7 days

Functionality failures

1current failed functionality-v2 rows in the latest publisher state

This is the quality surface for the publisher, not just a directory listing. It shows how much of the catalog has real receipts, how often those receipts are passing, whether richer fixture-backed proof exists, and whether the publisher currently carries regressions, reproduced failures, or stale runtime evidence.

Latest runtime touch: 2026-03-15 06:00 UTC. Publisher-level summaries do not replace skill-level review, but they do make reputation more earned: a publisher with broader coverage, stronger pass rates, and fixture-backed proof looks different from one living on thin smoke tests.

If you want the system-wide view, open the runtime dashboard. If you want the scoring logic, read the methodology.

Fresh runtime slice Stale runtime slice

failedfunctionality-v2first failed run seen for this lane20h ago

google-keep

passedbaseline-v320h ago

google-keep

passedfunctionality-v222h ago

golf-tee-times

passedbaseline-v322h ago

golf-tee-times

Skills from this publisher

Showing 6 of 6 skills

Label mix on this page

Trusted: 2Use Caution: 2Insufficient Evidence: 1High Risk: 1

This distribution is a quick provenance cue, not a verdict. A publisher can have a mix of safer and riskier skills, so the useful move is to compare patterns here and then open the individual scorecards.

Publisher profiles are best for spotting catalog patterns: repeated shell access, common external services, whether manual review exists, and whether higher-risk labels are isolated or widespread.

On this page: 6 source-scanned, 0 catalog-only, and 0 manually reviewed entries in the current slice.

If you want the scoring logic, read the methodology. If you want the broader landscape, go back to the full index.

merge-check

tag-assistant · vsource-scanned

Analyze a GitHub pull request for mergeability — predict whether it will get merged based on technical, architectural, process, social, and compliance factors. Use when asked to review a PR, check if a PR will be merged, assess PR quality, or predict PR acceptance. Works with any GitHub PR via `owner/repo#number` or URL.

Trustedconfidence: source evidencesource-scanned

Take: Source-aware scan found normal operational surface via environment, network, or shell-related references.

Decision cue: Decent evidence base — source-level signals are available, so inspect the receipts.

pi

tag-assistant · vsource-scanned

>

Trustedconfidence: source evidencesource-scanned

Take: Source-aware scan found higher-privilege capability areas (whatsapp, email), but that alone is not evidence of malicious behavior.

Decision cue: Decent evidence base — source-level signals are available, so inspect the receipts.

wow

tag-assistant · vsource-scanned

Look up World of Warcraft characters — M+ scores, best runs, raid progression, gear, and more. Uses Raider.io (free), with optional Blizzard API and Warcraft Logs integration for armory data and raid parses.

Insufficient Evidenceconfidence: source evidencesource-scanned

Take: Source-aware scan found higher-privilege capability areas (oauth), but that alone is not evidence of malicious behavior.

Decision cue: Decent evidence base — source-level signals are available, so inspect the receipts.

nest-sdm

tag-assistant · vsource-scanned

Control Nest thermostat, doorbell, and cameras via the Google Smart Device Management (SDM) API.

Use Cautionconfidence: source evidencesource-scanned

Take: Source-aware scan found higher-privilege capability areas (token, oauth, telegram, email), but that alone is not evidence of malicious behavior.

Decision cue: Decent evidence base — source-level signals are available, so inspect the receipts.

golf-tee-times

tag-assistant · vsource-scanned

Search for golf tee times and deals near any location. Find cheapest rounds, compare prices across platforms, and get discount tips. Use when asked about golf, tee times, courses, or booking a round.

Use Cautionfollow-on functionality checks passed · 7/7confidence: source evidence

Runtime receipts + what passed2026-03-15 03:15 UTC

functionality-v2evidence depth: follow-on functionality checkstested recently: within 24 hourspassedoutput 116 Bartifacts 0worker oc-sandboxsource stage: cache hitsuite 2447 msbaseline-v3 8/8

RatioDaemon on this skillGolf Tee Times is built for search for golf tee times and deals near any location. Functionality-v2 currently passes, the trust label is High Risk, and setup looks advanced.

Observed: skill-structure-ok

Take: Potentially suspicious implementation signals detected: password.

Decision cue: Proceed carefully — suspicious signals matter more than capability surface alone.

google-keep

tag-assistant · vsource-scanned

Read, create, edit, search, and manage Google Keep notes and lists via CLI.

High Riskfollow-on functionality checks failed · 6/7confidence: source evidence

Runtime receipts + what failed2026-03-15 06:00 UTC

functionality-v2evidence depth: follow-on functionality checkstested recently: within 24 hoursfirst failed run seen for this lanepassed, runtime_failedoutput 99 Bartifacts 0worker oc-sandboxsource stage: cache hitsuite 2480 msbaseline-v3 8/8

🕵️ expected proof signal was missing🚫 skill exited with an error

RatioDaemon muttered: google-keep made it to runtime and then fell apart on contact, which is not ideal for a skill asking to be trusted.6/7 functionality-v2 checks passed before the stumble. The python help is the part that made this interesting.

Observed: skill-structure-ok

Take: Potentially suspicious implementation signals detected: password.

Decision cue: Review first — functionality-v2 already found trouble.

Page 1 / 1

Trust reading guide

Publisher-level summaries help with provenance context, but trust still lives at the skill level. Use this page to compare patterns across the publisher’s catalog, then inspect the raw findings on individual skill pages.

Back to the full index