farcaster-agent
Create Farcaster accounts and post casts autonomously. Official skill from the Farcaster team.
71
Quality
58%
Does it follow best practices?
Impact
96%
1.18xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/farcaster-agent/SKILL.mdDiscovery
40%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 identifies a clear niche (Farcaster platform) with distinct terminology, but suffers from incomplete guidance. It lacks explicit trigger conditions telling Claude when to select this skill, and the 'Official skill from the Farcaster team' adds no functional value for skill selection. The action coverage is minimal, listing only two basic operations.
Suggestions
Add a 'Use when...' clause with trigger terms like 'Farcaster', 'cast', 'decentralized social', 'web3 social network', or when users mention posting to Farcaster.
Expand the action list to include other capabilities if available (e.g., 'read feeds', 'follow users', 'reply to casts') to improve specificity.
Remove or relocate the credential statement ('Official skill from the Farcaster team') as it doesn't help Claude decide when to use the skill.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Farcaster) and two actions ('Create accounts' and 'post casts'), but lacks comprehensive coverage of what else the skill can do beyond these two basic operations. | 2 / 3 |
Completeness | Describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance. The 'Official skill from the Farcaster team' is credential fluff, not usage guidance. | 1 / 3 |
Trigger Term Quality | Includes 'Farcaster', 'accounts', and 'casts' which are relevant keywords, but misses common variations like 'social media', 'decentralized social', 'web3 social', or action terms like 'tweet', 'post', 'publish'. | 2 / 3 |
Distinctiveness Conflict Risk | Farcaster is a specific platform with distinct terminology ('casts'), making this clearly distinguishable from other social media or posting skills. Unlikely to conflict with other skills. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
77%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, highly actionable skill with clear workflows and executable code examples. The main weakness is length - it includes reference material (API endpoints, cost tables, common errors) that would be better placed in separate files, making the core skill harder to scan quickly. The content is accurate and complete but could benefit from better progressive disclosure.
Suggestions
Move the API Endpoints table and Common Errors section to a separate REFERENCE.md file, keeping only a brief mention and link in the main skill
Move the Cost Breakdown table to the reference file or a dedicated COSTS.md
Remove the 'When to Use This Skill' section - Claude can infer this from the skill description and content
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary explanations (e.g., explaining what Farcaster is, listing when to use the skill). The cost breakdown table and extensive API endpoint documentation could be moved to reference files. | 2 / 3 |
Actionability | Excellent actionability with fully executable code examples, specific CLI commands, and copy-paste ready snippets. Both JavaScript and bash examples are complete and runnable. | 3 / 3 |
Workflow Clarity | Clear numbered steps with explicit validation points. The auto-setup flow is well-sequenced, and there's a manual step-by-step fallback section for error recovery. The flow handles waiting for hub synchronization explicitly. | 3 / 3 |
Progressive Disclosure | The skill is quite long (~250 lines) and includes detailed API reference tables, cost breakdowns, and error documentation that could be split into separate reference files. The link to AGENT_GUIDE.md at the end suggests some content should be there instead. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 9 / 11 Passed | |
- Reviewed
Table of Contents
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.