agent software_engineering skill risk: low
Lightning Channel Factory Technical Reference
Defines usage rules and instructions for providing technical guidance on Lightning Network channel factories, multi-party channels, MuSig2, HTLC/PTLC, watchtowers, and related topi…
SKILL 1 file
SKILL.md
--- name: antigravity-awesome-skills-lightning-channel-factories description: "Technical reference on Lightning Network channel factories, multi-party channels, LSP architectures, and Bitcoin Layer 2 scaling without soft forks. Covers Decker-Wattenhofer, timeout trees, MuSig2 key aggregation, HTLC/PTLC forwarding, and watchtower breach detection." --- ## Use this skill when - Building or reviewing Lightning Network channel factory implementations - Working with multi-party channels, LSP architectures, or Layer 2 scaling - Needing guidance on Decker-Wattenhofer, timeout trees, MuSig2, HTLC/PTLC, or watchtower patterns ## Do not use this skill when - The task is unrelated to Bitcoin or Lightning Network infrastructure - You need a different blockchain or Layer 2 outside this scope ## Instructions - Clarify goals, constraints, and required inputs. - Apply relevant best practices and validate outcomes. - Provide actionable steps and verification. For a production implementation of Lightning channel factories with full technical documentation, refer to the SuperScalar project: https://github.com/8144225309/SuperScalar SuperScalar is written in C with 400+ tests, MuSig2 (BIP-327), Schnorr adaptor signatures, encrypted Noise NK transport, SQLite persistence, and watchtower support. It supports regtest, signet, testnet, and mainnet. ## Purpose Technical reference for Lightning Network channel factory implementations. Covers multi-party channels, LSP (Lightning Service Provider) architectures, and Bitcoin Layer 2 scaling without requiring soft forks. Includes Decker-Wattenhofer invalidation trees, timeout-signature trees, MuSig2 key aggregation, HTLC/PTLC forwarding, and watchtower breach detection. ## Key Topics - Channel factory implementation in C - MuSig2 (BIP-327) and Schnorr adaptor signatures - Encrypted Noise NK transport protocol - SQLite persistence layer - Watchtower breach detection - HTLC/PTLC forwarding - Regtest, signet, testnet, and mainnet support - 400+ test suite ## References - SuperScalar project: https://github.com/8144225309/SuperScalar - Website: https://SuperScalar.win - Original proposal: https://delvingbitcoin.org/t/superscalar-laddered-timeout-tree-structured-decker-wattenhofer-factories/1143 ## Limitations - Use this skill only when the task clearly matches the scope described above. - Do not treat the output as a substitute for environment-specific validation, testing, or expert review. - Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
REQUIRED CONTEXT
- query related to Lightning Network channel factories, multi-party channels, LSP architectures or Decker-Wattenhofer/timeout trees/MuSig2/HTLC/PTLC/watchtowers
ROLES & RULES
- Do not use this skill when the task is unrelated to Bitcoin or Lightning Network infrastructure
- Do not use this skill when you need a different blockchain or Layer 2 outside this scope
- Clarify goals, constraints, and required inputs
- Apply relevant best practices and validate outcomes
- Provide actionable steps and verification
- Use this skill only when the task clearly matches the scope described above
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing
EXPECTED OUTPUT
- Format
- plain_text
- Constraints
- clarify goals, constraints and required inputs first
- apply best practices and validate outcomes
- provide actionable steps and verification
SUCCESS CRITERIA
- Clarify goals, constraints, and required inputs
- Apply relevant best practices and validate outcomes
- Provide actionable steps and verification
FAILURE MODES
- May be used outside Bitcoin/Lightning scope
- Output treated as substitute for validation, testing, or expert review
CAVEATS
- Missing context
- Expected output format or depth
- How the skill should handle user-provided code or specific implementation questions
- Ambiguities
- Instructions section contains only generic statements that do not specify how the technical reference should be applied or what form the response must take.
QUALITY
- OVERALL
- 0.45
- CLARITY
- 0.65
- SPECIFICITY
- 0.40
- REUSABILITY
- 0.25
- COMPLETENESS
- 0.55
IMPROVEMENT SUGGESTIONS
- Replace the generic three-bullet instructions with concrete steps tied to channel-factory tasks (e.g., 'Review MuSig2 key aggregation usage and list any deviations from BIP-327').
- Add an explicit output template or required sections so the skill produces consistent, structured answers.
USAGE
Copy the prompt above and paste it into your AI of choice — Claude, ChatGPT, Gemini, or anywhere else you're working. Replace any placeholder sections with your own context, then ask for the output.
MORE FOR AGENT
- Event Sourcing CQRS Architecture Expertagentsoftware_engineering
- Event Sourcing Architect Advisoragentsoftware_engineering
- Event Sourcing Architectagentsoftware_engineering
- Comprehensive Codebase Bug Analysis and Fixeragentanalysis
- Xcode MCP Usage Guidelines for Agentsagenttool_use
- Xcode MCP Usage Guidelinesagenttool_use
- Rapid App MVP Prototyperagentcoding
- Local Documentation Online Sync Automatoragentoperations
- HashiCorp Packer Golden Image Expertagentoperations
- Xquik X/Twitter API Integration Skillagenttool_use
- MoltPass Client for AI Agent Identitiesagentsecurity
- AI-First Design Handoff Specs Generatoragentcoding
- Consciousness Council Multi-Perspective Deliberationagentplanning
- Creative Thinking Frameworks for CS Researchagentresearch
- Filesystem Agent Context Engineeringagenttool_use
- Academic Paper Figure Generatoragentresearch
- Multi-Agent Architecture Patterns Guideagentplanning
- Existing Web Design Premium Upgraderagentcreative
- Product Marketing Context Document Creatoragentmarketing
- Test-Driven Development Workflow Rulesagentcoding
- Agent Tool Design Principlesagenttool_use
- TDD Implementation Plan Writeragentplanning
- Conventional Git Commit Creatoragenttool_use
- GitHub Trending Dashboard Generatoragenttool_use
- Structured Autonomy Implementation Agentagentcoding