What problem does it solve? Jito bundles on Solana fail for a small set of well-defined reasons, but the error messages are cryptic and the failure modes (rejected, simulated-failed, silently dropped, landed-but-reverted) are hard to distinguish. This Skill turns a vague report like "the bundle didn't land" into a specific root cause and a concrete next command in under a minute. ## Core Features & Use Cases - Symptom-to-cause mapping: A decision flow and diagnosis table covering sendBundle errors (Invalid, tip-account lock failures, simulation failures), silent drops, and landed-but-reverted bundles. - Status classification workflow: Uses tools/check-bundle-status.ts with a bundle UUID to classify bundles as LANDED, PROCESSED, PENDING, or UNKNOWN, and explains what each state means operationally. - Tip economics guidance: Concrete tip sizing recommendations per scenario (fee collection, standard launch, sniper competition, leaked-key rescue) plus regional block-engine endpoint fallbacks. - Use Case: Your fire-jito.js launch script returned "Bundles must write lock at least one tip account". The Skill identifies stale hardcoded tip accounts as the cause and directs you to run tools/check-tip-accounts.ts and patch the account list. ## Quick Start Ask the assistant to diagnose why my Jito bundle did not land, given the error message or bundle UUID from my script output.