Name: formspree
Rating: 58.4 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

formspree

Formspree integration. Manage Forms. Use when the user wants to interact with Formspree data.

Quality

68%

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/formspree/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 executable Membrane CLI commands and a well-sequenced, checkpointed connection workflow. Its main weakness is conciseness: an unnecessary introductory paragraph and a few filler lines pad the otherwise efficient guidance.

Suggestions

Delete the opening paragraph defining what Formspree is and the filler line 'When to use which actions: Use action names and parameters as needed.'

Fix the broken 'skip to Step 2' reference and relabel '1b' so the connection workflow's step numbering is consistent.

Consider moving the proxy flags table and the full clientAction state machine into a reference file to slim the main SKILL.md.

Dimension	Reasoning	Score
Conciseness	Mostly efficient command examples, but the opening 'Formspree is a service that allows developers to easily add forms...' and filler like 'When to use which actions: Use action names and parameters as needed.' explain concepts/background Claude does not need, fitting 'Mostly efficient but includes some unnecessary explanation or could be tightened'.	3 / 5
Actionability	Provides copy-paste-ready commands across install, login, connection ensure/get, action list/run, and proxy with a flags table, fully executable and covering the common cases, matching the top anchor.	5 / 5
Workflow Clarity	The connection setup is clearly sequenced with state-based checkpoints (polling until READY, handling CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR), but the 'skip to Step 2' reference is broken (no Step 2) and the '1b' labeling is inconsistent, fitting 'Clear sequence with most checkpoints present; minor validation gaps' rather than a clean 5.	4 / 5
Progressive Disclosure	No bundle files exist, so all content is inline in a single file organized under clear section headers (Overview, Authentication, Connecting, Searching, Proxy, Best practices) with no nested references, fitting 'Good structure; most content is appropriately placed; minor organization gaps'.	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 correctly includes an explicit 'Use when' trigger and leverages a distinctive brand name, but its capability statement ('Manage Forms') is generic and thin. Trigger keywords cover the brand but omit common synonyms like 'submissions'.

Suggestions

Replace the generic 'Manage Forms' with concrete actions, e.g. 'List forms, retrieve submissions, and create or update Formspree forms.'

Add natural trigger synonyms to the 'when' clause such as 'form submissions' or 'collect form responses'.

Keep the third-person voice but make the 'what' as specific as the 'when' already is.

Dimension	Reasoning	Score
Specificity	Quotes 'Formspree integration. Manage Forms.' name the domain plus a single generic action verb ('Manage'), matching the anchor 'Names the domain but actions are minimal or generic' rather than the 3-anchor which requires 1-2 concrete actions.	2 / 5
Completeness	It states a 'what' ('Manage Forms') and an explicit 'when' ('Use when the user wants to interact with Formspree data'), but the 'what' is thin and the 'when' is broad, fitting 'Has both what and when; when could be more explicit or specific' rather than the fully concrete 5-anchor.	4 / 5
Trigger Term Quality	Phrases 'Formspree', 'Forms', and 'Formspree data' give some relevant keywords but miss common variations like 'submissions' or 'form submissions', fitting 'Some relevant keywords but missing common variations or synonyms'.	3 / 5
Distinctiveness Conflict Risk	'Formspree' is a unique branded service name, giving a clear niche with distinct triggers and minimal conflict risk with other skills, matching the top anchor.	5 / 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/formspree/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.