Data Streaming

Stream Light Protocol account state transitions via Laserstream gRPC.

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
2. Identify references and skills
• Match task to domain references below
• Locate relevant documentation and examples
3. 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
4. Execute
• Use Task tool with subagents for parallel research
• Subagents load skills via Skill tool
• Track progress with TodoWrite
5. When stuck: spawn subagent with Read, Glob, Grep, DeepWiki MCP access and load skills/ask-mcp

When NOT to use

For simple account lookups, call get_account_interface from light-client. It races hot and cold lookups automatically.

This skill is for continuous data pipelines: aggregators, market makers, and indexers that need real-time state change notifications rather than point queries.

Domain references

Account type decision

Program addresses

External references

SDK references

Security

This skill does not pull, store, or transmit external secrets. It provides code patterns, documentation references, and development guidance only.

• No credentials consumed. The skill requires no API keys, private keys, or signing secrets. env: [] is declared explicitly.
• User-provided configuration. RPC endpoints, wallet keypairs, and authentication tokens (Privy, wallet adapters) are configured in the user's own application code — the skill only demonstrates how to use them.
• API keys. Reference code uses HELIUS_API_KEY as a placeholder. For production, set your RPC provider key as an environment variable.
• Subagent scope. This skill may spawn read-only subagents that use Read, Glob, and Grep to search the local repository. Restrict the working directory to your project.
• Install source. npx skills add Lightprotocol/skills installs from the public GitHub repository (Lightprotocol/skills). Verify the source before running.
• Audited protocol. Light Protocol smart contracts are independently audited. Reports are published at github.com/Lightprotocol/light-protocol/tree/main/audits.