x-bookmarks
Skill1 starsChanged 17 days agoMITView on GitHub
Fetch, summarize, and manage X/Twitter bookmarks via the `bird` CLI. Use when: (1) user says \"check my bookmarks\", \"what did I bookmark\", \"bookmark digest\", \"summarize my bookmarks\", \"x bookmarks\", \"twitter bookmarks\", (2) user wants a periodic digest of saved tweets, (3) user wants to categorize, search, or analyze their bookmarks, (4) scheduled bookmark digests via cron. Requires `bird` CLI (npm i -g bird-cli) and X/Twitter authentication via browser cookies or manual tokens.
- Reads credentials
- Installs packages
2 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- Atmoskun/claude-skillstheir own version, first seen Nov 16, 2026
- sharbelxyz/x-bookmarksedited, first seen Oct 8, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- sharbelxyz/x-bookmarks★ 28945% same
Wrote their own version · 1
- Atmoskun/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository199 other files it gives its agents.
- activecampaignSkill
- adcp-advertisingSkill
- admapixSkill
- aegis-auditSkill
- afrexai-compliance-auditSkill
- afrexai-seo-content-engineSkill
- agent-browserSkill
- agentic-codingSkill
- agent-overflowSkill
- agent-skills-toolsSkill
- ai-ppt-generatorSkill
- airdrop-hunterSkill
- ai-web-automationSkill
- alicloud-ai-video-wan-r2vSkill
- alpha-finderSkill
- amap-trafficSkill
- amazon-product-apiSkill
- apertureSkill
- api-developmentSkill
- api-gatewaySkill
- asterSkill
- auto-replySkill
- auto-updaterSkill
- aviation-weatherSkill
- awwwards-designSkill
- base-8004Skill
- bioskillsSkill
- brainrepoSkill
- browserless-agentSkill
- browser-secureSkill
- btc15-autonomous-marketSkill
- buy-anythingSkill
- byteroverSkill
- cal-com-automationSkill
- capability-evolverSkill
- catalogSkill
- chargebeeSkill
- clawcostSkill
- clawdbot-documentation-expertSkill
- clawdbot-for-vcsSkill
- clawddocsSkill
- claw-syncSkill
- claw-trader-liteSkill
- clean-codeSkill
- cloudphoneSkill
- cls-certifySkill
- codebergSkill
- code-mentorSkill
- commit-analyzerSkill
- competitor-analysis-reportSkill
- content-ideas-generatorSkill
- content-ideasSkill
- contract-generatorSkill
- conventional-commitsSkill
- copywritingSkill
- crypto-payments-ecommerceSkill
- custom-smtp-senderSkill
- dashboard-manager2Skill
- data-analystSkill
- docker-sandboxSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 3 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Core philosophy: Don't just summarize — propose actions the agent can execute.
- Very specific: line 44
If user has a .env.bird file or env vars AUTH_TOKEN/CT0, source them first: source .env.bird
- Distinctive: line 103
When user asks for content ideas from bookmarks:
- Distinctive: line 111
When user has enough bookmark history:
- Very specific: line 136
Start with -n 20 for quick digests, --all for deep analysis
- Very specific: line 137
Use --include-parent to get thread context for replies
- Very specific: line 139
Add --sort-chronological for time-ordered output
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
X Bookmarks
Turn X/Twitter bookmarks from a graveyard of good intentions into actionable work.
Core philosophy: Don't just summarize — propose actions the agent can execute.
Prerequisites
- bird CLI:
npm install -g bird-cli(v0.8+) - Auth (one of):
--chrome-profile <name>— auto-extracts cookies from Chrome (recommended)--firefox-profile <name>— Firefox equivalent- Manual:
--auth-token <token> --ct0 <token>from browser dev tools - Config:
~/.config/bird/config.json5with{ chromeProfile: "Default" }
- See references/auth-setup.md for detailed setup guide
Fetching Bookmarks
# Latest 20 bookmarks (default)
bird bookmarks --json
# Specific count
bird bookmarks -n 50 --json
# All bookmarks (paginated)
bird bookmarks --all --json
# With thread context
bird bookmarks --include-parent --thread-meta --json
# With Chrome cookie auth
bird --chrome-profile "Default" bookmarks --json
# With manual tokens
bird --auth-token "$AUTH_TOKEN" --ct0 "$CT0" bookmarks --jsonIf user has a .env.bird file or env vars AUTH_TOKEN/CT0, source them first: source .env.bird
JSON Output Format
Each bookmark returns:
{
"id": "tweet_id",
"text": "tweet content",
"createdAt": "Wed Feb 11 01:00:06 +0000 2026",
"replyCount": 46,
"retweetCount": 60,
"likeCount": 801,
"author": { "username": "handle", "name": "Display Name" },
"media": [{ "type": "photo|video", "url": "..." }],
"quotedTweet": { ... }
}Core Workflows
1. Action-First Digest (Primary Use Case)
The key differentiator: don't just summarize, propose actions the agent can execute.
- Fetch bookmarks:
bird bookmarks -n <count> --json - Parse and categorize by topic (auto-detect: crypto, AI, marketing, tools, personal, etc.)
- For EACH category, propose specific actions:
- Tool/repo bookmarks → "I can test this, set it up, or analyze the code"
- Strategy/advice bookmarks → "Here are the actionable steps extracted — want me to implement any?"
- News/trends → "This connects to [user's work]. Here's the angle for content"
- Content ideas → "This would make a great tweet/video in your voice. Here's a draft"
- Questions/discussions → "I can research this deeper and give you a summary"
- Flag stale bookmarks (>2 weeks old) — "Use it or lose it"
- Deliver categorized digest with actions
Format output as:
📂 CATEGORY (count)
• Bookmark summary (@author)
→ 🤖 I CAN: [specific action the agent can take]2. Scheduled Digest (Cron)
Set up a recurring bookmark check. Suggest this cron config to the user:
Schedule: daily or weekly
Payload: "Check my X bookmarks for new saves since last check.
Fetch bookmarks, compare against last digest, summarize only NEW ones.
Categorize and propose actions. Deliver to me."Track state by saving the most recent bookmark ID processed. Store in workspace:
memory/bookmark-state.json → { "lastSeenId": "...", "lastDigestAt": "..." }
3. Content Recycling
When user asks for content ideas from bookmarks:
- Fetch recent bookmarks
- Identify high-engagement tweets (>500 likes) with frameworks, tips, or insights
- Rewrite key ideas in the user's voice (if voice data available)
- Suggest posting times based on the bookmark's original engagement
4. Pattern Detection
When user has enough bookmark history:
- Fetch all bookmarks (
--all) - Cluster by topic/keywords
- Report: "You've bookmarked N tweets about [topic]. Want me to go deeper?"
- Suggest: research reports, content series, or tools based on patterns
5. Bookmark Cleanup
For stale bookmarks:
- Identify bookmarks older than a threshold (default: 30 days)
- For each: extract the TL;DR and one actionable takeaway
- Present: "Apply it today or clear it"
- User can unbookmark via:
bird unbookmark <tweet-id>
Error Handling
| Error | Cause | Fix |
| "No Twitter cookies found" | Not logged into X in browser | Log into x.com in Chrome/Firefox |
| EPERM on Safari cookies | macOS permissions | Use Chrome or Firefox instead |
| Empty results | Cookies expired | Re-login to x.com, retry |
| Rate limit | Too many requests | Wait and retry, use --max-pages to limit |
Tips
- Start with
-n 20for quick digests,--allfor deep analysis - Use
--include-parentto get thread context for replies - Bookmark folders are supported via
--folder-id <id> - Add
--sort-chronologicalfor time-ordered output
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.

