testing

Tracks a pending zk-router testing skill placeholder until the upstream SKILL.md becomes available.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? The requested zk-router testing skill path does not exist in the current checkout, leaving a gap in the skills catalog. This placeholder keeps the zk-router testing entry visible in the Cheshire Terminal skills hub so users know the skill is planned and can track its status. ## Core Features & Use Cases - Catalog Placeholder: Advertises the requested zk-router testing skill in /skills and /api/skills even though the source SKILL.md is missing. - Source Status Tracking: Documents the requested path (zk-router/skills/testing) and explicitly notes that no local SKILL.md was found. - Use Case: A developer browsing the skills hub sees the zk-router testing entry marked as pending-source, understands it is not yet functional, and knows to replace the placeholder once the upstream SKILL.md is published. ## Quick Start Ask the assistant to show the current status of the zk-router testing skill and confirm whether the upstream SKILL.md has been added yet.

Frequently Asked Questions about testing

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

FAQPage Schema
What is the zk-router testing skill?

It is a planned skill for zk-router testing guidance covering smoke tests and verification. The current entry is only a placeholder because the requested source path zk-router/skills/testing has no SKILL.md in the current checkout.

Why does the testing skill show as pending-source?

The placeholder exists because no SKILL.md was found at the requested zk-router path in the local checkout. It remains visible in /skills and /api/skills so the catalog advertises the planned skill until the real file is added.

How do I activate the zk-router testing skill?

Replace the placeholder SKILL.md with the upstream version once the zk-router repository publishes it at zk-router/skills/testing. Until then, the entry only provides catalog visibility and no operational testing instructions.

Can I run smoke tests with this placeholder skill?

No, the placeholder contains no executable testing logic, scripts, or verification procedures. It only documents the requested source path and its pending status in the Cheshire Terminal skills hub.

Where is the upstream source for the zk-router testing skill?

The expected source is the zk-router repository at github.com/Solizardking/zk-router, specifically the path zk-router/skills/testing. Check that repository for when the official SKILL.md becomes available.