Name: favro
Rating: 56.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

favro

Favro integration. Manage Organizations. Use when the user wants to interact with Favro data.

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/favro/SKILL.md

Quality

Content

67%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 highly actionable with concrete CLI commands and a clear connection-state workflow, though it carries some padded prose and inline reference-style content. Organization is good but could externalize the actions reference.

Suggestions

Trim motivational prose (e.g., 'so you can focus on the integration logic', 'This is the fastest way to get a connection') that adds no executable value.

Move the 20-row popular-actions table (mostly 'No description') into a separate references file, signaled from SKILL.md, to lighten the inline body.

Resolve the dangling 'skip to Step 2' reference by labeling the next step explicitly.

Dimension	Reasoning	Score
Conciseness	Mostly efficient command examples, but padded with unnecessary prose like "so you can focus on the integration logic rather than auth plumbing", "This is the fastest way to get a connection", and a best-practices rationale; fits 'mostly efficient but includes some unnecessary explanation', below 4 due to several padded passages.	3 / 5
Actionability	Provides concrete, copy-paste-ready commands (npm install -g @membranehq/cli@latest, membrane connection ensure, membrane action run, membrane request) plus an actions table and flag tables; minor gaps (CONNECTION_ID/actionId placeholders) keep it just below fully executable 5.	4 / 5
Workflow Clarity	Clear sequence (install → login → connect → search → run) with a polling feedback loop on connection state (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR); below 5 because the "skip to Step 2" reference is dangling and the overall sequence lacks an explicit end-to-end checklist.	4 / 5
Progressive Disclosure	Well-organized with clear section headers and a single external pointer (official docs); no bundle files exist, so structure is one self-contained file, but the 20-row 'No description' actions table and proxy-flags table are bulk inline content that could be externalized, keeping it below 5.	4 / 5
	Total	15 / 20 Passed

Description

62%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 covers both what and when with a clear trigger, but is thin on specific capabilities and trigger-term variety. It is distinct as a Favro-specific skill yet reads generically.

Suggestions

Enumerate more concrete capabilities (e.g., manage cards, boards, columns, tasks) instead of only 'Manage Organizations'.

Broaden the trigger with natural user phrases such as 'cards', 'boards', or 'tasks in Favro'.

Make the 'when' clause more specific, e.g. 'Use when the user wants to manage Favro cards, boards, tasks, or organizations.'

Dimension	Reasoning	Score
Specificity	Quotes "Favro integration" (domain) and "Manage Organizations" (one concrete action), but no other capabilities are listed, fitting the 'names domain and 1-2 concrete actions, not comprehensive' anchor; below 4 because only a single action is named.	3 / 5
Completeness	Explicitly answers both what ("Favro integration. Manage Organizations.") and when ("Use when the user wants to interact with Favro data"), matching the 'has both what and when; when could be more explicit' anchor; below 5 because the 'when' trigger is generic and the 'what' is sparse.	4 / 5
Trigger Term Quality	Includes the natural keyword "Favro" and trigger phrase "Use when the user wants to interact with Favro data", but misses synonyms and broader task terms (cards, boards, tasks); below 4 because keyword coverage is thin rather than 'a few natural terms missing'.	3 / 5
Distinctiveness Conflict Risk	Favro is a specific tool niche, so the trigger "Favro" is largely distinct with only minor overlap risk against other project-management skills; below 5 because the generic 'interact with Favro data' phrasing and thin trigger list keep it from a clear, well-fenced niche.	4 / 5
	Total	14 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/favro/SKILL.md
Commit: f484c82

Reviewed: ~19 hours 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.