Guide users through their first complete trade on Hyperliquid via Senpi. This skill teaches the core loop: discover top traders → create a strategy that mirrors a chosen trader → monitor → close strategy.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionsenpi-getting-started-guideExecute the skills CLI command in your project's root directory to begin installation:
Fetches senpi-getting-started-guide from senpi-ai/senpi-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate senpi-getting-started-guide. Access via /senpi-getting-started-guide in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
2
total installs
2
this week
61
GitHub stars
0
upvotes
Run in your terminal
2
installs
2
this week
61
stars
Guide users through their first complete trade on Hyperliquid via Senpi. This skill teaches the core loop: discover top traders → create a strategy that mirrors a chosen trader → monitor → close strategy.
Prerequisites (agent-only): Senpi MCP connected. Onboarding complete (see state check below). Wallet funded for creating a strategy; if not yet funded, show a funding reminder and do not start until balance ≥ $100 or user confirms they funded.
User-facing rule: Never show the user internal details. Do not mention state names (e.g. UNFUNDED, READY, FRESH), file paths (e.g. state.json, ~/.config/senpi), step codes (e.g. STRATEGY_CREATED), or MCP/tool names. Use only plain, friendly language (e.g. "You're all set to start", "Fund your wallet to begin", "Your strategy is running").
Minimum strategy budget: Use $100 as the minimum when creating the first-trade mirror strategy. Do not suggest or use $50 or any amount below $100.
Before starting the tutorial, verify:
Ensure state file exists; if missing, create it and redirect. When redirecting, tell the user only: "You need to complete setup first. Say 'set up Senpi' or 'connect to Senpi' to get started." Do not mention state file, FRESH, or any internal state.
# Ensure state file exists (per state lifecycle); if missing, create and redirect
if [ ! -f ~/.config/senpi/state.json ]; then
mkdir -p ~/.config/senpi
cat > ~/.config/senpi/state.json << 'STATEEOF'
{
"version": "1.0.0",
"state": "FRESH",
"error": null,
"onboarding": {
"step": "IDENTITY",
"startedAt": null,
"completedAt": null,
"identityType": null,
"subject": null,
"walletGenerated": false,
"existingAccount": false
},
"account": {},
"wallet": { "funded": false },
"firstTrade": { "completed": false, "skipped": false },
"mcp": { "configured": false }
}
STATEEOF
# Tell user only (do not echo internal messages):
# "You need to complete setup first. Say 'set up Senpi' or 'connect to Senpi' to get started."
exit 1
fi
STATE=$(cat ~/.config/senpi/state.json | node -p "JSON.parse(require('fs').readFileSync(0,'utf8')).state")
if [ "$STATE" = "FRESH" ] || [ "$STATE" = "ONBOARDING" ]; then
# Tell user only (do not echo "User needs to complete onboarding" or state names):
# "You need to complete setup first. Say 'set up Senpi' or 'connect to Senpi' to get started."
exit 1
fi
Start this tutorial when:
AWAITING_FIRST_TRADE and user sends a trading-related messageDo NOT start if: MCP not connected — then tell the user to set up Senpi first (do not mention MCP or state). If user says "skip tutorial", set state to READY and show the skip message from references/next-steps.md. If wallet has less than $100 when starting, do not create a strategy until funded; use the funding reminder below (user-friendly wording only).
Follow steps in order. Reference files contain display copy, state schemas, and error handling.
If the user asked for the first-trade guide (e.g. "let's trade") but the wallet is not yet funded:
If onboarding is not complete (state FRESH or ONBOARDING), tell the user only: "Complete setup first — say 'set up Senpi' to get started." Do not say "onboarding", "state", or "User needs to complete onboarding first."
Display the trade cycle. When showing the 4-step list to the user, use this exact wording:
1️⃣ Discover — Find top-performing traders on Hyperliquid
2️⃣ Create a strategy — Mirror a chosen trader's positions ($100 budget)
3️⃣ Monitor — Watch how the strategy performs
4️⃣ Close — Exit when you're ready
Recommend a $100 minimum budget for the first strategy and include a short risk disclaimer. Ask user to say "yes" to continue or "skip" if experienced.
Update state: set firstTrade.step to INTRODUCTION, firstTrade.started true, startedAt (ISO 8601). Preserve existing fields in state.json.
Wait for user confirmation before proceeding.
Use MCP discovery_get_top_traders to fetch top traders. Optionally use discovery_get_trader_state or discovery_get_trader_history for extra detail. Show a short table of top traders (e.g. by PnL, win rate) and recommend one trader to mirror for the first trade.
See references/discovery-guide.md for display template and state update (firstTrade.step: "DISCOVERY", recommendedTraderId, recommendedTraderName).
Before creating the strategy, explain: chosen trader, budget ($100 minimum), and that the strategy will mirror that trader's positions. Warn about risk and liquidation. Ask user to say "confirm" to create the strategy.
See references/strategy-management.md for the sizing table and wording.
On user confirmation, call MCP strategy_create with the chosen trader (from Step 2) and budget (minimum $100). On success, show the celebration (see references/next-steps.md — "Celebrate (After First Strategy Created)"): congratulate the user for opening their first strategy, then offer "how's my strategy?", "close my strategy", or "show my positions". Do not show strategy status or raw IDs.
Update state per references/strategy-management.md: set firstTrade.step: "STRATEGY_CREATED", tradeDetails (strategyId, mirroredTraderId, etc.), and set firstTrade.completed: true, firstTrade.step: "COMPLETE", firstTrade.completedAt. On failure, see references/error-handling.md.
When user asks "how's my strategy?" or similar, fetch data via MCP: strategy_get, strategy_get_clearinghouse_state, or execution_get_open_position_details for open positions. Show strategy value, open positions (if any), unrealized PnL, ROE. Offer: Hold, Close strategy, or Add protection. Do not show a separate congratulations here — that was already shown when they created their first strategy (Step 4).
When user says "close", "exit", "close my strategy", "take profit", etc., call MCP strategy_close with the strategy ID from state. Tell the user the strategy is closed and show realized PnL, duration, and fees in plain language. Show the "After Close" result and next steps from references/next-steps.md (no separate congratulations — already shown when they created the strategy). Do not mention strategy status or internal codes. Update state (STRATEGY_CLOSE, tradeDetails with closedAt, pnl, etc.). See references/strategy-management.md.
When the user has closed their strategy (Step 6), the result and next steps are shown there. No separate celebration step — state was already set to READY and firstTrade.completed when they created their first strategy (Step 4). Full "After Close" copy: references/next-steps.md. State shape: references/strategy-management.md.
If the user returns mid-tutorial, read firstTrade.step from state and resume from the matching step. See references/next-steps.md for resume logic. Resume message must be user-friendly only — e.g. "You were in the middle of your first trade. Here’s where we left off…" Do not mention step names (INTRODUCTION, DISCOVERY, STRATEGY_CREATED, etc.) or state.
npx skills add Senpi-ai/senpi-skills/senpi-getting-started-guide
Or manually:
mkdir -p ~/.senpi/skills/senpi-getting-started-guide
curl -sL "https://raw.githubusercontent.com/Senpi-ai/senpi-skills/main/senpi-getting-started-guide/SKILL.md" \
-o ~/.senpi/skills/senpi-getting-started-guide/SKILL.md
# Copy references/ into the same skill directory
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
anthropics/claude-code
mblode/agent-skills
github/awesome-copilot
leonxlnx/taste-skill
sickn33/antigravity-awesome-skills
erichowens/some_claude_skills
senpi-getting-started-guide reduced setup friction for our internal harness; good balance of opinion and flexibility.
senpi-getting-started-guide fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
senpi-getting-started-guide is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
senpi-getting-started-guide fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Registry listing for senpi-getting-started-guide matched our evaluation — installs cleanly and behaves as described in the markdown.
Solid pick for teams standardizing on skills: senpi-getting-started-guide is focused, and the summary matches what you get after install.
Registry listing for senpi-getting-started-guide matched our evaluation — installs cleanly and behaves as described in the markdown.
Useful defaults in senpi-getting-started-guide — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
senpi-getting-started-guide fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
senpi-getting-started-guide reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 43