CtrlK
BlogDocsLog inGet started
Tessl Logo

lightning-channel-factories

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.

44

Quality

46%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/lightning-channel-factories/SKILL.md

The canonical home for this skill is lightning-channel-factories in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

22%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill is essentially a topic description and link collection rather than an actionable skill. It repeats the same information across multiple sections (description, purpose, key topics) without providing any concrete guidance, code examples, commands, or workflows. The 'Instructions' section is entirely generic and could apply to any skill, making it useless for teaching Claude how to work with Lightning channel factories.

Suggestions

Replace the generic 'Instructions' section with concrete, actionable guidance — e.g., specific code patterns for MuSig2 key aggregation, example commands for running the test suite, or step-by-step workflows for setting up a channel factory on regtest.

Add at least one concrete workflow with validation steps, such as: clone repo → build → run tests → deploy on regtest → verify channel creation, with explicit checkpoints.

Eliminate redundancy between the description, Purpose section, and Key Topics — consolidate into a single concise overview and use the freed space for actual technical content.

Include executable code examples or command-line snippets demonstrating key operations (e.g., creating a channel factory, detecting a breach with the watchtower, forwarding an HTLC).

DimensionReasoningScore

Conciseness

The skill repeats itself significantly — the purpose, key topics, and description all restate the same information (MuSig2, watchtower, HTLC/PTLC, etc.) multiple times. The 'Instructions' section is generic filler ('Clarify goals, constraints, and required inputs') that adds no value. However, it's not excessively verbose in explaining concepts Claude already knows.

3 / 5

Actionability

The skill provides no concrete code, commands, examples, or executable guidance whatsoever. The 'Instructions' section contains only vague platitudes ('Apply relevant best practices and validate outcomes'). It essentially just points to an external GitHub repository without teaching Claude how to do anything specific.

1 / 5

Workflow Clarity

There is no workflow, no sequence of steps, no validation checkpoints, and no concrete process described. The three bullet points under 'Instructions' are generic and content-free. For a skill covering complex multi-step processes like channel factory implementation, this is entirely inadequate.

1 / 5

Progressive Disclosure

The skill has some structural organization with sections (Use/Don't use, Instructions, Purpose, Key Topics, References) and provides external links. However, there are no bundle files to reference, the content is repetitive across sections rather than progressively disclosing detail, and the references section is just links without context on what each contains.

3 / 5

Total

8

/

20

Passed

Description

70%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description excels at identifying a clear technical niche with specific protocol names and concepts, making it highly distinctive. However, it reads as a topic list rather than describing concrete actions, and critically lacks a 'Use when...' clause that would help Claude know when to select this skill over others.

Suggestions

Add a 'Use when...' clause with trigger phrases like 'Use when the user asks about Lightning Network scaling, channel factories, multi-party payment channels, or Bitcoin Layer 2 solutions without soft forks.'

Reframe as actions rather than topics, e.g., 'Explains channel factory construction, analyzes LSP architectures, describes breach detection mechanisms' to clarify what the skill does rather than what it covers.

DimensionReasoningScore

Specificity

Lists several specific technical topics (channel factories, multi-party channels, LSP architectures, Decker-Wattenhofer, timeout trees, MuSig2, HTLC/PTLC forwarding, watchtower breach detection) but these are more topic areas than concrete actions the skill performs.

4 / 5

Completeness

Clearly answers 'what' (technical reference covering specific Lightning/L2 topics) but has no explicit 'when' clause or trigger guidance. The absence of a 'Use when...' clause caps this at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

Contains many relevant technical keywords users would search for (Lightning Network, channel factories, MuSig2, HTLC, PTLC, watchtower, Layer 2, soft forks, LSP), though it's missing some natural user phrases like 'payment channels', 'off-chain', or 'Bitcoin scaling solutions'.

4 / 5

Distinctiveness Conflict Risk

Highly specific niche covering Lightning Network channel factories and Bitcoin L2 scaling without soft forks. The combination of specific protocols (Decker-Wattenhofer, timeout trees, MuSig2) makes this extremely unlikely to conflict with other skills.

5 / 5

Total

16

/

20

Passed

Validation

90%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.