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".
78
75%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/crypto/cross-chain-bridge-monitor/skills/monitoring-cross-chain-bridges/SKILL.mdQuality
Discovery
100%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 strong skill description that clearly defines its scope around cross-chain bridge monitoring, provides explicit trigger guidance with natural user phrases, and lists concrete capabilities. It follows the recommended pattern of 'what it does' + 'Use when' + trigger phrases, making it easy for Claude to select appropriately from a large skill set.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: monitor TVL, volume, fees, and transaction status across networks. These are distinct, measurable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (monitor cross-chain bridge TVL, volume, fees, transaction status) and 'when' (explicit 'Use when' clause plus 'Trigger with phrases like' providing concrete trigger guidance). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including 'monitor bridges', 'compare bridge fees', 'track bridge tx', 'bridge TVL', 'cross-chain transfer status' — these are phrases users would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific niche focused on cross-chain bridges with distinct terminology (TVL, bridge fees, cross-chain transfer status) that is unlikely to conflict with other crypto or general monitoring skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides a well-structured overview of a cross-chain bridge monitoring CLI tool with clear command syntax and a useful reference table. However, the actual script (bridge_monitor.py) is missing from the bundle, making the commands non-executable. There is notable redundancy between the Commands and Instructions sections, and critical content like error handling and examples is deferred to referenced files that don't exist.
Suggestions
Include the actual bridge_monitor.py script in the bundle or provide the core implementation inline so the commands are truly executable.
Merge the Commands and Instructions sections to eliminate redundancy—keep one authoritative section showing the CLI usage with workflow context.
Add inline validation/feedback steps for transaction tracking (e.g., 'If status shows pending after 30 min, retry with --bridge flag to query protocol-specific explorer').
Fix the misleading inline comment '# 1000: 1 second in ms' on the compare command—clarify this is the transfer amount in token units.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill has some redundancy—the Commands section and Instructions section overlap significantly (both show how to run the same CLI commands). The Supported Bridges table and Supported Chains list add useful reference value but the overall content could be tightened by merging the duplicated command examples. | 2 / 3 |
Actionability | Commands are concrete and copy-paste ready, but the actual bridge_monitor.py script is never provided (no bundle files), making none of this truly executable. The skill describes a CLI tool that doesn't exist in the bundle, so a user cannot actually run any of these commands. The inline comment '# 1000: 1 second in ms' on the compare command is confusing and likely incorrect (it seems to be the transfer amount, not milliseconds). | 2 / 3 |
Workflow Clarity | The Instructions section provides a reasonable sequence (check TVL → compare routes → get details → track tx → export), but there are no validation checkpoints or error recovery steps inline. Error handling is deferred entirely to a referenced file that doesn't exist in the bundle. For operations like tracking bridge transactions, there's no feedback loop for pending/failed states. | 2 / 3 |
Progressive Disclosure | The skill references errors.md and examples.md in appropriate locations, and external resources are well-linked. However, no bundle files are provided, so these references point to nothing. The main file itself contains some content that could be split out (the full command reference) while also deferring critical content (error handling, examples) to non-existent files. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 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 | 9 / 11 Passed | |
- Commit
3a2d27d
- 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.