Binance Trade Jury

Use this skill when the user wants to put a Binance trade thesis on trial, review whether a long or short idea deserves risk, get an APPROVE / REVIEW / REJEC...

Security Scan

The skill is internally consistent: it is an instruction-only wrapper that posts a user's trade thesis to a third-party web API to get a verdict and playbook; the main practical risk is that user-provided strategy text (and any bankroll values) will be sent to an external service and the share-image payload is placed in a URL query string which may be logged.

Purpose & Capability

The name and description (review Binance trade theses) match the instructions (POST to a trade-jury API and build a share card). The skill requests no credentials, no binaries, and no config paths — nothing extraneous to the stated purpose. The external endpoints are third-party (vercel.app) but that is a reasonable implementation choice for this functionality.

Instruction Scope

Runtime instructions only direct the agent to extract symbol/side/thesis/bankroll and call the listed public endpoints, then base the response on returned JSON. The instructions do not read local files or unrelated env vars. Important privacy note: the SKILL.md instructs constructing a URL with a URL-encoded JSON payload for the share-image endpoint (GET query param), which can expose the thesis in logs, referrers, or analytics — this is a potential data-leakage vector to consider.

Install Mechanism

There is no install spec and no code files beyond SKILL.md and a small agent YAML; nothing is downloaded or written to disk by the skill itself. This minimizes installation risk.

Credentials

The skill requests no environment variables or credentials, which is proportionate. However, because the agent will POST user content (thesis and optional bankroll) to a third-party API, any sensitive or proprietary strategy text will be transmitted off-host. The use of a GET URL with the payload for the share-image endpoint increases the chance that data will be logged or leaked.

Persistence & Privilege

always:false (not forced into every session). agents/openai.yaml sets allow_implicit_invocation:true (the default) so the agent may autonomously call the skill when invoked — this is expected platform behavior and not in itself a red flag. There is no requested persistent system privilege or configuration of other skills.

Assessment

This skill appears to do what it says, but it sends whatever you put in the 'thesis' (and optional bankroll) to a third-party service (binance-trade-jury.vercel.app). If your trade ideas are sensitive or proprietary, avoid sending them verbatim. Prefer redacting identifying details or testing with dummy content first. Be cautious about using the share-image URL flow: it embeds the payload in the GET query string, which can be logged by servers, CDNs, or appear in referrers — avoid putting secret information there. If you want to avoid external network calls entirely, do not enable or invoke this skill. If you trust the service, proceed; otherwise ask the provider for a privacy policy or consider a local/manual review process.

Use this skill to review a Binance trade thesis before it becomes a real position.

Public endpoints:

• Review API: https://binance-trade-jury.vercel.app/api/trade-jury
• Share image: https://binance-trade-jury.vercel.app/api/trade-jury/share-image

When to use it

• The user wants a second opinion on a Binance trade idea.
• The user asks whether a long or short thesis is worth taking.
• The user wants a verdict backed by Binance market data instead of generic chat.
• The user wants a clearer entry, invalidation, and no-chase plan.
• The user wants a verdict card or social post for a reviewed thesis.

Workflow

1. Extract the trade symbol. Accept either BTC or BTCUSDT.
2. Extract the side as LONG or SHORT. If the user does not specify, default to LONG.
3. Extract the full thesis text. If the user gives no thesis, ask for it.
4. Optionally extract bankroll in USD. If none is given, send null.
5. Run:

curl -sS -X POST https://binance-trade-jury.vercel.app/api/trade-jury \
  -H 'Content-Type: application/json' \
  -d '{"symbol":"<symbol>","side":"<LONG|SHORT>","thesis":"<thesis>","bankrollUsd":null}'

6. Base the answer on the returned JSON. The most important fields are:

   • verdict
   • score
   • headline
   • summary
   • jurors
   • concerns
   • approvalConditions
   • playbook
   • shareText

7. If the user wants a share card, build a payload with:

   • verdict
   • score
   • symbol
   • side
   • headline
   • summary
   • primaryJuror
   • primaryConcern
   • generatedAt

   Then URL-encode the JSON and append it to:

https://binance-trade-jury.vercel.app/api/trade-jury/share-image?payload=<urlencoded-json>

Output guidance

• Lead with the verdict and why the bench reached it.
• Quote the three jurors in short form when useful.
• Keep the playbook concrete: starter, add, invalidation, no-chase, and risk cap.
• Do not invent exchange-private data or portfolio permissions. This skill uses Binance public market data only.
• If the API fails, surface the error and suggest retrying with a cleaner symbol or tighter thesis.