xurl-best-practices
Skill1 starsChanged 5 months agoMITView on GitHub
Best practices and guidelines for using xurl CLI tool effectively with X (Twitter) API, including rate limits, content guidelines, optimal posting times, and error handling. Use when working with xurl for automated posting, engagement, or any Twitter API operations to avoid rate limits, content blocks, and optimize performance.
In this repository8 other files it gives its agents.
- ai-cognitive-loadSkill
- android-controlSkill
- autonomous-researchSkill
- cron-task-specSkill
- git-worktreeSkill
- hermes-pr-guidelinesSkill
- jj-workspaceSkill
- knowledge-explorerSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 29
After bulk operations (deletes): 1 hour before posting
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
xurl Best Practices
Guidelines for effective automated posting with xurl based on real-world usage patterns.
Critical Rules
1. Emoji Limitations
❌ FORBIDDEN:
- Excessive emoji (>3 per tweet)
- Multiple emoji in lists or formatting
- Decorative emoji in every line
✅ ALLOWED:
- 1-2 emoji per tweet maximum
- Functional emoji only (e.g., one ✅ for checklists)
Why: Twitter API blocks tweets with excessive emoji with 403 Forbidden error.
2. Rate Limiting
Minimum intervals:
- Between posts: 30 minutes minimum
- After bulk operations (deletes): 1 hour before posting
- Daily post limit: 50 tweets/day (recommended safe limit)
Rate limit recovery:
403 Forbidden → Wait 60-90 minutes → Retry3. Content Guidelines
Avoid:
- Marketing-heavy language
- Excessive formatting
- ALL CAPS
- Repetitive content
- Hashtags at start of tweet
Best practices:
- Clear, concise language
- 1-2 relevant hashtags at end
- Natural conversational tone
- Value-focused content
Posting Strategy
Optimal Times (Beijing Time)
Weekdays:
- Morning: 10:00-11:00
- Afternoon: 15:00-16:00
- Evening: 20:00-21:00
Weekends:
- Morning: 10:00-11:00
- Evening: 18:00-19:00
Posting Frequency
- Minimum: 1 post per day
- Recommended: 2-3 posts per day
- Maximum: 5 posts per day (with 2+ hour gaps)
Content Mix
Week 1 example:
- Day 1: Project introduction
- Day 2: Technical tip
- Day 3: Official announcement
- Day 4: Case study/user story
- Day 5: Light/engaging content
- Day 6: Industry insight
- Day 7: Engagement/poll
Error Handling
403 Forbidden
Causes:
- Rate limit exceeded
- Content flagged (excessive emoji, spam-like)
- Short interval after bulk operations
Solution:
# Check if rate limited
xurl whoami # If this works, it's content filtering
# For rate limits
sleep 3600 # Wait 1 hour
# For content filtering
# Remove emoji, simplify language, retry429 Too Many Requests
Solution:
# Wait until reset (check headers)
sleep 900 # 15 minutes defaultAutomated Posting Workflow
Safe Posting Script
Use scripts/safe_post.sh:
# Post with automatic rate limit handling
scripts/safe_post.sh "Your tweet text here"
# With media
scripts/safe_post.sh "Check this out" --media photo.jpgBatch Posting Strategy
For multiple tweets:
- Schedule, don't spam:
# Post tweet 1 xurl post "First tweet" # Wait 30 minutes sleep 1800 # Post tweet 2 xurl post "Second tweet" - Use background timers:
# Schedule tweets with exec background exec command:"xurl post 'Tweet at 3pm'" background:true
Content Templates
Project Announcement
Just open sourced [PROJECT NAME]
A [BRIEF DESCRIPTION] that [VALUE PROPOSITION]
Install:
[INSTALL COMMAND]
Features:
- [Feature 1]
- [Feature 2]
- [Feature 3]
GitHub: [LINK]
#Hashtag1 #Hashtag2Technical Tip
[TOPIC] tip:
[Problem statement]
Example:
- [Example 1]
- [Example 2]
[Solution]
#Hashtag1 #Hashtag2Monitoring & Metrics
Track Performance
# Check your recent posts
xurl timeline -n 10
# Check mentions
xurl mentions -n 20
# Check engagement (likes, retweets)
xurl likes -n 10Success Metrics
- Week 1: 5-10 likes per tweet average
- Month 1: 20-50 likes per tweet average
- Engagement rate: >5% of followers
Advanced Usage
For detailed rate limits, content filtering rules, and advanced patterns:
- Rate limits: See references/rate-limits.md
- Content guidelines: See references/content-guidelines.md
Common Patterns
Project Launch Sequence
- Teaser (Day 1): "Working on something exciting..."
- Hint (Day 2): Technical insight or tip related to project
- Launch (Day 3): Official announcement with GitHub link
- Follow-up (Day 4-7): Case studies, user stories
Engagement Strategy
# Morning: Post content
xurl post "New blog post: [TITLE] [LINK] #Tech"
# Afternoon: Engage with replies
xurl mentions -n 20
# Evening: Share insights
xurl post "Key takeaway from today: [INSIGHT]"Quick Reference
| Action | Command | Notes |
| Safe post | scripts/safe_post.sh "text" | Auto rate limit handling |
| Check limits | xurl whoami | Verify auth status |
| Wait after delete | sleep 3600 | 1 hour after bulk delete |
| Max emoji | 1-2 per tweet | Or 403 Forbidden |
| Min post interval | 30 minutes | Avoid rate limits |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

