neynar_skill

This skill helps you read Farcaster feeds, lookup users, post casts, and search content via Neynar API.
  • Python

51

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill bankrbot/moltbot-skills --skill neynar

  • SKILL.md5.7 KB

Overview

This skill connects an agent to Farcaster via the Neynar API, enabling reading feeds, searching users and casts, and performing authenticated actions like posting, liking, and following. It requires a NEYNAR_API_KEY in config and a signerUuid for write operations. Use it to integrate Farcaster data and interactions into automation, monitoring, or social workflows.

How this skill works

The skill calls Neynar REST endpoints to look up users, fetch feeds (user, channel, trending, following), search casts and users, retrieve specific casts, and perform actions (post, like, recast, follow). Read-only calls use the API key; write calls require a signer UUID managed by Neynar. Responses are JSON; the skill extracts key fields (fid, username, cast text, timestamps) for concise output.

When to use it

  • Read a user’s Farcaster feed or a channel feed for monitoring or aggregation
  • Search casts or users to discover conversations and participants
  • Post casts, replies, or embeds from an automated agent (requires signer)
  • React to or recast content programmatically as part of engagement workflows
  • Follow or unfollow users as part of account management or recommendation systems

Best practices

  • Store NEYNAR_API_KEY and signerUuid in a secure config and never expose keys in logs
  • Cache user lookups (FIDs are permanent) and batch requests via bulk endpoints to reduce rate usage
  • Limit polling frequency and respect X-RateLimit-Remaining headers; implement exponential backoff on 429 responses
  • Prefer channel-targeted posts for better contextual reach and use authentic, human-like content for engagement
  • Validate signer permissions before write operations and use managed signers to simplify key custody

Example use cases

  • Monitor the /base channel for breaking on-chain announcements and surface them to an ops dashboard
  • Automate cross-posting of product release notes from your CI pipeline to Farcaster casts
  • Create a discovery tool that searches casts for keywords and surfaces active contributors to recruit or collaborate
  • Run a bot that replies to mentions or thanks users after sign-up using the signer for authenticated replies
  • Bulk fetch user metadata (fid, follower counts) for analytics and community health reports

FAQ

An NEYNAR_API_KEY is required for all requests; a signerUuid is required for writes (post, like, follow).

How do I avoid rate limits?

Use bulk endpoints, cache user lookups, respect X-RateLimit-Remaining, and implement exponential backoff on 429 responses.

How long until a posted cast appears on Warpcast?

Casts usually propagate in seconds, but indexing may sometimes take longer; check the returned cast hash and Warpcast if needed.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
neynar skill by bankrbot/moltbot-skills | VeilStrat