Sub-account request on Binance using authenticated API endpoints. Requires API key and secret key for certain endpoints. Return the result in JSON format.
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
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
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
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
Submit your Claude Code skill and start earning
epx add binance/binance-skills-hub --skill sub-accountCompatible with
Supported agents
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionsub-accountExecute the skills CLI command in your project's root directory to begin installation:
epx add binance/binance-skills-hub --skill sub-accountFetches sub-account from binance/binance-skills-hub 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:
.cursor/skills/sub-account
Restart Cursor to activate sub-account. Access via /sub-accountin your agent's command palette.
Learn more:View source on GitHubSkills CLI docsAbout CursorWhat are agent skills?
Time estimate: 30-60 minutes to see productivity improvements
Prerequisites
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ 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.
grill-me
mattpocock/skills · Productivity · same category
deslop
cursor/plugins · Productivity · same category
premortem
parcadei/continuous-claude-v3 · Productivity · same category
find-skills
kimyx0207/findskill · Productivity · same category
smart-ocr
claude-office-skills/skills · Productivity · same category
filament-pro
marcelorodrigo/agent-skills · Productivity · same category
I recommend sub-account for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
sub-account is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Useful defaults in sub-account — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Solid pick for teams standardizing on skills: sub-account is focused, and the summary matches what you get after install.
sub-account has been reliable in day-to-day use. Documentation quality is above average for community skills.
sub-account reduced setup friction for our internal harness; good balance of opinion and flexibility.
I recommend sub-account for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
sub-account is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
sub-account reduced setup friction for our internal harness; good balance of opinion and flexibility.
Useful defaults in sub-account — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 72