monitoring-cross-chain-bridges

Monitor cross-chain bridge TVL, volume, fees, and transaction status across networks. Use when researching bridges, comparing routes, or tracking bridge transactions. Trigger with phrases like "monitor bridges", "compare bridge fees", "track bridge tx", "bridge TVL", or "cross-chain transfer status".

Quality

86%

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

Quality

Content

72%Weight 40%Scale 1-3

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

The body is actionable and well-structured with real bundled scripts and one-level-deep references, but it duplicates command examples across the Commands and Instructions sections and presents a loose list rather than a validated workflow.

Suggestions

Collapse the duplicate command listings: keep concrete examples in Commands and have Instructions reference them or show only the distinct sequencing rationale, instead of repeating tvl/compare/detail/tx verbatim.

Add a short validation checkpoint to the transaction-tracking flow (e.g. confirm source and destination confirmation status before declaring a transfer complete).

Remove or correct the misleading inline comment `# 1000: 1 second in ms` on the compare example, which conflicts with the actual `--amount 1000` (USD) semantics described elsewhere.

Dimension	Reasoning	Score
Conciseness	Mostly efficient, but the Commands section and the Instructions section repeat the same operations (tvl, compare, detail, tx) with near-identical invocations, wasting tokens on duplicated guidance.	2 / 3
Actionability	Every section gives concrete, copy-paste-ready commands backed by real bundled scripts (e.g. `python bridge_monitor.py compare --source ethereum --dest arbitrum --amount 1000 --token USDC`).	3 / 3
Workflow Clarity	The numbered Instructions are a menu of independent read-only commands rather than a dependent sequence, and no validation/checkpoints are described even where useful (e.g. confirming a tracked tx resolved).	2 / 3
Progressive Disclosure	Overview stays lean and points one level deep to real bundled references (`references/errors.md`, `references/examples.md`) and scripts, with no deeply nested reference chains.	3 / 3
	Total	10 / 12 Passed

Description

100%Weight 40%Scale 1-3

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 strong description: it states concrete capabilities, gives natural trigger phrases, answers both what and when, and occupies a clear niche. Written in third person with no fluff.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete monitoring actions/objects — "bridge TVL, volume, fees, and transaction status" — matching the score-3 anchor for multiple specific concrete actions.	3 / 3
Completeness	Explicitly answers both what ("Monitor cross-chain bridge TVL, volume, fees, and transaction status") and when ("Use when researching bridges, comparing routes, or tracking bridge transactions") plus explicit trigger phrases.	3 / 3
Trigger Term Quality	Provides natural phrases users would say ("monitor bridges", "compare bridge fees", "track bridge tx", "bridge TVL", "cross-chain transfer status"), giving good coverage.	3 / 3
Distinctiveness Conflict Risk	Cross-chain bridges is a clear niche with distinct triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/crypto/cross-chain-bridge-monitor/skills/monitoring-cross-chain-bridges/SKILL.md
Commit: 4c47e33

Reviewed: about 21 hours 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.