Farcaster social protocol via Neynar API - read feeds, post casts, follow users
70
61%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./src/skills/bundled/farcaster/SKILL.mdQuality
Discovery
50%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description effectively communicates specific capabilities within a well-defined niche (Farcaster/Neynar), making it distinctive. However, it lacks explicit trigger guidance ('Use when...') which is critical for Claude to know when to select this skill. The trigger terms are domain-specific but may miss users who don't know Farcaster terminology.
Suggestions
Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user mentions Farcaster, casts, Neynar, or decentralized social media'
Include broader trigger terms users might naturally say like 'web3 social', 'decentralized social network', or 'crypto social media' to improve discoverability
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'read feeds, post casts, follow users'. These are clear, actionable capabilities within the Farcaster domain. | 3 / 3 |
Completeness | Describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance. Per rubric guidelines, missing explicit trigger guidance caps completeness at 2, and this has no trigger guidance at all. | 1 / 3 |
Trigger Term Quality | Includes domain-specific terms like 'Farcaster', 'Neynar API', 'casts', 'feeds' but misses common variations users might say like 'social media', 'decentralized social', or 'web3 social'. | 2 / 3 |
Distinctiveness Conflict Risk | Very clear niche - Farcaster is a specific protocol and Neynar is a specific API. Unlikely to conflict with other social media or API skills due to the distinct terminology. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, concise skill that efficiently documents Farcaster/Neynar API interactions. Its main weakness is that the commands appear to be custom slash commands rather than executable code Claude can run directly, and it lacks validation steps for setup and signer configuration.
Suggestions
Add executable curl or Python examples showing actual Neynar API calls, not just slash command syntax
Include a validation step to verify API key is configured correctly (e.g., a simple test request)
Add guidance on obtaining and configuring the NEYNAR_SIGNER_UUID for write operations
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations of what Farcaster is or how APIs work. Every line serves a purpose - setup, commands, examples, and limits. | 3 / 3 |
Actionability | Provides clear command syntax and examples, but these appear to be custom slash commands rather than executable code. Missing actual API call examples or curl commands that Claude could directly execute. | 2 / 3 |
Workflow Clarity | Setup steps are clear, but there's no validation checkpoint for API key configuration. For write operations requiring a signer, there's no guidance on how to obtain/configure the signer or verify it's working before attempting posts. | 2 / 3 |
Progressive Disclosure | For a skill of this size (~60 lines), the organization is excellent. Clear sections for setup, commands by category, examples, and limits. No need for external file references given the scope. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
2a8c94e
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.