farcaster

Farcaster social protocol via Neynar API - read feeds, post casts, follow users

Quality

58%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./src/skills/bundled/farcaster/SKILL.md

Quality

Discovery

67%

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 is concise and specific about its domain (Farcaster via Neynar API) with clear concrete actions listed. Its main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill. The trigger terms are adequate but could benefit from broader natural language variations.

Suggestions

Add a 'Use when...' clause, e.g., 'Use when the user asks about Farcaster, posting casts, reading Farcaster feeds, interacting with the Neynar API, or working with decentralized social media.'

Include additional natural trigger terms users might say, such as 'Warpcast', 'decentralized social', 'social graph', 'reply to cast', or 'Farcaster timeline'.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'read feeds', 'post casts', 'follow users', and names the specific protocol (Farcaster) and API (Neynar).	3 / 3
Completeness	Clearly answers 'what does this do' (read feeds, post casts, follow users via Neynar API on Farcaster), but lacks an explicit 'Use when...' clause or equivalent trigger guidance, which caps this at 2 per the rubric.	2 / 3
Trigger Term Quality	Includes domain-specific terms like 'Farcaster', 'Neynar API', 'casts', 'feeds', and 'follow users', but misses common variations users might say such as 'social media posting', 'timeline', 'reply', or 'Warpcast'. The term 'casts' is Farcaster-specific jargon that users may or may not use.	2 / 3
Distinctiveness Conflict Risk	Highly distinctive due to the specific mention of 'Farcaster' and 'Neynar API', which are niche enough to be clearly distinguishable from other social media or API skills.	3 / 3
	Total	10 / 12 Passed

Implementation

50%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill provides a clean command reference for Farcaster/Neynar interaction but falls short on actionability — the '/fc' commands assume a tool exists without explaining its origin or installation. The Features section is redundant, and write operations lack validation/error handling guidance. The skill would benefit from executable code examples and clearer setup instructions for the signer.

Suggestions

Add executable code examples (e.g., curl commands or Python requests) showing actual API calls, or clarify what tool provides the '/fc' command and how to install it.

Add a workflow for obtaining a signer UUID, since write operations depend on it but no guidance is provided.

Remove the redundant 'Features' section — it restates what the commands already demonstrate.

Add validation/error handling guidance for write operations (e.g., how to confirm a cast was posted, what errors look like).

Dimension	Reasoning	Score
Conciseness	Mostly efficient, but the 'Features' section at the end is redundant — it just restates what the commands section already shows. The rate limits section adds marginal value. Otherwise reasonably lean.	2 / 3
Actionability	Provides clear CLI-style commands and examples, but lacks any actual executable code (no curl commands, no API call examples, no code snippets showing how to make requests). The '/fc' commands imply a pre-existing CLI tool but don't explain how to install or invoke it, leaving gaps in executability.	2 / 3
Workflow Clarity	Setup and command usage are listed but there's no workflow for multi-step processes. Write operations require a signer UUID but there's no guidance on how to obtain one, no validation steps for confirming posts succeeded, and no error handling guidance.	2 / 3
Progressive Disclosure	Content is reasonably organized with clear sections, but everything is in one file with no references to deeper documentation. The commands section could benefit from linking to detailed API docs or a separate reference file for advanced usage patterns.	2 / 3
	Total	8 / 12 Passed

Validation

90%

Warnings & errors only

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

Repository: alsk1992/CloddsBot
Commit: e71a5f6

Reviewed: 11 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

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.