How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

lightning-factory-explainer - Skill

Name: lightning-factory-explainer
Author: sickn33

Imported from sickn33/agentic-awesome-skills (skills/lightning-factory-explainer/SKILL.md). Install upstream with npx skills add sickn33/agentic-awesome-skills --skill lightning-factory-explainer. Copyright stays with the author.

Use this skill when

Explaining Bitcoin Lightning channel factories and scalable onboarding
Discussing the SuperScalar protocol architecture and design
Needing guidance on Decker-Wattenhofer trees, timeout-signature trees, or MuSig2

Do not use this skill when

The task is unrelated to Bitcoin or Lightning Network scaling
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.

The declared community implementation at 8144225309/SuperScalar returned HTTP 404 on 2026-10-14. Do not treat it as a verified production implementation, funded-mainnet deployment, 400-test suite or audited watchtower. The original SuperScalar proposal is a protocol source, not proof that a similarly named repository implements it correctly.

Purpose

Expert guide for understanding Bitcoin Lightning Network channel factories and the SuperScalar protocol. Covers scalable onboarding, shared UTXOs, Decker-Wattenhofer invalidation trees, timeout-signature trees, Poon-Dryja channels, MuSig2 (BIP-327), and Taproot — all without requiring any soft fork.

Key Topics

Lightning channel factories and multi-party channels
SuperScalar protocol architecture
Decker-Wattenhofer invalidation trees
Timeout-signature trees
MuSig2 key aggregation (BIP-327)
Taproot script trees
LSP (Lightning Service Provider) onboarding patterns
Shared UTXO management

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

Example

User request:

Explain Bitcoin Lightning channel factories and scalable onboarding.

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.

Review evidence

Distinguish proposal properties from a specific implementation revision. Trace funding ownership, required signers, offline/liveness assumptions, timelock ordering, old-state invalidation, recovery artifacts, fee/bump behavior and unilateral exit under congestion. Define what N measures before stating complexity. Verify HTLC/PTLC and watchtower compatibility with actual protocol versions and test vectors; a claim of no consensus change does not establish deployability or safety. Use an isolated regtest fixture; signing, funding or broadcasting with real funds needs separate explicit authorization.

Install lightning-factory-explainer and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "ocm": "1", "id": "sickn33-agentic-awesome-skills-lightning-factory-explainer", "kind": "skill", "name": "lightning-factory-explainer", "description": "Explain Bitcoin Lightning channel factories and the SuperScalar protocol — scalable Lightning onboarding using shared UTXOs, Decker-Wattenhofer trees, timeout-signature trees, MuSig2, and Taproot. No soft fork required.", "publisher": "sickn33", "version": "1.0.0", "capabilities": { "domains": [ "hr", "math" ], "tags": [ "skill-md", "skills-sh" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Explain Bitcoin Lightning channel factories and the SuperScalar protocol — scalable Lightning onboarding using shared UTXOs, Decker-Wattenhofer trees, timeout-signature trees, MuSig2, and Taproot. No soft fork required." ], "primary": false, "metadata": { "source": { "provider": "skills.sh", "repository": "https://github.com/sickn33/agentic-awesome-skills", "path": "skills/lightning-factory-explainer/SKILL.md", "ref": "HEAD", "url": "https://github.com/sickn33/agentic-awesome-skills/blob/HEAD/skills/lightning-factory-explainer/SKILL.md", "key": "sickn33/agentic-awesome-skills/skills/lightning-factory-explainer/SKILL.md" } }, "instructions": "## Use this skill when\n\n- Explaining Bitcoin Lightning channel factories and scalable onboarding\n- Discussing the SuperScalar protocol architecture and design\n- Needing guidance on Decker-Wattenhofer trees, timeout-signature trees, or MuSig2\n\n## Do not use this skill when\n\n- The task is unrelated to Bitcoin or Lightning Network scaling\n- You need a different blockchain or Layer 2 outside this scope\n\n## Instructions\n\n- Clarify goals, constraints, and required inputs.\n- Apply relevant best practices and validate outcomes.\n- Provide actionable steps and verification.\n\nThe declared community imple", "cost": { "context_tokens": 736 } }

lightning-factory-explainer

About

Use this skill when

Do not use this skill when

Instructions

Purpose

Key Topics

References

Example

Limitations

Review evidence

Install lightning-factory-explainer and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Use it

Manifest

Reviews