lightning-architecture-review

Review Bitcoin Lightning Network protocol designs, compare channel factory approaches, and analyze Layer 2 scaling tradeoffs. Covers trust models, on-chain footprint, consensus requirements, HTLC/PTLC compatibility, liveness, and watchtower support.

Quality

48%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/lightning-architecture-review/SKILL.md

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 masquerading as actionable guidance. It identifies a valid domain (Lightning Network protocol review) but provides no concrete methodology, evaluation frameworks, comparison criteria, or worked examples. The 'Instructions' section is entirely generic boilerplate that could apply to any analytical task.

Suggestions

Add a concrete evaluation framework with specific criteria (e.g., a comparison table template covering trust model, on-chain footprint, consensus requirements, liveness, watchtower support) that Claude should fill out when reviewing a protocol.

Provide at least one worked example showing how to analyze a specific channel factory design against the evaluation criteria, with specific questions to ask and tradeoffs to identify.

Replace the generic 'Instructions' bullets with a specific workflow: e.g., 1) Identify the construction's building blocks, 2) Map trust assumptions, 3) Calculate on-chain costs for cooperative/unilateral cases, 4) Assess liveness requirements, 5) Check HTLC/PTLC routing compatibility.

Add concrete comparison anchors (e.g., how SuperScalar compares to Ark, eltoo-based factories, or basic Poon-Dryja) so Claude has reference points for evaluating new proposals.

Dimension	Reasoning	Score
Conciseness	The skill has some unnecessary sections like 'Purpose' which repeats the description, and 'Key Topics' which is just a list of keywords that don't add actionable value. The 'Instructions' section is extremely generic. However, it's not excessively verbose overall.	3 / 5
Actionability	The skill provides no concrete guidance on how to actually review protocols, compare channel factories, or analyze tradeoffs. The 'Instructions' section is entirely generic ('Clarify goals, constraints, and required inputs. Apply relevant best practices.') with no specific frameworks, evaluation criteria, comparison matrices, or worked examples.	1 / 5
Workflow Clarity	There is no meaningful workflow defined. The three bullet points in 'Instructions' are so generic they could apply to any task. There's no sequence for how to conduct a protocol review, no validation checkpoints, and no structured comparison methodology.	1 / 5
Progressive Disclosure	The skill has some structure with sections (Use when, Instructions, Purpose, Key Topics, References) and provides external links. However, there are no bundle files to support deeper content, and the references section is just links without context on what each contains or when to use them.	3 / 5
	Total	8 / 20 Passed

Description

75%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.

This is a technically rich and specific description that clearly communicates what the skill does across multiple concrete dimensions of Lightning Network protocol analysis. Its main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know precisely when to select this skill. The trigger terms are strong but could include a few more natural synonyms.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Lightning Network design, channel factories, Layer 2 Bitcoin scaling, or payment channel tradeoffs.'

Include common synonyms and abbreviations users might use, such as 'LN', 'L2', 'payment channels', 'off-chain', or 'Bitcoin scaling solutions'.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: reviewing protocol designs, comparing channel factory approaches, analyzing Layer 2 scaling tradeoffs. Further enumerates specific dimensions of analysis: trust models, on-chain footprint, consensus requirements, HTLC/PTLC compatibility, liveness, and watchtower support.	5 / 5
Completeness	The 'what' is clearly and thoroughly described with specific actions and coverage areas. However, there is no explicit 'when' clause (e.g., 'Use when...') telling Claude when to select this skill, which caps this dimension at 3 per the rubric guidelines.	3 / 5
Trigger Term Quality	Includes strong domain-specific trigger terms like 'Bitcoin', 'Lightning Network', 'channel factory', 'Layer 2', 'HTLC', 'PTLC', 'watchtower'. Missing some natural user phrases like 'LN', 'L2 scaling', 'payment channels', or 'off-chain transactions' that users might naturally say.	4 / 5
Distinctiveness Conflict Risk	Extremely niche and well-defined domain — Bitcoin Lightning Network protocol design review with specific technical dimensions. Very unlikely to conflict with other skills given the highly specialized terminology and scope.	5 / 5
	Total	17 / 20 Passed

Validation

90%

Warnings & errors only

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

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
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
Path: skills/lightning-architecture-review/SKILL.md
Commit: 57c135b

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.