publisher profilecommunity

koba42corp

koba42corp publishes 5 tracked skills in DriftBot.

Catalog decision: Mixed but usable publisher: there is meaningful evidence here, but reputation still needs to be earned skill by skill.

5

indexed skills

63

average score

0

manual reviews

0

high-risk labels

catalog evidence snapshotno baseline-v3 receipts yetno functionality-v2 receipts yetno manual reviews yetno high-risk labels

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: 5latest touch: n/ano current regressions

Baseline coverage

00% of eligible skills have baseline-v3 receipts

Baseline pass rate

0%0 passed · 0 currently failing

Functionality coverage

00% 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

0current 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: n/a. 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

No runtime receipts for this publisher yet.

Skills from this publisher

Showing 5 of 5 skills

Label mix on this page

Trusted: 2Use Caution: 3Insufficient Evidence: 0High Risk: 0

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: 5 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.

rue-chialisp

koba42corp · vsource-scanned

Create Chia blockchain puzzles using Rue, a type-safe language that compiles to CLVM. Use for smart contract development, custom puzzle creation, or when user says "create a coin that...", "build a puzzle", "chialisp", "rue", "timelock", "multisig", "escrow", "atomic swap", or describes coin spending conditions.

Use Cautionconfidence: source evidencesource-scanned

Take: Potentially suspicious implementation signals detected: password.

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

chia-walletconnect

koba42corp · vsource-scanned

Telegram Web App for Chia wallet verification via WalletConnect and Sage. Enables cryptographic proof of wallet ownership through signature verification using MintGarden API.

Use Cautionconfidence: source evidencesource-scanned

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

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

mintgarden

koba42corp · vsource-scanned

Browse, search, and analyze Chia NFTs via the MintGarden API.

Use Cautionconfidence: source evidencesource-scanned

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

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

autoresponder

koba42corp · vsource-scanned

Monitor iMessage/SMS conversations and auto-respond based on configurable rules, AI prompts, and rate-limiting conditions. Use when you need to automatically reply to specific contacts with AI-generated responses based on conversation context. Also use when the user asks to manage auto-responder settings, contacts, prompts, or view status/history.

Trustedconfidence: source evidencesource-scanned

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

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

chia-splitxch

koba42corp · vsource-scanned

Create SplitXCH royalty split addresses from plain language descriptions. Use when the user wants to split XCH payments, royalties, or revenue between multiple recipients. Triggers on "split royalties", "royalty split", "splitxch", "split XCH between", "revenue share", "payment split", "basis points split", or any request to divide Chia payments among wallets. Supports nested/cascading splits for complex hierarchies and 128+ recipients.

Trustedconfidence: source evidencesource-scanned

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

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

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