Agent skill · ma08
birdclaw
Use Birdclaw for cache-first X/Twitter data workflows, especially followers/following, unfollowers, mutuals, non-mutual following, top followers, leadgen lists, local timeline/DM/search analysis, backups, or PR/code work in the Birdclaw repo. Prefer this skill over direct xurl whenever Birdclaw can answer from its local SQLite cache or explicit sync workflow; use xurl only for auth setup, unsupported endpoints, or intentional live API calls.
What it needs
About 3k tokens when loaded.
What this skill does
Birdclaw Birdclaw is the preferred interface for X/Twitter analysis because it stores local SQLite data and avoids unnecessary live API reads. Use direct xurl only when Birdclaw cannot answer the task or when the user explicitly wants raw X API behavior. Core Rule Prefer birdclaw / pnpm cli cache reads before any live X API call. Treat birdclaw graph commands as cache-only and safe for repeated analysis. Treat birdclaw sync followers following --yes as a live-read operation unless it clearly reuses fresh cache. Do not pass --refresh unless the user asked for a live refresh or current data is required. Ask before any social write action. Birdclaw follow-graph work is read-only; posting, following, unfollowing, blocking, muting, liking, reposting, DMing, and media upload still need explicit approval. Never read or print ~/.xurl, app secrets, tokens, or repo .env values. Local Setup Canonical checkout on this machine: ~/pro/birdclaw. Run Birdclaw commands from that checkout. Use the repo-pinned runtime before validation or development: Use pnpm cli ... in the repo. In installed contexts, birdclaw ... may also exist; prefer the repo command when working from the checkout. Cache-First Workflow 1. Inspect existing local state first: 2. If account targeting matters and the default account is uncertain, inspect local accounts without live API calls: 3. Use --account <accountid> for personal/account-specific analysis once the account is known. 4. Save CSV/Markdown exports under the active task folder, not inside the Birdclaw repo, unless the user explicitly asks for repo changes. Live Sync Workflow Use live sync only when the user asks for a fresh/live check, or when local cache is missing/stale and the user’s task requires current data. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills ma08/birdclaw