CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

61%

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 ./.agents/skills/lightning-architecture-review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

40%Weight 40%Scale 1-5

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

The body is well-sectioned and free of concept over-explanation, but it delivers almost no actionable review guidance — the Instructions are generic boilerplate, and the skill's actual scope is repeated across three redundant sections instead of concrete methodology. It reads as a scope declaration with links rather than an expert-reviewer playbook.

Suggestions

Replace the vague Instructions with a concrete review procedure, e.g., a numbered workflow: enumerate the design's channel construction, assess trust model per role, compute on-chain footprint (UTXO count, exit cost/complexity), check HTLC/PTLC compatibility, then verify liveness and watchtower assumptions.

Add explicit comparison criteria for channel factory approaches (e.g., a table of trust model, on-chain footprint, exit complexity, consensus requirements, watchtower support) so reviews have an executable rubric.

Merge the "Use this skill when", "Purpose", and "Key Topics" sections into one concise scope statement to eliminate triple restatement and free tokens for the missing methodology.

DimensionReasoningScore

Conciseness

The scope is restated three times — in "Use this skill when", nearly verbatim in "Purpose" ("Compares channel factory approaches, analyzes Layer 2 scaling tradeoffs..."), and again as the "Key Topics" list — which is padded duplication. There is no over-explanation of known concepts, so it sits at "mostly efficient but could be tightened" rather than the noticeably verbose anchor at 2.

3 / 5

Actionability

The Instructions are pure abstraction: "Clarify goals, constraints, and required inputs. Apply relevant best practices and validate outcomes. Provide actionable steps and verification." — no review methodology, comparison criteria, rubric, or checklist. Only the SuperScalar paragraph ("O(log N) unilateral exit, and watchtower breach detection") offers concrete substance, matching the minimal-guidance anchor at 2.

2 / 5

Workflow Clarity

The three instruction bullets form a rough pseudo-sequence (clarify → apply → provide) but the steps are poorly defined and there are no validation checkpoints or feedback loops for the review process, matching "rough sequence present but many gaps; validation absent".

2 / 5

Progressive Disclosure

No bundle files exist, and the body is under 50 lines with clear section headers and one-level-deep external links, which per the simple-skill guidance can support a high score. The redundant scattering of scope across three sections is a minor organization gap, keeping it at 4 rather than 5.

4 / 5

Total

11

/

20

Passed

Description

66%Weight 40%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.

A well-scoped, third-person description with concrete domain actions and strong natural trigger terms for the Lightning/factory-design niche. Its main weakness is the absence of any explicit "Use when..." trigger clause, and the generic review/compare/analyze verbs plus the broad "Layer 2 scaling" phrasing leave minor specificity and overlap gaps.

Suggestions

Add an explicit trigger clause, e.g. "Use when reviewing Lightning Network protocol proposals, comparing channel factory or payment-channel designs, or evaluating Layer 2 scaling tradeoffs."

Include natural synonyms users might say, such as "LN", "payment channels", or "Lightning factories", to broaden trigger term coverage.

Replace one generic verb with a more concrete action (e.g., "evaluate unilateral-exit cost and watchtower compatibility of factory designs") to sharpen capability specificity.

DimensionReasoningScore

Specificity

Lists several concrete, domain-anchored actions ("Review Bitcoin Lightning Network protocol designs, compare channel factory approaches, and analyze Layer 2 scaling tradeoffs") plus a broad topic list (trust models, on-chain footprint, HTLC/PTLC compatibility, watchtower support). The action verbs themselves (review/compare/analyze) are generic, leaving minor gaps versus the comprehensive anchor at 5.

4 / 5

Completeness

The "what" is clearly stated (review/compare/analyze Lightning protocol designs with enumerated coverage areas), but there is no "Use when..." clause or equivalent explicit trigger guidance in the description, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Includes strong natural terms a user in this domain would say: "Bitcoin Lightning Network", "channel factory", "Layer 2 scaling", "HTLC/PTLC", "watchtower". A few natural synonyms (e.g., "LN", "payment channels") are missing, so it falls just short of the comprehensive anchor at 5.

4 / 5

Distinctiveness Conflict Risk

"Bitcoin Lightning Network protocol designs" and "channel factory" define a clear niche that most skills would not conflict with. "Layer 2 scaling tradeoffs" is broader and leaves minor overlap risk with general blockchain/Layer 2 review skills, keeping it just below the minimal-conflict anchor at 5.

4 / 5

Total

15

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

BigSimmo/Communication

Path

.agents/skills/lightning-architecture-review/SKILL.md

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.