More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    FPGA Proof Chain

    1

    A 12-station proof chain for FPGA development that replaces guesswork with artifact-backed evidence.

    $30

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    FPGA Proof Chain

    FPGA Proof Chain

    Example session with this skill installed

    Run a status check on the led_controller block and tell me why the hardware isn't responding even though it's flashed.

    • Read your context and instructions
    • Compiled the fpga proof chain

    Station 09 (Flash) reports artifacts, but checkpoint 9.4 (visual check) failed. The chain indicates missing artifacts for Station 07 (Timing). Check *_timing.rpt for WNS < 0. Without timing closure, bitstream behavior is undefined. Resolve Station 07 before re-verifying the flash log.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    The problem

    FPGA projects often stall at "it should work" while hardware remains dead. Developers waste days debugging RTL for issues that are actually caused by timing violations, missing resets, or broken chains of custody.

    What it does

    • Scans project directories to identify missing proof artifacts across 12 maturity stations.
    • Enforces a 60-checkpoint validation sequence from golden models to logic-analyzer measurement.
    • Provides specific failure mode lessons for common issues like CDC errors and simulation mismatches.
    • Generates structured handover documentation with SHA-256 bitstream tracking.
    • Classifies errors between harness, RTL, and spec to prevent fixing correct hardware.

    Frameworks & tools

    Works with Yosys, Icarus Verilog, and major vendor toolchains (Vivado, Quartus, Libero). Scripts use Python 3.

    Why this beats prompting it yourself

    General LLMs often suggest Verilog fixes for hardware-level timing or reset issues they cannot see. This skill forces a rigorous physical evidence chain, ensuring you never debug a bitstream that hasn't passed timing or a testbench that lacks a golden model.

    Use cases

    • Auditing a legacy FPGA block to see which validation steps were skipped.
    • Systematizing the sign-off process between RTL design and hardware lab testing.
    • Troubleshooting "simulation-green, hardware-dead" scenarios using station-specific checks.
    • Maintaining a verifiable chain of custody for bitstreams in high-reliability environments.

    Known limitations

    Does not write initial Verilog code, install vendor tools, or design PCBs. Requires an existing project structure with rtl/ and tb/ directories to scan artifacts.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Agents & Orchestration.

    Requires local project files (rtl/, tb/) for artifact scanning. Does not perform vendor tool installation or PCB design.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 3 months ago

    Permissions

    Terminal / Shell
    Read Files
    Write Files

    File Scopes

    rtl/**
    tb/**
    HANDOVER*

    Shell runs the bundled artifact scanner (chain_status.py, Python stdlib only). Read: scans project files for proof artifacts. Write: creates/updates HANDOVER and validation documents. No network access - fully local.

    Listed3 months ago

    What's inside

    Frequently Asked Questions

    This skill enforces a 12-station validation sequence that requires artifact-backed evidence for every stage of development, preventing the common trap of debugging RTL for issues actually caused by timing, resets, or clock domain crossings.

    The skill supports industry-standard vendor suites including Xilinx Vivado, Intel Quartus, and Microchip Libero, as well as open-source tools like Yosys and Icarus Verilog.

    You will receive the AI agent skill configuration, the Python-based scanning scripts, and the 60-checkpoint validation framework integrated into the 12 maturity stations.

    While it can analyze any Verilog-based project, the skill requires a standard directory structure (specifically rtl/ and tb/ folders) to successfully scan for and verify your design artifacts.

    No, this skill is a diagnostic and verification framework; it focuses on auditing and proving existing logic rather than generating initial HDL code or designing physical PCB layouts.

    It classifies failures into three distinct categories—harness, RTL, or spec—ensuring you don't waste time 'fixing' correct hardware code when the issue is actually in the test environment or timing constraints.

    New in Agents & Orchestration