verify-mock

Validate silicon API mocks in tt-emule against verification checklists.

4|1|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/tenstorrent/tt-emule --skill verify-mock
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify-mock
Source: https://github.com/tenstorrent/tt-emule/tree/main/.claude/skills/verify-mock
Command: npx skills add https://github.com/tenstorrent/tt-emule --skill verify-mock

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents regressions and silent failures in tt-emule by providing a rigorous, multi-stage verification checklist for new silicon API mocks.

Core Features & Use Cases

  • Standardized Verification: Ensures mock signatures, math accuracy, and format-aware paths are correctly implemented.
  • Regression Prevention: Guides the user through build sanity checks and regression testing against existing tt-metal baselines.
  • Use Case: After implementing a new compute kernel mock, use this checklist to confirm the implementation handles bf16/fp32 formats correctly and passes the sentinel test before merging.

Quick Start

Run the verify-mock skill to audit your current mock implementation against the mandatory checklist and regression suite.

Frequently Asked Questions about verify-mock

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

FAQPage Schema
How do I validate silicon API mocks in tt-emule before deployment?

Validate silicon API mocks in tt-emule by applying a multi-stage verification checklist that checks mock signatures, math accuracy, and format-aware paths to prevent regressions before deployment.

What is the best way to prevent regressions when implementing compute kernel mocks?

Prevent regressions in compute kernel mocks by running build sanity checks and regression testing against existing tt-metal baselines to ensure strict parity with Tenstorrent hardware.

How do I verify bf16 and fp32 format handling in hardware emulation mocks?

Verify bf16 and fp32 format handling in hardware emulation mocks by auditing the implementation against a mandatory checklist to confirm correct format-aware paths and sentinel test passage before merging.

Does tt-emule emulation require regression testing against tt-metal baselines?

Yes, tt-emule emulation requires regression testing against tt-metal baselines to maintain high-fidelity hardware emulation and enforce architectural constraints during kernel-level development and host-side integration.

When do I need to run a verification checklist for kernel-level development mocks?

Run a verification checklist for kernel-level development mocks after implementing a new compute kernel mock to confirm math accuracy, format-aware paths, and architectural constraint adherence before merging.

Why does my silicon API mock fail the sentinel test in tt-emule?

Silicon API mocks fail the sentinel test in tt-emule due to incorrect mock signatures, math inaccuracies, or improper handling of bf16 and fp32 format-aware paths that violate architectural constraints.