Name: gravity-forms
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

gravity-forms

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

Quality

64%

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/gravity-forms/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 content is a well-structured, command-rich guide with a clear connection-to-action workflow and real validation checkpoints, weakened mainly by some trimmable prose and an actions table with empty description cells.

Suggestions

Fill in or remove the empty Description column in the Popular actions table so every row earns its tokens, and include the actionId so rows are runnable.

Resolve the dangling 'Step 2' references (the text says 'skip to Step 2' but no Step 2 exists) by renumbering or relabeling the sections.

Trim opinionated prose like 'so you can focus on the integration logic rather than auth plumbing' to keep the body lean.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean command-driven content, but it carries trimmable explanatory prose ("so you can focus on the integration logic rather than auth plumbing", the Agent Types paragraph) and a Popular actions table whose empty Description column adds tokens without value.	3 / 5
Actionability	It provides concrete copy-paste commands for install, login, connection ensure, action list/run, and proxy requests, with only minor gaps (placeholders like CONNECTION_ID/<actionId> require substitution and the actions table lacks runnable actionIds/descriptions).	4 / 5
Workflow Clarity	A clear sequence runs from install → auth → connection ensure → poll/wait for READY → handle client actions → search → run, with validation checkpoints (polling state, handling CONFIGURATION_ERROR) and a retry loop, but the text references a 'Step 2' that never appears.	4 / 5
Progressive Disclosure	The skill is a single well-organized SKILL.md with clear section headers and no nested or buried references, which is appropriate given it has no bundle files; minor gaps (the empty actions table) keep it just short of a 5.	4 / 5
	Total	15 / 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 answers both what and when and is highly distinctive thanks to the branded product name, but it is held back by a generic single action ("Manage Forms") and trigger phrasing that lacks concrete, natural synonyms.

Suggestions

Replace the generic "Manage Forms" with concrete actions, e.g. "Create and manage forms, list and submit entries, send notifications."

Expand the trigger clause with natural phrases a user would say, e.g. "Use when the user mentions Gravity Forms, form entries, or form submissions."

Dimension	Reasoning	Score
Specificity	The description names the domain ("Gravity Forms integration") but the only stated action is the generic "Manage Forms" — no concrete specific operations like create entries or submit forms, matching the 'names the domain but actions are minimal or generic' anchor.	2 / 5
Completeness	Both halves are present — "Manage Forms" gives a (vague) what and "Use when the user wants to interact with Gravity Forms data" gives a when — but the when is generic and could be more explicit with concrete triggers, fitting the 'both what and when, when could be more specific' anchor.	4 / 5
Trigger Term Quality	It includes the natural product term "Gravity Forms" and "forms", but the trigger phrasing "interact with Gravity Forms data" is generic and lacks common synonyms or variations a user might say.	3 / 5
Distinctiveness Conflict Risk	Gravity Forms is a specific branded WordPress plugin, so the description carves out a clear niche with distinct triggers and minimal risk of firing for an unrelated skill.	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/gravity-forms/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.