square-post▌
binance/binance-skills-hub · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Post text content to Binance Square with API key authentication and error handling.
- ›Supports pure text posts with hashtag support; constructs shareable post URLs on success
- ›Requires X-Square-OpenAPI-Key header authentication; agent prompts for missing credentials before attempting posts
- ›Handles 20+ error codes including sensitive content detection, daily post limits, identity verification requirements, and account bans
- ›Agent optimizes raw user input for readability and requests co
Square Post Skill
Overview
Post text content to Binance Square.
API: Add Content
Method: POST
URL:
https://www.binance.com/bapi/composite/v1/public/pgc/openApi/content/add
Request Headers:
| Header | Required | Description |
|---|---|---|
| X-Square-OpenAPI-Key | Yes | Square OpenAPI Key |
| Content-Type | Yes | application/json |
| clienttype | Yes | binanceSkill |
Request Body:
| Field | Type | Required | Description |
|---|---|---|---|
| bodyTextOnly | string | Yes | Post content text |
Example Request
curl -X POST 'https://www.binance.com/bapi/composite/v1/public/pgc/openApi/content/add' \
-H 'X-Square-OpenAPI-Key: your_api_key' \
-H 'Content-Type: application/json' \
-H 'clienttype: binanceSkill' \
-d '{
"bodyTextOnly": "BTC looking bullish today!"
}'
Response Example
{
"code": "000000",
"message": null,
"data": {
"id": "content_id_here"
}
}
Response Fields
| Field | Type | Description |
|---|---|---|
| code | string | "000000" = success |
| message | string | Error message (null on success) |
| data.id | string | Created content ID |
Post URL Format
On success, construct the post URL:
https://www.binance.com/square/post/{id}
Example: If data.id is 298177291743282, the post URL is:
https://www.binance.com/square/post/298177291743282
Error Handling
| Code | Description |
|---|---|
| 000000 | Success |
| 10004 | Network error. Please try again |
| 10005 | Only allowed for users who have completed identity verification |
| 10007 | Feature unavailable |
| 20002 | Detected sensitive words |
| 20013 | Content length is limited |
| 20020 | Publishing empty content is not supported |
| 20022 | Detected sensitive words (with risk segments) |
| 20041 | Potential security risk with the URL |
| 30004 | User not found |
| 30008 | Banned for violating platform guidelines |
| 220003 | API Key not found |
| 220004 | API Key expired |
| 220009 | Daily post limit exceeded for OpenAPI |
| 220010 | Unsupported content type |
| 220011 | Content body must not be empty |
| 2000001 | Account permanently blocked from posting |
| 2000002 | Device permanently blocked from posting |
Authentication
Required Header
| Header | Required | Description |
|---|---|---|
| X-Square-OpenAPI-Key | Yes | API key for Square posting |
Security
Never Display Full Keys
When showing credentials to users:
- X-Square-OpenAPI-Key: Show first 5 + last 4 characters:
abc12...xyz9
Listing Accounts
When listing accounts, show names and description only — never full keys:
Accounts:
* default (Default account for Square posting)
Agent Behavior
- Check key before API calls: Verify that X-Square-OpenAPI-Key is configured and not the placeholder
your_api_key - Prompt for key if missing: If key is not configured, ask user to provide their API Key first
- Prompt for content if missing: If user triggers posting but doesn't provide specific content, ask what they want to post
- Never display full keys: Only show first 5 + last 4 characters (e.g.,
abc12...xyz9) - Store provided keys: When user provides a new key, update the Accounts section in this file
- Optimize content before posting:
- Polish user's raw input for better readability
- Do NOT auto-add hashtags (#xxx) during optimization — keep any hashtags the user wrote, but never add new ones
- Show optimized content and ask user to choose: use optimized version or post original text
- Return post URL on success: After successful post, return the URL
https://www.binance.com/square/post/{id} - Handle missing id: If code is
000000butdata.idis empty or missing, inform user that post may have succeeded but URL is unavailable, suggest checking Square page manually
Notes
- Only pure text posts are supported currently
- Check daily post limit to avoid 220009 error
How to use square-post on Cursor
AI-first code editor with Composer
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 square-post
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches square-post from GitHub repository binance/binance-skills-hub and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate square-post. Access the skill through slash commands (e.g., /square-post) 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.
Ratings
4.7★★★★★46 reviews- ★★★★★Neel Khanna· Dec 24, 2024
Useful defaults in square-post — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Aditi Huang· Dec 12, 2024
I recommend square-post for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Advait Khan· Dec 4, 2024
square-post reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Chinedu Bansal· Nov 23, 2024
We added square-post from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Rahul Santra· Nov 15, 2024
square-post fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Amina Gupta· Nov 15, 2024
I recommend square-post for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Kaira Smith· Nov 3, 2024
Useful defaults in square-post — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Meera Kim· Oct 22, 2024
Registry listing for square-post matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Advait Harris· Oct 14, 2024
Keeps context tight: square-post is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Pratham Ware· Oct 6, 2024
square-post has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 46