zk

Tracks planned zero-knowledge proof, Merkle journal, and routing attestation guidance as a pending-source catalog entry.

1|Updated Aug 5, 2026
One-click install
npx skills add https://github.com/Solizardking/Solana-Robotics-Kit --skill zk-solizardking
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: zk
Source: https://github.com/Solizardking/Solana-Robotics-Kit/tree/main/eliza/skills/zk%20copy
Command: npx skills add https://github.com/Solizardking/Solana-Robotics-Kit --skill zk-solizardking

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? This Skill acts as a placeholder catalog entry for the requested zk-router zk skill, keeping the skill visible in the Cheshire Terminal skills hub while the upstream SKILL.md source is not yet available. ## Core Features & Use Cases - Pending-Source Tracking: Records the requested source path zk-router/skills/zk and notes that no SKILL.md exists in the current zk-router checkout. - Catalog Visibility: Ensures the skill appears in /skills and /api/skills listings as a pending-source zk-router skill. - Use Case: A hub maintainer wants the zk-router zk skill advertised in the skills catalog even though the upstream repository has not yet published its SKILL.md, so this placeholder documents the planned zero-knowledge proof, Merkle journal, and routing attestation scope. ## Quick Start Ask the assistant to show the current status of the zk-router zk skill catalog entry and whether its upstream source is available.

Frequently Asked Questions about zk

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

FAQPage Schema
What is the zk skill in the skills catalog?

The zk skill is a placeholder catalog entry for the requested zk-router zk skill path. It tracks planned guidance on zero-knowledge proofs, Merkle journals, and routing attestations until the upstream SKILL.md becomes available.

Why does the zk skill show as pending-source?

The requested source path zk-router/skills/zk has no SKILL.md in the current zk-router checkout. The placeholder keeps the entry visible in /skills and /api/skills while documenting that the real source is missing.

Can I use the zk skill for zero-knowledge proof tasks now?

No, the current entry contains no operational instructions for generating proofs or attestations. It only documents the planned scope and must be replaced with the upstream SKILL.md before real zk functionality exists.

How do I activate the real zk-router zk skill?

Replace the placeholder SKILL.md with the upstream file once zk-router publishes it at the zk-router/skills/zk path. The catalog entry will then reflect the actual skill content instead of the pending-source notice.