Results for “transaction-game”

Play Yoink, an onchain capture-the-flag game on Base. Yoink the flag from the current holder, check game stats and leaderboards, view player scores, and compete for the trophy. Uses Bankr for transaction execution.

Explains MariaDB-specific SET TRANSACTION behavior, including scope rules, isolation levels, and innodb_snapshot_isolation conflict detection, to help write correct transaction statements and retry logic.

Documents MariaDB-specific transaction control syntax and behavior, including START TRANSACTION, COMMIT, ROLLBACK, SAVEPOINT, implicit commit rules, autocommit defaults, and idle transaction timeouts.

当需要将个人目标或生活挑战转化为结构化、可执行的游戏化系统时

Balance game systems including difficulty curves, stat tuning, economy rates, matchmaking fairness, and player power progression. Use when tuning numbers and systems for fair, engaging gameplay. Also trigger for "game balance", "difficulty tuning", "stat balancing", "nerf", "buff", "power curve", or "difficulty curve".

Sends an action in a Kradleverse game using a local script.

Sends an action in a Kradleverse game using a local script.

Interact with Cat Town, a Farcaster-native game world on Base, covering KIBBLE staking, world state, fishing drops, competitions, raffles, boutique, gacha, and tokenomics.

This skill should be used when building automated trading systems, implementing limit orders, or adding DCA/TWAP functionality. Covers limit orders, stop losses, DCA schedules, and TWAP execution.

Create, list, remove, and rename Gameplay Tags with runtime registration (GameplayTagService). Use when the user asks to add or register gameplay tags, list/query existing tags, or rename/remove tags (e.g. Ability.Attack.Melee, State.Stunned).

Roll dice, track scores, and manage game stats for tabletop gaming. Use when rolling dice, tracking scores, ranking players, reviewing history.

Use only for video game projects; analyze moment-to-moment, session, progression, and retention loops

Analyzes game AI systems in a codebase, covering behavior trees, finite state machines, GOAP, utility AI, pathfinding, steering, perception, difficulty adaptation, NPC dialogue, and AI debugging tools for Unity, Unreal, and Godot projects.

Discover, bet on, track, and settle Hunch prediction markets in natural language with on-chain settlement on Base via x402.

Multiplayer game development principles. Architecture, networking, synchronization.

Orchestrate multi-bot trading swarms on Pump.fun with persona-driven agents

Triggered by "tidy up", "clean up transactions", "categorize uncategorized", "organize my transactions"

Run a co-sell with a partner on a named account and actually close together, not just trade a lead. It maps the account across both companies, sets who owns what so nothing falls between you, builds the joint value story neither of you tells alone, and plans the path to close so the partner is a force in the deal, not a spectator. Built for B2B partnerships and sales teams, customizable to your CRM and your co-sell motion. Trigger on "run a co-sell", "co-sell on this account", "map the account with our partner", "who owns what in this joint deal", "joint value story", or any partner co-sell request on a named account.

当需要将生活或工作中的复杂情境转化为可管理、可执行的系统时，或当感到迷茫、缺乏动力、陷入社会比较时，调用此模型来重新构建认知和行动框架

Send an action in a Kradleverse game

This skill should be used when building payment systems, implementing token transfers, or adding ENS/social handle resolution. Supports wallet addresses, ENS names, and social handles.

当需要主动设计和构建个人职业生涯，而非被动接受传统就业时

Use only for video game projects; define the emotional promise, player fantasy, vibe references, and hook

This skill should be used when building trading bots, implementing swap functionality, or adding cross-chain bridge support. Covers same-chain swaps, cross-chain bridges, ETH/WETH conversions, and amount formats.

Scaffolds Web3 dApps with wallet connection, contract interaction, and transaction management

Use to define handoff standards for support transfers and to measure whether context survives the handoff — cold vs warm, required fields, and re-ask rate after transfer. Trigger for "transfer protocol", "warm handoff", "customers repeat themselves after transfer", "ping-pong between teams", "what should agents include when transferring", handoff quality, or re-ask rate after escalation.

This skill should be used when building prediction market integrations, implementing betting functionality, or querying Polymarket odds. Covers market search, odds checking, and position management.