Name: feathery
Rating: 60 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

feathery

Feathery integration. Manage Organizations, Users. Use when the user wants to interact with Feathery data.

Quality

70%

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/feathery/SKILL.md

Quality

Content

75%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, copy-paste Membrane CLI commands and a clear connection-state workflow, but it carries some marketing prose and a vestigial overview section, and the "Step 2" cross-reference is broken. Structure is solid for a single-file skill, though the actions table could be externalized.

Suggestions

Fix the broken "Step 2" cross-reference (there is no Step 2) and renumber the connection steps consistently instead of jumping to "1b".

Trim non-essential prose such as the "Membrane handles authentication... so you can focus on the integration logic rather than auth plumbing" line and the empty "Feathery Overview" bullet list.

Add a brief confirm-before-delete note for the destructive actions (delete-user, delete-form, delete-document-envelope) listed in the actions table.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-dense and efficient, but includes trimmable prose such as the Membrane auth-plumbing marketing line and a near-empty "Feathery Overview" bullet list plus "Use action names and parameters as needed", fitting the anchor for mostly efficient content with some unnecessary explanation.	3 / 5
Actionability	It provides copy-paste-ready commands for the common cases (install, login, connection ensure, action list/run, request proxy) with real flags and a populated actions table, matching the anchor for fully executable, copy-paste-ready guidance covering common cases.	5 / 5
Workflow Clarity	The connection workflow has an explicit sequence with state-validation checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a poll-after-action feedback loop, but references a non-existent "Step 2" and uses odd "1b" numbering, fitting the anchor for a clear sequence with minor validation/labeling gaps.	4 / 5
Progressive Disclosure	The skill is a single self-contained file with well-organized sections and no nested references, but the large inline popular-actions table and proxy-options table could arguably live in separate reference files, matching the anchor for good structure with minor organization gaps rather than the ideal one-level-deep reference split.	4 / 5
	Total	16 / 20 Passed

Description

66%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 distinct and includes an explicit Use-when trigger, but its capability statement is thin and generic ("Manage Organizations, Users") rather than enumerating the concrete actions the skill actually exposes. It reads as a competent but under-specified trigger description.

Suggestions

Replace the generic verb "Manage" with concrete actions the skill supports, e.g. "List and create users, retrieve form submissions, fill document templates, and get workspace/account info."

Broaden trigger terms to natural phrasings users might say, such as "Feathery forms, submissions, document envelopes, or users" rather than only "Feathery data".

Align the description's stated capabilities with the body's action table so the "what" is comprehensive rather than implying only Organizations and Users.

Dimension	Reasoning	Score
Specificity	The description names the domain (Feathery) and a couple of concrete entity types ("Manage Organizations, Users"), but the verb "Manage" is generic and coverage is far from comprehensive, matching the anchor for naming a domain with 1-2 actions that are not comprehensive.	3 / 5
Completeness	It states both a "what" ("Feathery integration. Manage Organizations, Users.") and an explicit "when" ("Use when the user wants to interact with Feathery data."), but the "what" is thin and the trigger could be more specific, matching the anchor for having both with room for greater specificity rather than the fully concrete level 5.	4 / 5
Trigger Term Quality	It surfaces the core keyword "Feathery" and the data terms "Organizations, Users" plus "Feathery data", but lacks common variations or synonyms a user might naturally say, fitting the anchor for some relevant keywords with missing variations.	3 / 5
Distinctiveness Conflict Risk	"Feathery integration" names a specific single-app niche with a distinct trigger ("interact with Feathery data"), giving it minimal conflict risk with other skills, matching the clear-niche anchor.	5 / 5
	Total	15 / 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/feathery/SKILL.md
Commit: f484c82

Reviewed: 5 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.