Run any Skill in Manus with one click

imperial

Stars23

Forks21

UpdatedMay 21, 2026 at 18:28

Entry-point skill for Imperial perpetual routing on Solana. Use before answering or acting on Imperial router flows, Phoenix-routed perps, profile funding, market/portfolio intel, risk checks, TP/SL, TWAP, grid, or Telegram bot trading workflows.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

x402agent

x402agent/solana-clawd

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	imperial
description	Entry-point skill for Imperial perpetual routing on Solana. Use before answering or acting on Imperial router flows, Phoenix-routed perps, profile funding, market/portfolio intel, risk checks, TP/SL, TWAP, grid, or Telegram bot trading workflows.

Imperial

Imperial is the router layer. In this project, Phoenix is the preferred default venue when the user asks to "go straight Phoenix", but execution still flows through Imperial's authenticated mobile/* endpoints when the bot is acting as the operator.

Use this skill first, then route to the focused Imperial skill that matches intent.

Core rules:

Treat IMPERIAL_API_KEY / IMPERIAL_JWT as a trading credential. Never display or log it.
Treat every profile as isolated. Always track profileIndex.
Always inspect success in POST /api/v1/mobile/orders responses even on HTTP 200.
Prefer Phoenix (underwriter=2) unless the user explicitly requests another venue or route data says otherwise.
For Telegram/webhook flows, only promise durable strategy execution when a real runner exists. Do not present a stateless webhook as a TWAP/grid engine.

More from this repository

same repository

pump-build-release

x402agent/solana-clawd

Build and release pipeline for the Pump SDK — tsup TypeScript builds, Cargo release profiles, semantic release with commitizen, npm publishing, linting, Makefile targets, Vercel deployment, and MCP server distribution.

2026-05-2423

pump-claims-readonly

x402agent/solana-clawd

Read-only query methods for PumpFun claims — unclaimed token rewards, creator vault balances, volume accumulators, distributable fees, and current-day token previews across Pump and PumpAMM programs.

2026-05-2423

pump-sdk-core

x402agent/solana-clawd

Build and extend the core Pump SDK — an offline-first TypeScript SDK that constructs Solana TransactionInstructions for token creation, buying, selling, migration, and creator fee collection across three on-chain programs (Pump, PumpAMM, PumpFees).

2026-05-2423

pump-admin-ops

x402agent/solana-clawd

Admin and authority operations for the Pump protocol — set coin creator, update token incentives, set IDL authority, claim cashback, Mayhem mode, and BothPrograms cross-program admin instructions.

2026-05-2423

pump-ai-agents

x402agent/solana-clawd

AI agent integration layer for the Pump SDK — agent instruction files, .well-known discovery, LLM context documents, 15+ skill files, MCP server prompts, and terminal management rules for GitHub Copilot, Claude, and Gemini.

2026-05-2423

pump-bonding-curve

x402agent/solana-clawd

Constant-product AMM bonding curve math for Pump token pricing — buy/sell quoting, fee-aware calculations, market cap computation, tiered fees, ceiling division, virtual vs real reserves, and edge-case handling.

2026-05-2423

name	imperial
description	Entry-point skill for Imperial perpetual routing on Solana. Use before answering or acting on Imperial router flows, Phoenix-routed perps, profile funding, market/portfolio intel, risk checks, TP/SL, TWAP, grid, or Telegram bot trading workflows.

Imperial

Use this skill first, then route to the focused Imperial skill that matches intent.

Core rules:

Treat IMPERIAL_API_KEY / IMPERIAL_JWT as a trading credential. Never display or log it.
Treat every profile as isolated. Always track profileIndex.
Always inspect success in POST /api/v1/mobile/orders responses even on HTTP 200.
Prefer Phoenix (underwriter=2) unless the user explicitly requests another venue or route data says otherwise.
For Telegram/webhook flows, only promise durable strategy execution when a real runner exists. Do not present a stateless webhook as a TWAP/grid engine.