Portfolio Copilot

v1.0.0

Conversational portfolio briefings for Paradex accounts and vaults. Unifies account summary, positions, fills, balances, market data, and funding into natura...

0· 90·0 current·0 all-time
bySergey Vidyuk@sv

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for sv/paradex-portfolio-copilot.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Portfolio Copilot" (sv/paradex-portfolio-copilot) from ClawHub.
Skill page: https://clawhub.ai/sv/paradex-portfolio-copilot
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install paradex-portfolio-copilot

ClawHub CLI

Package manager switcher

npx clawhub@latest install paradex-portfolio-copilot
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description request portfolio summaries and the SKILL.md only refers to Paradex-specific MCP tools (account_summary, positions, balances, market_summaries, funding, transfers). There are no unrelated environment variables, binaries, or install steps requested — the requested capabilities match the stated purpose.
Instruction Scope
All runtime instructions are limited to reading Paradex portfolio and market data and formatting briefings. The SKILL.md does not instruct reading local files, environment secrets, or contacting external endpoints outside of the listed MCP tools. Recommendation: confirm that the referenced MCP tools are read-only and do not themselves have side effects (e.g., placing orders) or return unrelated account data.
Install Mechanism
No install spec and no code files — instruction-only skill. Nothing is downloaded or written to disk, which minimizes installation risk.
Credentials
The skill declares no required environment variables, secrets, or config paths. This is proportionate for a read-only briefing skill. Verify on your platform whether access to the MCP tools requires separate credentials and that those credentials are scoped appropriately.
Persistence & Privilege
always is false and model invocation is allowed (normal). The skill does not request permanent presence or claim to modify other skills or system settings.
Assessment
This skill appears internally consistent and low-risk: it only formats and presents Paradex account and market data. Before installing, confirm two things with your platform/operator: (1) the MCP tools referenced are read-only (they should only return account/market data and not execute trades or expose unrelated credentials), and (2) any credentials the platform supplies to those MCP tools are scoped minimally (read-only, limited to the specific Paradex account). If you want extra caution, test the skill with a non-production or demo Paradex account so you can confirm the outputs and that no unexpected actions occur.

Like a lobster shell, security has layers — review code before you run it.

latestvk97d6jb3aatj211zkf8yn08xjd841tfg
90downloads
0stars
1versions
Updated 3w ago
v1.0.0
MIT-0

Paradex Portfolio Copilot

The conversational interface for "what's going on with my Paradex account." Turns scattered data from multiple MCP tools into clear, concise briefings.

Available MCP Tools

ToolPortfolio data
paradex_vault_account_summaryEquity, margin, account health
paradex_vault_positionsAll open positions with P&L
paradex_vault_balanceCash balances
paradex_vault_transfersDeposit/withdrawal history
paradex_market_summariesCurrent prices, 24h changes for context
paradex_bboReal-time prices for any specific market
paradex_funding_dataFunding payments for cost tracking

Briefing Types

1. Quick Status ("How am I doing?")

The minimum viable answer. Pull vault_account_summary + vault_positions:

Your Paradex account has $X equity with N open positions.
Unrealized P&L: +$X (+X%).
Largest position: MARKET at $X notional.
Margin used: X% — [healthy/watch it/tight].

Keep it to 3-4 sentences. Only expand if asked.

2. Position Breakdown ("What are my positions?")

Pull vault_positions and present clearly:

For each position, report:

  • Market (e.g., BTC-USD-PERP)
  • Direction (Long/Short)
  • Size (in base currency and USD notional)
  • Entry price (if available)
  • Current mark price (from market_summaries)
  • Unrealized P&L (dollar and percentage)
  • Funding status (paying or receiving)

Sort by: largest notional first, or by P&L if user asks about winners/losers.

3. Daily Recap ("What happened today?")

Combine multiple data sources:

  1. Account snapshot: equity change from start of day (if inferrable from transfers + P&L)
  2. Position changes: new positions opened, positions closed, size changes
  3. P&L breakdown: which positions contributed most to today's P&L
  4. Funding costs: total funding paid/received today
  5. Market context: how did the user's markets move? (from market_summaries price_change_rate_24h)

4. Morning Briefing ("Give me a briefing")

A comprehensive start-of-day view:

  1. Account overview: equity, margin health, free capital
  2. Position summary: all positions with overnight P&L
  3. Overnight funding: total funding cost/income since last session
  4. Market context: how the user's markets moved overnight
  5. Risk flags: anything that needs attention (high margin, large unrealized loss, funding drain)
  6. Today's outlook: key levels or events for the user's markets (if identifiable from data)

5. P&L Analysis ("How much have I made?")

The most common question. Answer at the right granularity:

If they ask about total P&L:

  • Total unrealized from current positions
  • Note that realized P&L from closed positions isn't directly available via current MCP tools
  • Suggest checking the Paradex UI for full trade history

If they ask about a specific position:

  • Current unrealized P&L
  • Entry price vs. current price
  • Funding costs accumulated (estimate from funding_data)

If they ask about a time period:

  • Use position data + market price changes to estimate
  • Be honest about precision: "Based on current positions and recent market moves, approximately..."

6. Balance & Cash ("How much do I have?")

Pull vault_balance:

  • Total balance
  • Available (free to trade or withdraw)
  • Locked (in positions as margin)
  • Ratio of deployed vs. idle capital

If user asks about deposits/withdrawals, also pull vault_transfers:

  • Recent transfer history
  • Net deposits over time
  • Any pending transfers

Conversational Patterns

The copilot should feel like talking to a knowledgeable friend, not reading a report.

Match the question's energy:

  • "How am I doing?" → 2-3 sentence summary, positive framing, flag concerns
  • "Give me everything" → Full detailed briefing
  • "Am I making money?" → Lead with the P&L number, then context
  • "What's my biggest position?" → Direct answer, then relevant context

Proactive observations: After answering the direct question, add 1 relevant observation if useful:

  • "By the way, your ETH position is now 55% of your exposure — worth keeping an eye on."
  • "Your funding costs are running about $X/day — mostly from the SOL position."
  • "Your margin is at 72% — you don't have much room for new positions."

Don't add observations every time — only when something is noteworthy.

Follow-up suggestions: End with 1 natural follow-up when appropriate:

  • "Want me to break down the P&L by position?"
  • "Want a risk check on your current positions?"
  • "Should I look at what's happening in those markets?"

Output Style

  • Lead with the answer, not the process
  • Use dollar amounts for P&L and equity (real money feels concrete)
  • Use percentages for changes and ratios
  • Round sensibly: $12,345 not $12,345.6789
  • Use 🟢🟡🔴 sparingly — only for clear health indicators
  • No tables unless the user has 4+ positions (just describe 1-3 positions in prose)
  • Tables for 4+ positions with clean columns: Market | Direction | Size | P&L

Caveats

  • Realized P&L from closed trades is not directly available from the current MCP tools. Be upfront about this and point users to the Paradex UI for complete history.
  • P&L estimates for time periods are approximate — based on current positions and market moves
  • Account data is a point-in-time snapshot — positions and prices change continuously
  • This is portfolio information, not trading advice

See briefing-formats.md for detailed output templates with examples.

Comments

Loading comments...