Name: web3forms-contact-forms-for-static-websites
Rating: 59.2 (1 reviews)
Author: membranedev

web3forms-contact-forms-for-static-websites

Web3Forms — Contact Forms for Static Websites integration. Manage data, records, and automate workflows. Use when the user wants to interact with Web3Forms — Contact Forms for Static Websites 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/web3forms-contact-forms-for-static-websites/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 CLI commands and a strong connection-state workflow including feedback loops, held back mainly by mild verbosity in the intro and best-practices prose and a small numbering inconsistency in the workflow.

Suggestions

Trim filler prose such as 'so you can focus on the integration logic rather than auth plumbing' and tighten the best-practices bullets to imperative guidance.

Fix the workflow numbering: the body references 'Step 2' and '1b' but never defines Step 1/Step 2, so relabel the connecting/waiting steps into a coherent numbered sequence.

Add a brief validation note for running actions (e.g. inspect outputSchema before destructive action runs) to strengthen the workflow feedback loop.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient command reference, but it includes unnecessary prose such as 'so you can focus on the integration logic rather than auth plumbing' and padded best-practice sentences ('This will burn less tokens and make communication more secure') that could be trimmed.	3 / 5
Actionability	It provides copy-paste-ready executable commands for every key task (install, login, connection ensure, action list, action run, request proxy) with flag tables and JSON examples that cover the common cases.	5 / 5
Workflow Clarity	The connection flow has a clear sequence with explicit state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll-then-retry feedback loop, but it references an undefined 'Step 2'/'1b' numbering and lacks validation around running actions.	4 / 5
Progressive Disclosure	The skill is a single self-contained SKILL.md with no bundle files, organized into well-labeled sections (install, auth, connecting, searching, running, proxy, best practices); content is appropriately placed though no one-level-deep references exist to push it to 5.	4 / 5
	Total	16 / 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 explicitly includes a 'Use when' trigger and names a distinct service niche, but the capability phrasing is generic and lacks the concrete, domain-specific actions and natural synonyms (e.g. form submissions) that would make it fully clear and easily triggered.

Suggestions

Replace 'Manage data, records, and automate workflows' with concrete Web3Forms-specific actions such as 'Retrieve form submissions, list forms, and trigger workflows from contact form data'.

Add natural trigger synonyms users would say, e.g. 'Use when the user wants to view contact form submissions, check form entries, or automate workflows from Web3Forms data'.

Keep the explicit 'Use when' clause but tighten it to mention submissions/email delivery so the trigger matches real user phrasing.

Dimension	Reasoning	Score
Specificity	The description names the domain (Web3Forms) and lists actions ('Manage data, records, and automate workflows'), but those actions are generic CRUD/workflow terms rather than concrete, domain-specific operations like retrieving form submissions or sending form data.	3 / 5
Completeness	Both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Web3Forms... data') are present; the 'when' is clear, though the 'what' is vague enough to keep it from a 5.	4 / 5
Trigger Term Quality	It surfaces 'Contact Forms for Static Websites' as part of the product name, which are natural terms, but it omits common variations users would actually say such as 'form submissions', 'email delivery', or 'contact form submissions'.	3 / 5
Distinctiveness Conflict Risk	The named service 'Web3Forms — Contact Forms for Static Websites' carves a clear niche with distinct triggers and low conflict risk, but the generic 'manage data, records, and automate workflows' phrasing leaves minor overlap with other data-management skills.	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/web3forms-contact-forms-for-static-websites/SKILL.md
Commit: f484c82

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