القائمة
Generate zero-knowledge proofs with snarkjs for zkVerify. Use when the user wants to create proofs, generate witness, or run the prover with their circuit inputs.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Design system for the Horizen protocol website (www.horizen.io). Use this skill whenever building UI, components, pages, or layouts for the Horizen protocol — including when the user mentions Horizen, hz- tokens, horizen.io, or needs to create web3/blockchain UI following Horizen's yellow/black brand. Also use when the user references horizen-design-system.html or asks about Horizen design tokens, typography (Funnel Display, Proxima Nova), or component patterns.
Design system for the Horizen Labs company website (www.horizenlabs.io). Use this skill whenever building UI, components, pages, or layouts for Horizen Labs — including when the user mentions Horizen Labs, hl- tokens, horizenlabs.io, or needs to create institutional/technical UI following Horizen Labs' navy/teal/magenta brand with sharp corners. Also use when the user references horizenlabs-design-system.html or asks about Horizen Labs design tokens, typography (Azeret Mono, Roboto), component patterns, or the sharp-corner design philosophy.
Design system for the zkVerify verification protocol website (www.zkverify.io). Use this skill whenever building UI, components, pages, or layouts for zkVerify — including when the user mentions zkVerify, zk- tokens, zkverify.io, zero-knowledge proofs, or needs to create verification/ZK-proof UI following zkVerify's green(Pulse)/blue(Signal)/dark(Void) brand. Also use when the user references zk-verify-design-system.html or asks about zkVerify design tokens, typography (Monigue, Space Grotesk), or component patterns.
Horizen Labs Agent Marketplace integration on Base Sepolia — full pipeline from ZK proof submission (Kurier) through attestation relay to on-chain validation recording. Covers agent registration (IdentityRegistry), validation recording (ValidationGateway), attestation polling, and marketplace discovery.
Kurier REST API for simplified proof verification. Use when you want the simplest integration path, don't need real-time events, or are building serverless/REST-based architectures. Covers API key setup, proof submission, status polling, and aggregation.
This skill should be used when the user asks to "analyze a crate for no_std", "assess no_std compatibility", "check if a crate supports no_std", "evaluate no_std support", "no_std assessment report", "can this crate compile with no_std", "no_std feasibility", "what std dependencies does this crate have", or mentions evaluating a Rust crate or library for `no_std` compilation support.
| name | groth16-prove |
| description | Generate zero-knowledge proofs with snarkjs for zkVerify. Use when the user wants to create proofs, generate witness, or run the prover with their circuit inputs. |
| argument-hint | ["circuit-name"] |
Help the user generate zero-knowledge proofs using their compiled Circom circuit.
If invoked with an argument (e.g., /groth16-prove password_hash), use it as the circuit name.
If no argument provided, look for compiled circuits in build/ (files ending in .zkey) or ask the user which circuit to prove.
Before generating proofs, verify all prerequisites exist:
ls build/*.zkey build/*_js/*.wasm build/verification_key.json 2>/dev/null
ls inputs/*.json 2>/dev/null
| Check | If Missing |
|---|---|
build/<circuit>.zkey | Run /groth16-compile first |
build/<circuit>_js/<circuit>.wasm | Run /groth16-compile first |
build/verification_key.json | Run /groth16-compile first |
inputs/<input>.json | Create input file (see examples.md) |
If prerequisites are missing, stop and help user get them first.
This skill generates Groth16 proofs from compiled Circom circuits using snarkjs.
What this covers:
Prerequisites (from /groth16-compile):
.wasm file).zkey file)verification_key.json)node build/<circuit_name>_js/generate_witness.js \
build/<circuit_name>_js/<circuit_name>.wasm \
inputs/input.json \
build/witness.wtns
mkdir -p proofs
snarkjs groth16 prove \
build/<circuit_name>.zkey \
build/witness.wtns \
proofs/proof.json \
proofs/public.json
snarkjs groth16 verify \
build/verification_key.json \
proofs/public.json \
proofs/proof.json
Expected output: [INFO] snarkJS: OK!
proofs/
├── proof.json # The ZK proof (safe to share)
└── public.json # Public signals (revealed in verification)
/groth16-submit to submit proof to zkVerifyproofs/public.json - These values are revealed during verificationproof.json is safe to share - It doesn't reveal private inputsOK!)