midnight-verify:verify-by-wallet-source

Verify wallet-related claims by inspecting Midnight Wallet monorepo source code.

37|9|Updated Feb 25, 2026

Search Tags:#monorepo #verify #wallet #evidence-based #source-code #claim-verification #octocode-mcp

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reads and verifies claims about the Midnight Wallet SDK by inspecting the actual source code, ensuring that conclusions stem from primary artifacts rather than docs or tests.

Core Features & Use Cases

Uses primary evidence from function signatures, type exports, and implementations in source files to validate claims.
Treats tests as navigation aids that point toward the correct source without serving as evidence themselves.
Provides a clear workflow (repo routing, targeted file lookups, and optional local cloning) to verify cross-package wallet claims across a monorepo like Midnight Wallet.

Quick Start

Clone the Midnight Wallet repository and inspect the targeted source files to verify claims against actual implementations.

Frequently Asked Questions about midnight-verify:verify-by-wallet-source

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

FAQPage Schema

How do I verify wallet claims by inspecting source code in a monorepo?▼

You can verify wallet claims by using targeted path lookups, code search, and optional local cloning to inspect function definitions, type exports, and implementations directly from source files in the repository.

What is the best way to validate API surface claims for a DApp Connector?▼

Validating API surface claims involves inspecting actual source code implementations rather than relying on documentation, using tests strictly as navigational aids to locate the correct source files.

Can I use documentation as evidence when verifying wallet SDK implementations?▼

Documentation cannot serve as primary evidence when verifying wallet SDK implementations; it only provides hints, while conclusions must stem from primary artifacts like function signatures and type exports.

How do I check variant runtime implementations across a monorepo?▼

Checking variant runtime implementations requires routing through the repository to perform targeted file lookups, optionally cloning the monorepo locally to inspect source code evidence.

Why should tests only be used as navigation aids for claim verification?▼

Tests serve as navigation aids because they point toward the correct source without providing evidence themselves, ensuring claim verification relies strictly on actual source code implementations.