Add SuperScalar Lightning skills

Add three Bitcoin Lightning Network skills from the SuperScalar project:
- lightning-factory-explainer: Explains channel factory concepts and the SuperScalar protocol
- lightning-channel-factories: Technical reference for channel factories, LSP architectures, and L2 scaling
- lightning-architecture-review: Reviews Lightning protocol designs and Layer 2 scaling tradeoffs

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
8144225309 2026-03-03 16:59:06 -05:00
parent e2323ae22c
commit b901cb5331

View file

@ -52,6 +52,9 @@
- [hashicorp-agent-skills](https://github.com/hashicorp/agent-skills) - HashiCorp-maintained Claude skills for Terraform workflows and infrastructure automation.
- [agnix](https://github.com/avifenesh/agnix) - Linter for AI agent configurations. Validates SKILL.md, CLAUDE.md, hooks, MCP configs, and more with 156 rules, auto-fix, and LSP server for real-time editor diagnostics.
- [email-html-mjml](https://github.com/framix-team/skill-email-html-mjml) - Generate responsive HTML email templates using MJML 4.x — cross-client compatible HTML with compilation, validation, width math, and component architecture.
- [lightning-factory-explainer](https://github.com/8144225309/superscalar-mcp/tree/master/skills/lightning-factory-explainer) - Explain Bitcoin Lightning channel factories and the SuperScalar protocol — scalable Lightning onboarding using shared UTXOs, Decker-Wattenhofer trees, timeout-signature trees, MuSig2, and Taproot.
- [lightning-channel-factories](https://github.com/8144225309/superscalar-mcp/tree/master/skills/lightning-channel-factories) - Technical reference on Lightning Network channel factories, multi-party channels, LSP architectures, and Bitcoin Layer 2 scaling without soft forks.
- [lightning-architecture-review](https://github.com/8144225309/superscalar-mcp/tree/master/skills/lightning-architecture-review) - Review Bitcoin Lightning Network protocol designs, compare channel factory approaches, and analyze Layer 2 scaling tradeoffs.