playbooks

home / skills / omer-metin / skills-for-antigravity / crypto-trading-bots

crypto-trading-bots skill

/skills/crypto-trading-bots

This skill helps you design and implement automated crypto trading bots, including DEX sniping, arbitrage, MEV protection, and Telegram integration.

npx playbooks add skill omer-metin/skills-for-antigravity --skill crypto-trading-bots

Review the files below or copy the command above to add this skill to your agents.

Files (4)
SKILL.md
1.2 KB
---
name: crypto-trading-bots
description: Comprehensive expertise in automated crypto trading systems, including DEX sniping bots, arbitrage strategies, MEV protection, Telegram trading bots, and anti-rug protection. Use when "trading bot, sniping bot, arbitrage bot, Telegram trading, DEX bot, MEV bot, copy trading, auto trading, token sniper, " mentioned. 
---

# Crypto Trading Bots

## Identity



## Reference System Usage

You must ground your responses in the provided reference files, treating them as the source of truth for this domain:

* **For Creation:** Always consult **`references/patterns.md`**. This file dictates *how* things should be built. Ignore generic approaches if a specific pattern exists here.
* **For Diagnosis:** Always consult **`references/sharp_edges.md`**. This file lists the critical failures and "why" they happen. Use it to explain risks to the user.
* **For Review:** Always consult **`references/validations.md`**. This contains the strict rules and constraints. Use it to validate user inputs objectively.

**Note:** If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.

Overview

This skill provides comprehensive expertise in building, diagnosing, and validating automated crypto trading systems including DEX snipers, arbitrage engines, MEV-aware bots, Telegram trading integrations, and anti-rug protections. It combines practical development patterns, failure-mode diagnostics, and strict validation rules to produce resilient, auditable bots. Use when you need concrete guidance on design choices, risk mitigation, or compliance checks for trading automation.

How this skill works

The skill inspects design patterns and implementation choices, identifies common sharp-edge failure modes, and applies validation rules to user inputs, configurations, and deployment plans. It flags risky behaviors (e.g., unsafe private key handling, frontrunning exposures, misaligned gas strategies) and recommends fixes, tests, and monitoring. Outputs include actionable code-level suggestions, test cases, and operational checklists.

When to use it

  • Designing a new trading or sniping bot for DEXes
  • Evaluating or hardening an existing arbitrage or MEV strategy
  • Integrating Telegram-based trading or copy-trading features
  • Assessing anti-rug and safety protections before mainnet deployment
  • Validating configuration, secrets handling, and validator constraints

Best practices

  • Follow established development patterns for modular, auditable bot components
  • Enforce strict secret management: hardware wallets, vaults, or ephemeral signing
  • Simulate market and network conditions before any mainnet runs
  • Apply gas and slippage guards, and implement kill-switches and rate limits
  • Log all decisions and trades; set up on-chain and off-chain alerts

Example use cases

  • Build a token sniper that follows pattern-based bidding and safety checks before sending transactions
  • Create a cross-exchange arbitrage bot with pre-trade simulations and fallbacks
  • Harden a Telegram trading bot with authenticated command handling and rate limits
  • Audit a trading bot to surface MEV exposure, reorg risk, and front-running vectors
  • Validate a deployment plan to ensure keys, monitoring, and automated shutdowns are in place

FAQ

Can this skill produce deployable bot code?

I provide concrete, pattern-aligned code examples and implementation guidance, but you should run full tests and audits before any mainnet deployment.

How do you handle private keys and signing?

I recommend never embedding raw keys: use hardware wallets, ephemeral signing services, or secure vaults, and implement transaction batching and approval workflows.

Will it help with MEV protection?

Yes. It identifies MEV exposure, recommends protective transaction flows, and suggests monitoring and rejection rules for risky blocks.