Name: fastfield-mobile-forms
Rating: 60 (1 reviews)
Author: membranedev

fastfield-mobile-forms

FastField Mobile Forms integration. Manage data, records, and automate workflows. Use when the user wants to interact with FastField Mobile Forms 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/fastfield-mobile-forms/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 commands and a well-sequenced connection workflow that includes state checkpoints and a feedback loop. It loses points on conciseness due to a marketing-style intro and a redundant section, and slightly on workflow clarity for missing post-action verification.

Suggestions

Trim the introductory paragraph to one line of functional context and remove the redundant 'Popular actions' section that repeats the action-list command from 'Searching for actions'.

Add a verification step after running actions or proxy requests (e.g. check the `output`/error field and confirm the expected record was created) to close the workflow feedback loop for write operations.

Consolidate 'Searching for actions' and 'Popular actions' into a single section to remove the duplicated command and improve navigation.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands, but the opening marketing paragraph ('helps businesses collect data and streamline workflows... field service teams, inspectors... replace paper forms with digital versions') and the redundant 'Popular actions' section that re-states the action-list command could be trimmed.	3 / 5
Actionability	Provides copy-paste-ready, executable commands throughout (install, login, connection ensure, action list/run, request) plus a clear flag table, covering the common integration cases.	5 / 5
Workflow Clarity	The connect→wait-for-ready→search→run sequence is clearly ordered with explicit state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a poll→handle→re-poll feedback loop; minor gap is the lack of result verification after running an action.	4 / 5
Progressive Disclosure	Well-organized into clearly headed sections with no nested references; for a CLI-integration skill the inline content is appropriately placed, with only minor organization gaps such as the duplicated action-list command.	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 clearly identifies a specific product niche and includes an explicit 'Use when' trigger, giving it strong distinctiveness and good completeness. It is held back by generic action verbs and limited trigger-term coverage that misses common synonyms a user might naturally say.

Suggestions

Replace generic verbs with concrete actions, e.g. 'Create and submit forms, query records, and dispatch assignments' instead of 'Manage data, records, and automate workflows'.

Broaden the 'Use when' clause to name natural trigger phrases such as 'mobile forms, form submissions, field service data, or inspections'.

Consider naming FastField-specific entities (submissions, dispatches, choice lists) to sharpen specificity.

Dimension	Reasoning	Score
Specificity	Names the domain ('FastField Mobile Forms integration') and a few actions ('Manage data, records, and automate workflows'), but the verbs are generic rather than concrete like 'extract' or 'fill'; not comprehensive.	3 / 5
Completeness	Both 'what' ('Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with FastField Mobile Forms data') are present and explicit, but the 'when' clause is narrow and could name more trigger phrases.	4 / 5
Trigger Term Quality	Includes the product name and 'data', 'records', 'workflows', but misses common natural variations users might say such as 'mobile forms', 'form submissions', 'field service', or 'inspections'.	3 / 5
Distinctiveness Conflict Risk	Targets a named, specific product ('FastField Mobile Forms') with distinct triggers, so it is clearly distinguishable from other skills with minimal conflict risk.	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/fastfield-mobile-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.