lcp-protocol-spec

Update and validate TLV definitions and message formats in LCP protocol docs.

2|Updated Dec 30, 2025

Search Tags:#documentation #protocol #lcp #go-lcpd #TLV #BOLT

Ready to run

npx skills add https://github.com/YusukeShimizu/lightning-compute-protocol --skill lcp-protocol-spec

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: lcp-protocol-spec
Source: https://github.com/YusukeShimizu/lightning-compute-protocol/tree/main/.codex/skills/lcp-protocol-spec
Command: npx skills add https://github.com/YusukeShimizu/lightning-compute-protocol --skill lcp-protocol-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Develop and maintain rigorous Lightning Compute Protocol (LCP) specifications, ensuring consistency and alignment with Bolt-style documentation. This Skill guides editors to refine protocol docs under docs/protocol/ and coordinate with related implementation references.

Core Features & Use Cases

Update and validate TLV definitions, message formats, and state flows in docs/protocol/protocol.md (and protocol-ja.md when applicable).
Align documentation with the go-lcpd implementation and maintain cross-reference accuracy.
Enforce Bolt-style formatting, TLV semantics, and non-modification of upstream Bolt behavior.

Quick Start

Update docs/protocol/protocol.md to reflect the latest LCP v0.2 definitions; verify TLV tables and state diagrams; then submit a PR following project guidelines.

Frequently Asked Questions about lcp-protocol-spec

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

FAQPage Schema

How do I format LCP protocol documentation to align with Bolt specifications?▼

To format LCP protocol documentation, update docs/protocol/protocol.md by applying Bolt-style formatting, validating TLV definitions, and ensuring message formats and state flows match upstream Bolt behavior without modification.

What are TLV definitions and how do they work in Lightning Compute Protocol specs?▼

TLV definitions in Lightning Compute Protocol specs are Type-Length-Value encoded data structures that define message formats. They ensure compatibility between protocol documentation and the go-lcpd implementation by enforcing consistent semantic rules.

How to update LCP protocol specs and cross-reference with the go-lcpd implementation?▼

Update LCP protocol specs by editing docs/protocol/protocol.md to reflect the latest definitions, then verify that TLV tables and state diagrams maintain accurate cross-references with the go-lcpd implementation before submitting a pull request.

Does this Skill support maintaining localized protocol-ja.md documentation alongside the main protocol specs?▼

Yes, the Skill supports maintaining localized protocol-ja.md documentation. It guides editors to update and validate TLV definitions, message formats, and state flows in both protocol.md and protocol-ja.md when applicable.

What are the limitations when modifying upstream Bolt behavior in LCP protocol docs?▼

The primary limitation is that upstream Bolt behavior must remain unchanged. The Skill enforces non-modification of upstream Bolt logic while allowing edits to TLV semantics, formatting, and LCP-specific state flow documentation.

Can I use this Skill to validate state diagrams and message formats for LCP v0.2?▼

Yes, you can use this Skill to validate state diagrams and message formats for LCP v0.2. It guides editors to verify TLV tables and update docs/protocol/protocol.md to reflect the latest LCP v0.2 definitions accurately.