CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

52

Quality

57%

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-claude/skills/lightning-architecture-review/SKILL.md

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

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-structured with clear sections and references, but its instructional content is generic and non-actionable, with no concrete review methodology or validation steps. Significant redundancy between the description, Purpose, and Key Topics sections wastes tokens.

Suggestions

Replace the generic Instructions with a concrete review methodology: a sequenced checklist for evaluating Lightning designs (e.g., enumerate trust assumptions, compute on-chain footprint, check HTLC/PTLC compatibility, verify liveness/watchtower support) with explicit validation steps.

Remove the redundant "Purpose" and "Key Topics" sections, which restate the frontmatter description, to improve conciseness.

Trim the promotional SuperScalar architectural paragraph to a one-line reference and fold the three links into a single References section.

DimensionReasoningScore

Conciseness

Mostly readable but carries redundant sections: "Purpose" and "Key Topics" restate the frontmatter description, and the SuperScalar paragraph adds promotional architectural detail that could be trimmed, fitting the "mostly efficient but could be tightened" anchor.

3 / 5

Actionability

Instructions are generic boilerplate ("Apply relevant best practices and validate outcomes", "Provide actionable steps and verification") with no concrete review methodology, checklist, or commands; the only specific item is an external URL, matching the "minimal concrete guidance" anchor.

2 / 5

Workflow Clarity

Only a rough implicit sequence (clarify → apply/validate → provide) exists across three vague bullets with no defined steps, no validation methodology, and no checkpoints, matching the "rough sequence, poorly defined, validation absent" anchor.

2 / 5

Progressive Disclosure

Well-organized into clear sections (Use when, Do not use when, Instructions, Purpose, Key Topics, References) with clearly signaled references; minor gaps from redundant Purpose/Key Topics content and external-only (non-bundled) references keep it just below 5.

4 / 5

Total

11

/

20

Passed

Description

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

The description is specific and well-scoped to a distinct niche, with strong natural trigger terms. Its main weakness is the absence of an explicit "Use when..." clause, which caps completeness at 3.

Suggestions

Add an explicit "Use when..." trigger clause naming the natural phrases users would say (e.g., "Use when reviewing Lightning Network designs, comparing channel factories, or analyzing Layer 2 scaling tradeoffs").

Include common synonyms such as "payment channels" or "Lightning channels" alongside "channel factory" to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ("Review", "compare channel factory approaches", "analyze Layer 2 scaling tradeoffs") plus comprehensive topic coverage (trust models, on-chain footprint, consensus requirements, HTLC/PTLC, liveness, watchtower), matching the comprehensive-coverage anchor.

5 / 5

Completeness

Clearly states the "what" but contains no "Use when..." trigger clause; per the guidelines a missing explicit trigger caps completeness at 3, matching the "clear what, missing when" anchor.

3 / 5

Trigger Term Quality

Strong natural terms a user would say ("Bitcoin Lightning Network", "channel factory", "Layer 2 scaling", "watchtower"), but common synonyms like "payment channels" or "Lightning channels" are absent, so it is good but not comprehensive.

4 / 5

Distinctiveness Conflict Risk

The Bitcoin Lightning Network protocol-design niche is highly specific with distinct triggers and minimal overlap with other skills, matching the clear-niche anchor.

5 / 5

Total

17

/

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.

Validation15 / 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
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.