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

Blog Docs Log in Get started

formcarry

Formcarry integration. Manage Forms. Use when the user wants to interact with Formcarry 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/formcarry/SKILL.md

Quality

Content

82%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 strong, executable guide: concrete CLI commands cover connection, action discovery/execution, and proxy fallback, with a well-sequenced connection workflow and explicit state-check feedback loops. The main weaknesses are minor over-explanation in the intro and a dangling "Step 2" reference that has no matching labeled section.

Suggestions

Add an explicitly labeled "## Step 2: Run an action" (or similar) section so the "skip to Step 2" references resolve to a real anchor.

Trim the introductory paragraph and the "focus on the integration logic rather than auth plumbing" phrasing to keep only what Claude does not already know.

Consider splitting the full action catalog / proxy flag reference into a `references/` file and linking to it, keeping SKILL.md as a tighter overview.

Dimension	Reasoning	Score
Conciseness	The body is dominated by lean, copy-paste command examples with minimal prose. It has minor over-explanation (the opening paragraph describing what Formcarry is, and "so you can focus on the integration logic rather than auth plumbing") that could be trimmed. Matches anchor 4; not 5 because of that mild padding, not 3 because the bulk is efficient.	4 / 5
Actionability	Concrete, executable commands are given throughout — `membrane connection ensure`, `membrane login complete <code>`, `membrane action run ... --input`, `membrane request` — covering connection, action discovery/execution, and proxy fallback. Matches anchor 5 (fully executable, copy-paste ready, covers common cases).	5 / 5
Workflow Clarity	The connection flow is clearly sequenced with state-based validation checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and an explicit poll-and-retry feedback loop. Below anchor 5 because the "skip to Step 2" reference points to a section that is not explicitly labeled "Step 2", leaving a minor navigation gap; above anchor 3 because checkpoints and error handling are present.	4 / 5
Progressive Disclosure	Content is organized into clear, well-signaled sections (Install, Authentication, Connecting, Searching actions, Popular actions, Running actions, Proxy, Best practices) with no nested/deep references and no bundle files to misplace. Below anchor 5 because some inline reference material (the Popular actions table and proxy flag table) is modest and could warrant a dedicated reference, but overall placement is good.	4 / 5
	Total	17 / 20 Passed

Description

57%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 functional and includes an explicit trigger clause, but the capability statement is thin (a single generic "Manage Forms" action) and natural keyword coverage is limited. Expanding the what with concrete actions and adding synonyms would lift it.

Suggestions

Replace the generic "Manage Forms" with concrete actions, e.g. "List and filter form submissions, create and delete forms, test API authentication."

Add natural trigger synonyms users might say, such as "form submissions", "form responses", or "Formcarry API", to improve trigger-term coverage.

Tighten the "when" clause to reference concrete scenarios, e.g. "Use when the user wants to retrieve form submissions, create forms, or interact with the Formcarry API."

Dimension	Reasoning	Score
Specificity	"Manage Forms" names the domain but is a single, minimal, generic action rather than several concrete actions. It sits at anchor 2 ("Names the domain but actions are minimal or generic"); not a 3 because there is no second concrete action, and not a 1 because the domain is named.	2 / 5
Completeness	It states both a "what" ("Manage Forms") and an explicit "when" ("Use when the user wants to interact with Formcarry data"). Below anchor 5 because the "what" is generic rather than concrete trigger phrases; above anchor 3 because an explicit "Use when" clause is present.	4 / 5
Trigger Term Quality	Keywords "Formcarry" and "Forms" appear, but common variations/synonyms a user might say (submissions, form data, .json) are missing. Matches anchor 3 ("Some relevant keywords but missing common variations or synonyms"); not 4 because coverage is thin, not 2 because real relevant terms are present.	3 / 5
Distinctiveness Conflict Risk	Naming the branded service "Formcarry" gives a clear niche with distinct triggers and minimal conflict risk. Below anchor 5 because "Manage Forms" could still overlap with generic form-handling skills; above anchor 3 because the brand name is specific.	4 / 5
	Total	13 / 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/formcarry/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.