CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

farcaster

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

59

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./src/skills/bundled/farcaster/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

76%Weight 40%Scale 1-5

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

The body is a clean, actionable command reference with concrete examples and no wasted tokens. Its main weakness is the absence of any confirmation/validation guidance for irreversible public write operations like posting or following.

Suggestions

Add an explicit validation/confirmation step before write operations, e.g. "Before /fc post or /fc follow, confirm the target and content with the user since casts and follows are public and not easily reversible."

Trim or merge the Features section into the Commands list to remove the minor redundancy and push conciseness toward 5.

Optionally add a short error-handling note (e.g. what to do on rate-limit or signer-missing errors) to strengthen workflow clarity for write operations.

DimensionReasoningScore

Conciseness

The body is lean — tabular commands, concrete examples, and factual rate limits with no padding about what Farcaster is; the trailing Features list partly restates the Commands section, a minor instance of over-explanation that keeps it just below 5.

4 / 5

Actionability

Commands are fully executable copy-paste-ready syntax (e.g. `/fc user <username>`, `/fc post <text>`, `/fc feed [--channel X]`) and the Examples section gives concrete invocations (`/fc user vitalik.eth`, `/fc post "Hello Farcaster!"`) covering the common cases.

5 / 5

Workflow Clarity

Setup → commands → examples is logically sequenced, but outward-facing write operations (post, reply, like, follow) have no validation or confirmation checkpoint, which caps workflow clarity at 3 per the destructive/outward-operation guideline.

3 / 5

Progressive Disclosure

A single self-contained file (~70 lines) with well-organized sections (Setup, Commands by category, Examples, Rate Limits, Features) and no need for external references; just over the under-50-line simple-skill exception, so it lands at 4 rather than 5.

4 / 5

Total

16

/

20

Passed

Description

61%Weight 40%Scale 1-5

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 concrete and domain-specific with good natural trigger terms, but it lacks any explicit "when to use" guidance and leaves several of the skill's capabilities unmentioned. Adding a Use-when clause and a fuller action list would raise completeness and specificity.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user wants to interact with Farcaster, read or post casts, follow users, or browse channels/trending."

Expand the action list to cover the other supported operations (search casts, channels, trending, reply, like, recast) so specificity reflects full coverage.

Lead with the most distinctive Farcaster-only terms ("casts", "channels") to further reduce overlap with generic social-media skills.

DimensionReasoningScore

Specificity

Names the domain (Farcaster via Neynar API) and three concrete actions ("read feeds, post casts, follow users"), but omits search, channels, trending, like, recast, and reply — gaps beyond the "minor" level that would warrant a 4.

3 / 5

Completeness

The "what" is clear (interact with Farcaster via Neynar API for feeds/casts/follows), but there is no "Use when…" clause or equivalent trigger guidance, which caps completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Includes several natural terms a user would say ("feeds", "casts", "post casts", "follow users"); missing a few natural variations like search, reply, or trending, so it stops short of comprehensive 5-level coverage.

4 / 5

Distinctiveness Conflict Risk

The Farcaster/Neynar API niche and the term "casts" are distinct, but "feeds" and "follow users" are generic social-media terms with minor overlap risk against other social skills, keeping it just below 5.

4 / 5

Total

14

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

alsk1992/CloddsBot

Path

src/skills/bundled/farcaster/SKILL.md

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.