spot▌
binance/binance-skills-hub · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
$npx skills add https://github.com/binance/binance-skills-hub --skill spot
summary
Complete Binance Spot trading API access with 40+ endpoints for orders, market data, and account management.
- ›Covers market data endpoints (tickers, klines, order books, trades) and authenticated trading operations (place, cancel, amend orders, OCO/OPO/OTO strategies)
- ›Supports three environments: mainnet, testnet, and demo with API key and secret authentication
- ›Includes advanced order types: stop-loss, take-profit, iceberg, trailing stop, and multi-leg strategies (OCO, OPO, OTO, OPOCO
skill.md
Binance Spot Skill
Spot request on Binance using authenticated API endpoints. Requires API key and secret key for certain endpoints. Return the result in JSON format.
Quick Reference
| Endpoint | Description | Required | Optional | Authentication |
|---|---|---|---|---|
/api/v3/exchangeInfo (GET) |
Exchange information | None | symbol, symbols, permissions, showPermissionSets, symbolStatus | No |
/api/v3/ping (GET) |
Test connectivity | None | None | No |
/api/v3/time (GET) |
Check server time | None | None | No |
/api/v3/aggTrades (GET) |
Compressed/Aggregate trades list | symbol | fromId, startTime, endTime, limit | No |
/api/v3/avgPrice (GET) |
Current average price | symbol | None | No |
/api/v3/depth (GET) |
Order book | symbol | limit, symbolStatus | No |
/api/v3/historicalTrades (GET) |
Old trade lookup | symbol | limit, fromId | No |
/api/v3/klines (GET) |
Kline/Candlestick data | symbol, interval | startTime, endTime, timeZone, limit | No |
/api/v3/ticker (GET) |
Rolling window price change statistics | None | symbol, symbols, windowSize, type, symbolStatus | No |
/api/v3/ticker/24hr (GET) |
24hr ticker price change statistics | None | symbol, symbols, type, symbolStatus | No |
/api/v3/ticker/bookTicker (GET) |
Symbol order book ticker | None | symbol, symbols, symbolStatus | No |
/api/v3/ticker/price (GET) |
Symbol price ticker | None | symbol, symbols, symbolStatus | No |
/api/v3/ticker/tradingDay (GET) |
Trading Day Ticker | None | symbol, symbols, timeZone, type, symbolStatus | No |
/api/v3/trades (GET) |
Recent trades list | symbol | limit | No |
/api/v3/uiKlines (GET) |
UIKlines | symbol, interval | startTime, endTime, timeZone, limit | No |
/api/v3/openOrders (DELETE) |
Cancel All Open Orders on a Symbol | symbol | recvWindow | Yes |
/api/v3/openOrders (GET) |
Current open orders | None | symbol, recvWindow | Yes |
/api/v3/order (POST) |
New order | symbol, side, type | timeInForce, quantity, quoteOrderQty, price, newClientOrderId, strategyId, strategyType, stopPrice, trailingDelta, icebergQty, newOrderRespType, selfTradePreventionMode, pegPriceType, pegOffsetValue, pegOffsetType, recvWindow | Yes |
/api/v3/order (DELETE) |
Cancel order | symbol | orderId, origClientOrderId, newClientOrderId, cancelRestrictions, recvWindow | Yes |
/api/v3/order (GET) |
Query order | symbol | orderId, origClientOrderId, recvWindow | Yes |
/api/v3/order/amend/keepPriority (PUT) |
Order Amend Keep Priority | symbol, newQty | orderId, origClientOrderId, newClientOrderId, recvWindow | Yes |
/api/v3/order/cancelReplace (POST) |
Cancel an Existing Order and Send a New Order | symbol, side, type, cancelReplaceMode | timeInForce, quantity, quoteOrderQty, price, cancelNewClientOrderId, cancelOrigClientOrderId, cancelOrderId, newClientOrderId, strategyId, strategyType, stopPrice, trailingDelta, icebergQty, newOrderRespType, selfTradePreventionMode, cancelRestrictions, orderRateLimitExceededMode, pegPriceType, pegOffsetValue, pegOffsetType, recvWindow | Yes |
/api/v3/order/oco (POST) |
New OCO - Deprecated | symbol, side, quantity, price, stopPrice | listClientOrderId, limitClientOrderId, limitStrategyId, limitStrategyType, limitIcebergQty, trailingDelta, stopClientOrderId, stopStrategyId, stopStrategyType, stopLimitPrice, stopIcebergQty, stopLimitTimeInForce, newOrderRespType, selfTradePreventionMode, recvWindow | Yes |
/api/v3/order/test (POST) |
Test new order | symbol, side, type | computeCommissionRates, timeInForce, quantity, quoteOrderQty, price, newClientOrderId, strategyId, strategyType, stopPrice, trailingDelta, icebergQty, newOrderRespType, selfTradePreventionMode, pegPriceType, pegOffsetValue, pegOffsetType, recvWindow | Yes |
/api/v3/orderList (DELETE) |
Cancel Order list | symbol | orderListId, listClientOrderId, newClientOrderId, recvWindow | Yes |
/api/v3/orderList (GET) |
Query Order list | None | orderListId, origClientOrderId, recvWindow | Yes |
/api/v3/orderList/oco (POST) |
New Order list - OCO | symbol, side, quantity, aboveType, belowType | listClientOrderId, aboveClientOrderId, aboveIcebergQty, abovePrice, aboveStopPrice, aboveTrailingDelta, aboveTimeInForce, aboveStrategyId, aboveStrategyType, abovePegPriceType, abovePegOffsetType, abovePegOffsetValue, belowClientOrderId, belowIcebergQty, belowPrice, belowStopPrice, belowTrailingDelta, belowTimeInForce, belowStrategyId, belowStrategyType, belowPegPriceType, belowPegOffsetType, belowPegOffsetValue, newOrderRespType, selfTradePreventionMode, recvWindow | Yes |
/api/v3/orderList/opo (POST) |
New Order List - OPO | symbol, workingType, workingSide, workingPrice, workingQuantity, pendingType, pendingSide | listClientOrderId, newOrderRespType, selfTradePreventionMode, workingClientOrderId, workingIcebergQty, workingTimeInForce, workingStrategyId, workingStrategyType, workingPegPriceType, workingPegOffsetType, workingPegOffsetValue, pendingClientOrderId, pendingPrice, pendingStopPrice, pendingTrailingDelta, pendingIcebergQty, pendingTimeInForce, pendingStrategyId, pendingStrategyType, pendingPegPriceType, pendingPegOffsetType, pendingPegOffsetValue, recvWindow | Yes |
/api/v3/orderList/opoco (POST) |
New Order List - OPOCO | symbol, workingType, workingSide, workingPrice, workingQuantity, pendingSide, pendingAboveType | listClientOrderId, newOrderRespType, selfTradePreventionMode, workingClientOrderId, workingIcebergQty, workingTimeInForce, workingStrategyId, workingStrategyType, workingPegPriceType, workingPegOffsetType, workingPegOffsetValue, pendingAboveClientOrderId, pendingAbovePrice, pendingAboveStopPrice, pendingAboveTrailingDelta, pendingAboveIcebergQty, pendingAboveTimeInForce, pendingAboveStrategyId, pendingAboveStrategyType, pendingAbovePegPriceType, pendingAbovePegOffsetType, pendingAbovePegOffsetValue, pendingBelowType, pendingBelowClientOrderId, pendingBelowPrice, pendingBelowStopPrice, pendingBelowTrailingDelta, pendingBelowIcebergQty, pendingBelowTimeInForce, pendingBelowStrategyId, pendingBelowStrategyType, pendingBelowPegPriceType, pendingBelowPegOffsetType, pendingBelowPegOffsetValue, recvWindow | Yes |
/api/v3/orderList/oto (POST) |
New Order list - OTO | symbol, workingType, workingSide, workingPrice, workingQuantity, pendingType, pendingSide, pendingQuantity | listClientOrderId, newOrderRespType, selfTradePreventionMode, workingClientOrderId, workingIcebergQty, workingTimeInForce, workingStrategyId, workingStrategyType, workingPegPriceType, workingPegOffsetType, workingPegOffsetValue, pendingClientOrderId, pendingPrice, pendingStopPrice, pendingTrailingDelta, pendingIcebergQty, pendingTimeInForce, pendingStrategyId, pendingStrategyType, pendingPegPriceType, pendingPegOffsetType, pendingPegOffsetValue, recvWindow | Yes |
/api/v3/orderList/otoco (POST) |
New Order list - OTOCO | symbol, workingType, workingSide, workingPrice, workingQuantity, pendingSide, pendingQuantity, pendingAboveType | listClientOrderId, newOrderRespType, selfTradePreventionMode, workingClientOrderId, workingIcebergQty, workingTimeInForce, workingStrategyId, workingStrategyType, workingPegPriceType, workingPegOffsetType, workingPegOffsetValue, pendingAboveClientOrderId, pendingAbovePrice, pendingAboveStopPrice, pendingAboveTrailingDelta, pendingAboveIcebergQty, pendingAboveTimeInForce, pendingAboveStrategyId, pendingAboveStrategyType, pendingAbovePegPriceType, pendingAbovePegOffsetType, pendingAbovePegOffsetValue, pendingBelowType, pendingBelowClientOrderId, pendingBelowPrice, pendingBelowStopPrice, pendingBelowTrailingDelta, pendingBelowIcebergQty, pendingBelowTimeInForce, pendingBelowStrategyId, pendingBelowStrategyType, pendingBelowPegPriceType, pendingBelowPegOffsetType, pendingBelowPegOffsetValue, recvWindow | Yes |
/api/v3/sor/order (POST) |
New order using SOR | symbol, side, type, quantity | timeInForce, price, newClientOrderId, strategyId, strategyType, icebergQty, newOrderRespType, selfTradePreventionMode, recvWindow | Yes |
/api/v3/sor/order/test (POST) |
Test new order using SOR | symbol, side, type, quantity | computeCommissionRates, timeInForce, price, newClientOrderId, strategyId, strategyType, icebergQty, newOrderRespType, selfTradePreventionMode, recvWindow | Yes |
/api/v3/account (GET) |
Account information | None | omitZeroBalances, recvWindow | Yes |
/api/v3/account/commission (GET) |
Query Commission Rates | symbol | None | Yes |
/api/v3/allOrderList (GET) |
Query all Order lists | None | fromId, startTime, endTime, limit, recvWindow | Yes |
/api/v3/allOrders (GET) |
All orders | symbol | orderId, startTime, endTime, limit, recvWindow | Yes |
/api/v3/myAllocations (GET) |
Query Allocations | symbol | startTime, endTime, fromAllocationId, limit, orderId, recvWindow | Yes |
/api/v3/myFilters (GET) |
Query relevant filters | symbol | recvWindow | Yes |
/api/v3/myPreventedMatches (GET) |
Query Prevented Matches | symbol | preventedMatchId, orderId, fromPreventedMatchId, limit, recvWindow | Yes |
/api/v3/myTrades (GET) |
Account trade list | symbol | orderId, startTime, endTime, fromId, limit, recvWindow | Yes |
/api/v3/openOrderList (GET) |
Query Open Order lists | None | recvWindow | Yes |
/api/v3/order/amendments (GET) |
Query Order Amendments | symbol, orderId | fromExecutionId, limit, recvWindow | Yes |
/api/v3/rateLimit/order (GET) |
Query Unfilled Order Count | None | recvWindow | Yes |
Parameters
Common Parameters
- symbol: Symbol to query (e.g., BNBUSDT)
- symbols: List of symbols to query
- permissions: List of permissions to query
- showPermissionSets: Controls whether the content of the
permissionSetsfield is populated or not. Defaults totrue(e.g., true) - symbol: (e.g., BNBUSDT)
- fromId: ID to get aggregate trades from INCLUSIVE. (e.g., 1)
- startTime: Timestamp in ms to get aggregate trades from INCLUSIVE. (e.g., 1735693200000)
- endTime: Timestamp in ms to get aggregate trades until INCLUSIVE. (e.g., 1735693200000)
- limit: Default: 500; Maximum: 1000. (e.g., 500)
- timeZone: Default: 0 (UTC)
- recvWindow: The value cannot be greater than
60000. Supports up to three decimal places of precision (e.g., 6000.346) so that microseconds may be specified. (e.g., 5000) - timestamp: (e.g., 1)
- quantity: (e.g., 1)
- quoteOrderQty: (e.g., 1)
- price: (e.g., 400)
- newClientOrderId: A unique id among open orders. Automatically generated if not sent. Orders with the same
newClientOrderIDcan be accepted only when the previous one is filled, otherwise the order will be rejected. - strategyId: (e.g., 1)
- strategyType: The value cannot be less than
1000000. (e.g., 1) - stopPrice: Used with
STOP_LOSS,STOP_LOSS_LIMIT,TAKE_PROFIT, andTAKE_PROFIT_LIMITorders. (e.g., 1) - trailingDelta: See Trailing Stop order FAQ. (e.g., 1)
- icebergQty: Used with
LIMIT,STOP_LOSS_LIMIT, andTAKE_PROFIT_LIMITto create an iceberg order. (e.g., 1) - pegOffsetValue: Priceleveltopegthepriceto(max:100). SeePeggedOrdersInfo (e.g., 1)
- orderId: (e.g., 1)
- origClientOrderId:
- newQty:
newQtymust be greater than 0 and less than the order's quantity. (e.g., 1) - cancelNewClientOrderId: Used to uniquely identify this cancel. Automatically generated by default.
- cancelOrigClientOrderId: Either
cancelOrderIdorcancelOrigClientOrderIdmust be sent. If bothcancelOrderIdandcancelOrigClientOrderIdparameters are provided, thecancelOrderIdis searched first, then thecancelOrigClientOrderIdfrom that result is checked against that order. If both conditions are not met the request will be rejected. - cancelOrderId: Either
cancelOrderIdorcancelOrigClientOrderIdmust be sent. If bothcancelOrderIdandcancelOrigClientOrderIdparameters are provided, thecancelOrderIdis searched first, then thecancelOrigClientOrderIdfrom that result is checked against that order. If both conditions are not met the request will be rejected. (e.g., 1) - listClientOrderId: A unique Id for the entire orderList
- quantity: (e.g., 1)
- limitClientOrderId: A unique Id for the limit order
- price: (e.g., 1)
- limitStrategyId: (e.g., 1)
- limitStrategyType: The value cannot be less than
1000000. (e.g., 1) - limitIcebergQty: Used to make the
LIMIT_MAKERleg an iceberg order. (e.g., 1) - stopClientOrderId: A unique Id for the stop loss/stop loss limit leg
- stopPrice: (e.g., 1)
- stopStrategyId: (e.g., 1)
- stopStrategyType: The value cannot be less than
1000000. (e.g., 1) - stopLimitPrice: If provided,
stopLimitTimeInForceis required. (e.g., 1) - stopIcebergQty: Used with
STOP_LOSS_LIMITleg to make an iceberg order. (e.g., 1) - computeCommissionRates: Default:
falseSee Commissions FAQ to learn more. - orderListId: Either
orderListIdorlistClientOrderIdmust be provided (e.g., 1) - aboveClientOrderId: Arbitrary unique ID among open orders for the above order. Automatically generated if not sent
- aboveIcebergQty: Note that this can only be used if
aboveTimeInForceisGTC. (e.g., 1) - abovePrice: Can be used if
aboveTypeisSTOP_LOSS_LIMIT,LIMIT_MAKER, orTAKE_PROFIT_LIMITto specify the limit price. (e.g., 1) - aboveStopPrice: Can be used if
aboveTypeisSTOP_LOSS,STOP_LOSS_LIMIT,TAKE_PROFIT,TAKE_PROFIT_LIMIT. EitheraboveStopPriceoraboveTrailingDeltaor both, must be specified. (e.g., 1) - aboveTrailingDelta: See Trailing Stop order FAQ. (e.g., 1)
- aboveStrategyId: Arbitrary numeric value identifying the above order within an order strategy. (e.g., 1)
- aboveStrategyType: Arbitrary numeric value identifying the above order strategy. Values smaller than 1000000 are reserved and cannot be used. (e.g., 1)
- abovePegOffsetValue: (e.g., 1)
- belowClientOrderId: Arbitrary unique ID among open orders for the below order. Automatically generated if not sent
- belowIcebergQty: Note that this can only be used if
belowTimeInForceisGTC. (e.g., 1) - belowPrice: Can be used if
belowTypeisSTOP_LOSS_LIMIT,LIMIT_MAKER, orTAKE_PROFIT_LIMITto specify the limit price. (e.g., 1) - belowStopPrice: Can be used if
belowTypeisSTOP_LOSS,STOP_LOSS_LIMIT, TAKE_PROFITorTAKE_PROFIT_LIMITEither belowStopPrice or belowTrailingDelta or both, must be specified. (e.g., 1) - belowTrailingDelta: See Trailing Stop order FAQ. (e.g., 1)
- belowStrategyId: Arbitrary numeric value identifying the below order within an order strategy. (e.g., 1)
- belowStrategyType: Arbitrary numeric value identifying the below order strategy. Values smaller than 1000000 are reserved and cannot be used. (e.g., 1)
- belowPegOffsetValue: (e.g., 1)
- workingClientOrderId: Arbitrary unique ID among open orders for the working order. Automatically generated if not sent.
- workingPrice: (e.g., 1)
- workingQuantity: Sets the quantity for the working order. (e.g., 1)
- workingIcebergQty: This can only be used if
workingTimeInForceisGTC, or ifworkingTypeisLIMIT_MAKER. (e.g., 1) - workingStrategyId: Arbitrary numeric value identifying the working order within an order strategy. (e.g., 1)
- workingStrategyType: Arbitrary numeric value identifying the working order strategy. Values smaller than 1000000 are reserved and cannot be used. (e.g., 1)
- workingPegOffsetValue: (e.g., 1)
- pendingClientOrderId: Arbitrary unique ID among open orders for the pending order. Automatically generated if not sent.
- pendingPrice: (e.g., 1)
- pendingStopPrice: (e.g., 1)
- pendingTrailingDelta: (e.g., 1)
- pendingIcebergQty: This can only be used if
pendingTimeInForceisGTCor ifpendingTypeisLIMIT_MAKER. (e.g., 1) - pendingStrategyId: Arbitrary numeric value identifying the pending order within an order strategy. (e.g., 1)
- pendingStrategyType: Arbitrary numeric value identifying the pending order strategy. Values smaller than 1000000 are reserved and cannot be used. (e.g., 1)
- pendingPegOffsetValue: (e.g., 1)
- pendingAboveClientOrderId: Arbitrary unique ID among open orders for the pending above order. Automatically generated if not sent.
- pendingAbovePrice: Can be used if
pendingAboveTypeisSTOP_LOSS_LIMIT,LIMIT_MAKER, orTAKE_PROFIT_LIMITto specify the limit price. (e.g., 1) - pendingAboveStopPrice: Can be used if
pendingAboveTypeisSTOP_LOSS,STOP_LOSS_LIMIT,TAKE_PROFIT,TAKE_PROFIT_LIMIT(e.g., 1) - pendingAboveTrailingDelta: See Trailing Stop FAQ (e.g., 1)
- pendingAboveIcebergQty: This can only be used if
pendingAboveTimeInForceisGTCor ifpendingAboveTypeisLIMIT_MAKER. (e.g., 1) - pendingAboveStrategyId: Arbitrary numeric value identifying the pending above order within an order strategy. (e.g., 1)
- pendingAboveStrategyType: Arbitrary numeric value identifying the pending above order strategy. Values smaller than 1000000 are reserved and cannot be used. (e.g., 1)
- pendingAbovePegOffsetValue: (e.g., 1)
- pendingBelowClientOrderId: Arbitrary unique ID among open orders for the pending below order. Automatically generated if not sent.
- pendingBelowPrice: Can be used if
pendingBelowTypeisSTOP_LOSS_LIMITorTAKE_PROFIT_LIMITto specify limit price (e.g., 1) - pendingBelowStopPrice: Can be used if
pendingBelowTypeisSTOP_LOSS,STOP_LOSS_LIMIT, TAKE_PROFIT or TAKE_PROFIT_LIMIT. EitherpendingBelowStopPriceorpendingBelowTrailingDeltaor both, must be specified. (e.g., 1) - pendingBelowTrailingDelta: (e.g., 1)
- pendingBelowIcebergQty: This can only be used if
pendingBelowTimeInForceisGTC, or ifpendingBelowTypeisLIMIT_MAKER. (e.g., 1) - pendingBelowStrategyId: Arbitrary numeric value identifying the pending below order within an order strategy. (e.g., 1)
- pendingBelowStrategyType: Arbitrary numeric value identifying the pending below order strategy. Values smaller than 1000000 are reserved and cannot be used. (e.g., 1)
- pendingBelowPegOffsetValue: (e.g., 1)
- pendingQuantity: Sets the quantity for the pending order. (e.g., 1)
- omitZeroBalances: When set to
true, emits only the non-zero balances of an account. Default value:false - fromAllocationId: (e.g., 1)
- timestamp
how to use spot
How to use spot on Cursor
AI-first code editor with Composer
1
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add spot
2
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
$npx skills add https://github.com/binance/binance-skills-hub --skill spot
The skills CLI fetches spot from GitHub repository binance/binance-skills-hub and configures it for Cursor.
3
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
◆ Which agents do you want to install to?
│
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4
Verify installation
Confirm successful installation by checking the skill directory location:
.cursor/skills/spot
Reload or restart Cursor to activate spot. Access the skill through slash commands (e.g., /spot) or your agent's skill management interface.
⚠
Security & Verification Notice
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 development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
✓
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
✓
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
✓
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
✓
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
general reviews
Ratings
4.5★★★★★32 reviews- ★★★★★Maya Huang· Dec 20, 2024
Solid pick for teams standardizing on skills: spot is focused, and the summary matches what you get after install.
- ★★★★★Dhruvi Jain· Dec 16, 2024
spot has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Olivia Okafor· Sep 25, 2024
spot fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Amina Patel· Sep 17, 2024
I recommend spot for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Sakshi Patil· Sep 5, 2024
Keeps context tight: spot is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Chaitanya Patil· Aug 24, 2024
Registry listing for spot matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Noah Ndlovu· Aug 16, 2024
spot is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Kofi Gupta· Aug 8, 2024
spot reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Naina Desai· Jul 23, 2024
Registry listing for spot matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Piyush G· Jul 15, 2024
spot reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 32
1 / 4