BytesAgain is a curated directory of 60,000+ AI agent skills from ClawHub, GitHub, LobeHub, and Dify. Search skills by keyword in 7 languages, browse by role (developer, creator, trader, marketer) or by use case.

How do I find AI skills on BytesAgain?

Use the search bar on BytesAgain.com to search by keyword in 7 languages. You can also browse by role (developer, creator, trader, marketer) or by use case. Each skill shows install instructions for Claude, Cursor, OpenClaw, Continue, and more.

Yes, BytesAgain is completely free. No registration required for searching skills. The MCP API is also free with rate limits.

Does BytesAgain have an API for AI agents?

Yes! BytesAgain provides a free MCP SSE endpoint at /api/mcp/sse for AI agents, plus a REST API at /api/mcp?action=search&q= . No authentication needed.

Can I request a new AI skill on BytesAgain?

Yes! Visit the Requests page on BytesAgain.com to submit a skill request. Your request will be visible to the community and notified to the site admin.

🦀 ClawHub

Ospf Analysis

by @vahagn-madatyan

OSPF protocol analysis with adjacency diagnosis, area design validation, LSA interpretation, and SPF convergence assessment. Multi-vendor coverage for Cisco...

Versionv1.0.0

#legal

⚡ When to Use

Trigger	Action
- Unexpected route changes or missing routes in the OSPF domain
- Area design review — backbone connectivity, stub/NSSA configuration audit
- SPF algorithm running too frequently (unstable link, flapping interface)
- Post-change verification of OSPF configuration (new interfaces, area changes,
redistribution updates)
- LSDB growing unexpectedly or LSA age anomalies indicating flooding issues
- Convergence too slow after planned maintenance or unplanned link failure

⚙️ Configuration

SSH or console access to the router (read-only privilege sufficient)

OSPF process running on the device with at least one active interface

Knowledge of expected area topology: which routers are ABRs/ASBRs, which

interfaces belong to which areas, expected neighbor relationships

Awareness of configured authentication type per area (none, simple, MD5)

Router IDs known or deterministic (explicit configuration preferred over

auto-selection from loopback/interface addresses)

📋 Tips & Best Practices

MTU Mismatch (ExStart Stuck)

The most common OSPF adjacency failure. Neighbors reach ExStart but cannot proceed because DBD packets exceed the smaller MTU and are dropped. Fix by matching MTU on both sides. Workaround: ip ospf mtu-ignore (Cisco/EOS) skips the check but may cause fragmentation issues. On JunOS, set matching MTU values at the interface level.

Duplicate Router IDs

Two routers with the same Router ID cause LSA conflicts — each router's Type 1 LSA overwrites the other's in the LSDB. Symptoms: routes flapping, intermittent reachability. Fix: assign unique router IDs explicitly. Detect by checking for Type 1 LSAs with the same Link State ID but different advertising routers.

Area 0 Discontinuity

If area 0 is split, inter-area routing breaks — ABRs cannot flood Type 3 LSAs across the gap. Fix: restore physical backbone connectivity or configure virtual links through a transit area. Virtual links are temporary solutions — long-term design should maintain contiguous backbone.

Excessive Redistribution

Redistributing too many external routes into OSPF floods the LSDB with Type 5 LSAs, increasing SPF computation time and memory usage. Use route-maps with prefix-lists to limit redistribution scope. Consider stub or NSSA areas to shield non-edge routers from external LSAs.

Type 7 to Type 5 Translation

In NSSA areas, the ABR with the highest Router ID translates Type 7 LSAs to Type 5 for flooding into area 0. If translation fails, external routes from the NSSA are invisible to the rest of the OSPF domain. Verify the translator ABR is healthy and the forwarding address in the Type 7 LSA is reachable.

View on ClawHub

TERMINAL

clawhub install ospf-analysis