midnight-verify:verify-wallet-sdk

Classify wallet SDK claims and route them to type-checking, source investigation, or devnet E2E testing.

37|9|Updated Feb 25, 2026

Search Tags:#type-checking #wallet-sdk #dapp-connector #claim-classification #source-investigation #devnet-e2e

Ready to run

npx skills add https://github.com/devrelaicom/midnight-expert --skill midnight-verify-verify-wallet-sdk

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: midnight-verify:verify-wallet-sdk
Source: https://github.com/devrelaicom/midnight-expert/tree/main/plugins/midnight-verify/skills/verify-wallet-sdk
Command: npx skills add https://github.com/devrelaicom/midnight-expert --skill midnight-verify-verify-wallet-sdk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the classification of wallet SDK claims and chooses the correct verification path so claims are resolved accurately without unnecessary or costly tests. It prevents premature E2E runs by enforcing a pre-flight type-check and relies on source investigation as the primary evidence source.

Core Features & Use Cases

Three-step verification flow: enforces pre-flight type-checking, primary source investigation, and conditional devnet E2E fallback.
Claim type routing: maps API, architecture, connector, and behavioral claims to the appropriate verification agents and methods.
Integration hints: suggests relevant companion skills (SDK, connector, witness, wallet-sdk) to provide context for investigations.
Use Case: verify a claim like "WalletFacade exports balanceFinalizedTransaction" by running a quick type-check then a source investigation to produce a verdict.

Quick Start

Classify the claim "WalletFacade exports balanceFinalizedTransaction" and route it to type-check, source-investigator, or sdk-tester according to the skill's routing rules.

Frequently Asked Questions about midnight-verify:verify-wallet-sdk

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I verify wallet SDK claims without running unnecessary E2E tests?▼

Verifying wallet SDK claims requires enforcing a pre-flight type-check and conducting primary source investigation before running any tests. You classify the claim type and route it to the appropriate verification method, reserving devnet E2E testing only as a fallback when source evidence is inconclusive.

What is the verification flow for claims about WalletFacade exports and DApp Connector APIs?▼

The verification flow for WalletFacade exports and DApp Connector APIs follows three steps: pre-flight type-checking, primary source investigation, and conditional devnet E2E fallback. Claim type routing maps API, architecture, connector, and behavioral claims to the appropriate verification agents and methods.

When do I need devnet E2E testing for Midnight wallet SDK claims?▼

Devnet E2E testing for Midnight wallet SDK claims is needed only as a fallback when source investigation evidence is inconclusive. Pre-flight type-checking and source investigation serve as primary verification methods to resolve claims accurately without unnecessary or costly tests.

Can I use this approach to verify claims about HD derivation and Bech32m addresses in wallet SDKs?▼

Yes, you can verify claims about HD derivation and Bech32m addresses in wallet SDKs by classifying them and applying the three-step verification flow. The process enforces pre-flight type-checking and relies on source investigation to produce accurate verdicts for these branded types.

What's the best way to classify wallet SDK claims for accurate verification routing?▼

The best way to classify wallet SDK claims for accurate verification routing is to map API, architecture, connector, and behavioral claims to their appropriate verification agents. This classification determines whether type-checking, source investigation, or devnet E2E testing is the correct method.

Why does source investigation take priority over E2E testing in wallet SDK verification?▼

Source investigation takes priority over E2E testing in wallet SDK verification to prevent premature E2E runs and resolve claims accurately without unnecessary costs. Devnet E2E testing is conditional, applied only when primary source evidence proves inconclusive.