How do I install the 2036 Errors 74fa27ba skill?

Run npx skillmds@latest add tools-only/2036-errors-74fa27ba in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the 2036 Errors 74fa27ba skill do?

Error Handling Reference It is listed under Research & Search on SkillMD.

Is 2036 Errors 74fa27ba safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with 2036 Errors 74fa27ba?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is 2036 Errors 74fa27ba free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published 2036 Errors 74fa27ba?

tools-only (@tools-only) published this skill. Their other Agent Skills are listed on their SkillMD profile.

2036 Errors 74fa27ba by tools-only — Agent Skill

Name: 2036 Errors 74fa27ba
Author: tools-only

File contents

Error Handling Reference

API Errors

DefiLlama API Unavailable

Error: Connection refused / timeout

Cause: DefiLlama bridges API is down or rate limited. Solution:

Wait and retry with exponential backoff
Use cached data if available
Check DefiLlama status page

Bridge API Unavailable

Error: Protocol API not responding

Cause: Specific bridge API (Wormhole, LayerZero, etc.) is down. Solution:

Try alternative tracking method (on-chain verification)
Wait and retry
Check bridge status page

Rate Limited

Error: 429 Too Many Requests

Cause: Exceeded API rate limits. Solution:

Reduce request frequency
Use caching more aggressively
Spread requests over time

Transaction Tracking Errors

Transaction Not Found

Transaction not found in any bridge

Cause: TX hash doesn't match any known bridge. Solution:

Verify the transaction hash is correct
Specify the bridge with --bridge
Specify source chain with --chain
Transaction may be too old

Wrong Bridge Specified

Bridge not found: xyz

Cause: Bridge name not recognized. Solution:

Use python bridge_monitor.py protocols to see supported bridges
Check spelling (case-insensitive)
Use bridge ID instead of name

Pending Too Long

Transaction still pending after 60 minutes

Cause: Bridge congestion, low gas, or failure. Solution:

Check source chain for confirmation
Verify transaction wasn't reverted
Contact bridge support if stuck

Chain Errors

Unsupported Chain

Error: No RPC URL for chain: xyz

Cause: Chain not in supported list. Solution:

Use python bridge_monitor.py chains to see supported chains
Set custom RPC via environment variable: {CHAIN}_RPC_URL
Check chain name spelling

RPC Connection Failed

Error: RPC connection timeout

Cause: RPC endpoint is overloaded or down. Solution:

Set custom RPC URL via environment variable
Try a different RPC provider
Check if chain is experiencing issues

Comparison Errors

Route Not Supported

No bridges support ethereum → xyz

Cause: Destination chain not supported by any bridge. Solution:

Verify destination chain exists
Check individual bridge support with python bridge_monitor.py detail --bridge
Consider multi-hop route

No Fee Estimates

No fee estimates available

Cause: Couldn't get fee data from any bridge. Solution:

Check if bridges are operational
Verify chains are supported
Try with a different token

Common Error Patterns

Error	Likely Cause	Quick Fix
Connection timeout	API overload	Retry with backoff
429 Too Many Requests	Rate limited	Wait and retry
Bridge not found	Wrong name	Check `protocols` command
TX not found	Wrong hash/bridge	Verify hash, try all bridges
Chain not supported	Typo or unsupported	Check `chains` command
No estimates	Route not supported	Check bridge details

Fallback Behavior

The system uses this fallback chain:

Protocol API - Bridge-specific API
DefiLlama API - Aggregated data
On-Chain RPC - Direct blockchain verification
Cached Data - Last known good data
Error - If all fail

Debug Mode

Enable verbose output for troubleshooting:

python bridge_monitor.py --verbose tvl

This shows:

API requests being made
Response times
Cache hits/misses
Error details

---name: 2036-errors-74fa27badescription: Error Handling Reference---# Error Handling Reference## API Errors### DefiLlama API Unavailable```Error: Connection refused / timeout```**Cause:** DefiLlama bridges API is down or rate limited.**Solution:**1. Wait and retry with exponential backoff2. Use cached data if available3. Check DefiLlama status page### Bridge API Unavailable```Error: Protocol API not responding```**Cause:** Specific bridge API (Wormhole, LayerZero, etc.) is down.**Solution:**1. Try alternative tracking method (on-chain verification)2. Wait and retry3. Check bridge status page### Rate Limited```Error: 429 Too Many Requests```**Cause:** Exceeded API rate limits.**Solution:**1. Reduce request frequency2. Use caching more aggressively3. Spread requests over time## Transaction Tracking Errors### Transaction Not Found```Transaction not found in any bridge```**Cause:** TX hash doesn't match any known bridge.**Solution:**1. Verify the transaction hash is correct2. Specify the bridge with `--bridge`3. Specify source chain with `--chain`4. Transaction may be too old### Wrong Bridge Specified```Bridge not found: xyz```**Cause:** Bridge name not recognized.**Solution:**1. Use `python bridge_monitor.py protocols` to see supported bridges2. Check spelling (case-insensitive)3. Use bridge ID instead of name### Pending Too Long```Transaction still pending after 60 minutes```**Cause:** Bridge congestion, low gas, or failure.**Solution:**1. Check source chain for confirmation2. Verify transaction wasn't reverted3. Contact bridge support if stuck## Chain Errors### Unsupported Chain```Error: No RPC URL for chain: xyz```**Cause:** Chain not in supported list.**Solution:**1. Use `python bridge_monitor.py chains` to see supported chains2. Set custom RPC via environment variable: `{CHAIN}_RPC_URL`3. Check chain name spelling### RPC Connection Failed```Error: RPC connection timeout```**Cause:** RPC endpoint is overloaded or down.**Solution:**1. Set custom RPC URL via environment variable2. Try a different RPC provider3. Check if chain is experiencing issues## Comparison Errors### Route Not Supported```No bridges support ethereum → xyz```**Cause:** Destination chain not supported by any bridge.**Solution:**1. Verify destination chain exists2. Check individual bridge support with `python bridge_monitor.py detail --bridge`3. Consider multi-hop route### No Fee Estimates```No fee estimates available```**Cause:** Couldn't get fee data from any bridge.**Solution:**1. Check if bridges are operational2. Verify chains are supported3. Try with a different token## Common Error Patterns| Error | Likely Cause | Quick Fix ||-------|--------------|-----------|| Connection timeout | API overload | Retry with backoff || 429 Too Many Requests | Rate limited | Wait and retry || Bridge not found | Wrong name | Check `protocols` command || TX not found | Wrong hash/bridge | Verify hash, try all bridges || Chain not supported | Typo or unsupported | Check `chains` command || No estimates | Route not supported | Check bridge details |## Fallback BehaviorThe system uses this fallback chain:1. **Protocol API** - Bridge-specific API2. **DefiLlama API** - Aggregated data3. **On-Chain RPC** - Direct blockchain verification4. **Cached Data** - Last known good data5. **Error** - If all fail## Debug ModeEnable verbose output for troubleshooting:```bashpython bridge_monitor.py --verbose tvl```This shows:- API requests being made- Response times- Cache hits/misses- Error details

Frequently asked questions

2036 Errors 74fa27ba