agentsclimarketplace
Sign in

X bookmarks agent skill

Skill eugenepyvovarov/mcpbundler-agent-skills-marketplace/x-bookmarks-agent-skill

Read X/Twitter bookmarks using the bird CLI, verify the active account via `bird whoami`, and return bookmarks as JSON. Use when the user asks to list, search, summarize, or export X bookmarks, or when you must validate the active X account before fetching bookmarks.From its SKILL.md

Install
npx -y skills add eugenepyvovarov/mcpbundler-agent-skills-marketplace --skill x-bookmarks-agent-skill

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 12 stars12 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.6 KB, 590 tokens by cl100k_base, as published. Nobody here has run it

X Bookmarks Manager

Overview

Fetch X bookmarks via a local bird CLI install and return JSON for the agent to summarize or filter.

Workflow (agent-driven)

  1. Ensure bird is installed locally via scripts/setup.sh (installs with npm into .skills-data).
  2. Ensure BIRD_EXPECTED_USER is set in .skills-data/x-bookmarks-manager/.env.
  3. Run scripts/x-bookmarks to validate the account and output JSON.
  4. Parse or summarize the JSON for the user.

Commands

  • scripts/x-bookmarks: validate bird whoami and print bird bookmarks --json.
  • scripts/setup.sh: install bird in .skills-data/x-bookmarks-manager/venv/node_modules/.bin/bird and create .env.

Output

  • Raw JSON from bird bookmarks --json on stdout.

Account safety

  • Always run bird whoami before fetching bookmarks.
  • If the active account does not match BIRD_EXPECTED_USER, stop and ask the user to fix login or update .env.

Local data and env

  • Store all mutable state under <project_root>/.skills-data/<skill-name>/.
  • Keep config and registries in .skills-data/<skill-name>/ (for example: config.json, <feature>.json).
  • Use .skills-data/<skill-name>/.env for SKILL_ROOT, SKILL_DATA_DIR, and any per-skill env keys.
  • Install local tools into .skills-data/<skill-name>/bin and prepend it to PATH when needed.
  • Install dependencies under .skills-data/<skill-name>/venv:
    • Python: .skills-data/<skill-name>/venv/python
    • Node: .skills-data/<skill-name>/venv/node_modules
    • Go: .skills-data/<skill-name>/venv/go (modcache, gocache)
    • PHP: .skills-data/<skill-name>/venv/php (cache, vendor)
  • Write logs/cache/tmp under .skills-data/<skill-name>/logs, .skills-data/<skill-name>/cache, .skills-data/<skill-name>/tmp.
  • Keep automation in <skill-root>/scripts and read SKILL_DATA_DIR (default to <project_root>/.skills-data/<skill-name>/).
  • Do not write outside <skill-root> and <project_root>/.skills-data/<skill-name>/ unless the user requests it.

Notes

  • bird is installed under .skills-data/x-bookmarks-manager/venv/node_modules/.bin/bird and invoked directly.
  • Network access is required to download bird from npm on first setup.
  • If bird is installed manually (npm/pnpm/bun), set BIRD_BIN in .env to the correct path.
  • If bird is not authenticated, ask the user to log in with bird and retry.

What ships with it: 5 files

214.0 KB alongside SKILL.md, 1 of them executable

assets/

scripts/

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.