lightprotocol/skills

testing

For testing with Light Protocol programs and clients on localnet, devnet, and mainnet validation.

First seen Feb 23, 2026

Installation

$ npx skills add lightprotocol/skills --skill testing

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from lightprotocol/skills · top by installs.

npx skills add lightprotocol/skills

Browse all from lightprotocol/skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 7
License LICENSE
Default branch main
Open issues 0
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Version1.0.0
LicenseMIT
Declared agents clawdbot
More metadata
source
https://github.com/Lightprotocol/skills
documentation
https://www.zkcompression.com
openclaw
{"requires":{"env":"[\"HELIUS_API_KEY\"] # Only needed for devnet testing","bins":["node","solana","anchor","cargo","light"]}}

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 3,403 B
  • docs SUMMARY.md 112 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 46 installs

SKILL.md

Light Protocol testing

Workflow

  1. Clarify intent

- Recommend plan mode, if it's not activated - Use AskUserQuestion to resolve blind spots - All questions must be resolved before execution

  1. Identify references and skills

- Match task to [test references](#routing) below - Locate relevant documentation and examples

  1. Write plan file (YAML task format)

- Use AskUserQuestion for anything unclear — never guess or assume - Identify blockers: permissions, dependencies, unknowns - Plan must be complete before execution begins

  1. Execute

- Use Task tool with subagents for parallel research - Subagents load skills via Skill tool - Track progress with TodoWrite

  1. When stuck: ask to spawn a read-only subagent with Read, Glob, Grep, and DeepWiki MCP access, loading skills/ask-mcp. Scope reads to skill references, example repos, and docs.

Routing

Task Reference
Start local validator [references/local.md](references/local.md)
Test on devnet [references/devnet.md](references/devnet.md)
Test Pinocchio programs cargo test-sbf -p <program-name> (no Anchor required)

Program addresses

These addresses are identical on devnet and mainnet.

Program Address
Light System SySTEM1eSU2p4BGQfQpimFEWWSC1XDFeun3Nqzz3rT7
Compressed Token cTokenmWW8bLPjZEBAUgYy3zKxQZW6VKi7bqNFEVv3m
Account Compression compr6CUsB5m2jS4Y3831ztGSTnDpnKJTKS95d64XVq
Light Registry Lighton6oQpVkeewmo2mcPTQQp7kYHr4fWpAgJyEmDX

Pre-initialized accounts

See [references/accounts.md](references/accounts.md) for state trees, address trees, and protocol PDAs.

See [references/addresses.md](references/addresses.md) for devnet-specific addresses and lookup tables.

SDK references

Package Link
light-program-test docs.rs
@lightprotocol/stateless.js API docs
light-client docs.rs

Security

This skill provides test patterns and configuration references only.

  • Declared dependencies. Devnet testing requires HELIUSAPIKEY (RPC provider key). Localnet testing needs no credentials. In production, load from a secrets manager.
  • Subagent scope. When stuck, the skill asks to spawn a read-only subagent with Read, Glob, Grep scoped to skill references, example repos, and docs.
  • Install source. npx skills add Lightprotocol/skills from Lightprotocol/skills.
  • Audited protocol. Light Protocol smart contracts are independently audited. Reports are published at github.com/Lightprotocol/light-protocol/tree/main/audits.