Miraix Meme Court

Use this skill when the user wants to run Miraix Meme Court, shortlist Solana meme candidates, apply Rug Court safety and liquidity checks, approve one disci...

Security Scan

The skill is internally consistent with its stated purpose: it is an instruction-only wrapper that POSTs trade-selection requests to app.miraix.fun, summarizes the result, and can request unsigned payload preparation only with explicit user consent; it requests no credentials or installs.

Purpose & Capability

The name/description (Miraix Meme Court, shortlist Solana meme candidates, run Rug Court checks, prepare unsigned payloads) map directly to the SKILL.md instructions which call three public Miraix endpoints. There are no unrelated environment variables, binaries, or install steps requested. The only oddity is a hard-coded default walletAddress, but this is consistent with a demo/default behaviour rather than an unexplained privilege.

Instruction Scope

Runtime instructions instruct the agent to POST JSON (walletAddress, budgetUsd, riskMode, strategy) to https://app.miraix.fun endpoints and to base responses on returned fields. This necessarily sends user-supplied wallet addresses and budget info to a third-party domain — expected for the skill's function but a privacy consideration. The SKILL.md explicitly requires the user to ask before preparing unsigned payloads and forbids claiming live signing unless API proves it, which reduces risk. The skill does not request private keys or other credentials.

Install Mechanism

Instruction-only skill with no install spec and no code files to execute. No downloads, package installs, or archive extraction are present, which minimizes disk/write risk.

Credentials

The skill declares no required environment variables, no credentials, and no config paths. This is proportionate: the API interactions shown do not require platform secrets. Note: a default walletAddress is embedded in the SKILL.md — that is not a secret but may be unexpected as a default input.

Persistence & Privilege

always:false (no forced permanent inclusion). The included agents/openai.yaml sets allow_implicit_invocation: true which permits the skill to be invoked by the agent when appropriate; this is standard for skills and not a persistence or privilege escalation by itself. The skill does not request to modify other skills or system-wide settings.

Assessment

Before installing or using this skill, consider that it will send the wallet address and budget/parameters you provide to a third-party domain (https://app.miraix.fun). The skill does not request or store private keys and will not sign or submit live trades unless the API returns a live prepared payload — and it only calls the 'prepare' endpoint when the user explicitly requests payload preparation. Verify you trust the Miraix service and its privacy/data-retention policies before sending any sensitive information, never paste private keys or signing seeds into prompts, and confirm any unsigned payloads with your wallet/signer before using them in live execution. If you require higher assurance, ask the skill author for details about the operator, hosting, and data handling for app.miraix.fun.

Use this skill to run the public Miraix Meme Court flow for the Bitget Wallet track. The skill narrows Solana meme candidates into one approved trade by splitting the work into Scout, Risk Agent / Rug Court, and Trader.

Public endpoints:

• Desk API: https://app.miraix.fun/api/meme-rotation-desk
• Prepare API: https://app.miraix.fun/api/meme-rotation-desk/prepare
• Order status API: https://app.miraix.fun/api/meme-rotation-desk/order-status

Defaults:

• walletAddress: AYY3Bi6NSwH3F9Q5cy5xN9ZqRgnNYhm6TMkTwVBRVGeq
• budgetUsd: 100
• riskMode: balanced
• strategy: momentum

Allowed values:

• riskMode: safe, balanced, degen
• strategy: momentum, reversal, shadow

When to use it

• The user wants one disciplined Solana meme trade instead of a list of ideas.
• The user wants to run Scout, Rug Court, and Trader against a wallet and budget.
• The user wants a shortlist plus vetoes plus one approved trade.
• The user wants to know whether unsigned payload preparation is available.
• The user already has an orderId and wants to check order status.

Workflow

1. Extract these inputs from the request:

   • walletAddress
   • budgetUsd
   • riskMode
   • strategy

   If any field is missing, fill it with the defaults above instead of blocking.

2. Run the desk:

curl -sS https://app.miraix.fun/api/meme-rotation-desk \
  -H 'Content-Type: application/json' \
  -d '{
    "walletAddress":"<wallet-address>",
    "budgetUsd":<budget-usd>,
    "riskMode":"<safe|balanced|degen>",
    "strategy":"<momentum|reversal|shadow>"
  }'

3. Base the answer on these fields:

   • dataMode
   • warnings
   • marketContext
   • agents
   • candidates
   • approvedTrade
   • execution
   • proofBundle

4. Lead with the one approved trade:

   • symbol
   • size in USD
   • allocation percentage
   • rationale
   • invalidation
   • take-profit ladder

5. Then summarize Rug Court:

   • approved names
   • watch names
   • banned names
   • the most important courtNote

6. Then summarize execution readiness:

   • state
   • mode
   • source
   • market
   • estimatedOutput
   • whether canPrepare is true

7. If and only if all of these are true:

   • the user explicitly wants payload preparation
   • execution.canPrepare is true
   • execution.market exists
   • approvedTrade.outputContract exists

   then call:

curl -sS https://app.miraix.fun/api/meme-rotation-desk/prepare \
  -H 'Content-Type: application/json' \
  -d '{
    "walletAddress":"<wallet-address>",
    "outputContract":"<approved-trade-output-contract>",
    "market":"<execution-market>",
    "amountUsd":<approved-trade-amount-usd>,
    "mode":"<order|swap>",
    "outputSymbol":"<approved-trade-symbol>"
  }'

8. If the user gives an orderId and wants status, run:

curl -sS https://app.miraix.fun/api/meme-rotation-desk/order-status \
  -H 'Content-Type: application/json' \
  -d '{
    "orderId":"<order-id>"
  }'

9. Treat preview mode honestly:
   • If dataMode is fallback, say the result is in preview mode.
   • If prepare returns prepared: false, say unsigned payload generation is not available in the current live environment.
   • Do not claim live signing or live order creation unless the API returns a live prepared payload.

Output guidance

• Keep the answer structured and concise.
• Lead with Approved trade.
• Then show Rug Court summary.
• Then show Execution readiness.
• Then show Warnings if present.
• Use the exact field values from the API instead of paraphrasing away important numbers.
• If the API is in preview mode, say so explicitly.
• Do not claim that Miraix or Bitget signed, submitted, or filled any trade unless the API response proves that.