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

tapform

Tapform integration. Manage Organizations, Pipelines, Users, Goals, Filters. Use when the user wants to interact with Tapform 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/tapform/SKILL.md

Quality

Content

68%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 lean, actionable integration guide built around concrete Membrane CLI commands and a well-sequenced connection workflow with state checkpoints. Its gaps are the missing validation/verification for destructive proxy and action operations and the absence of any Tapform-specific action examples under "Popular actions".

Suggestions

Add a validation/verification step after running actions or proxy requests (e.g., re-fetch the resource or check the response status) to support destructive operations safely.

Populate "Popular actions" with concrete Tapform-specific examples (list forms, create submission, manage workspace users) rather than only the generic discovery command.

Fill in the placeholder values in at least one end-to-end worked example so the run/proxy flow is fully copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The body is mostly executable commands with brief, justified operational prose (Membrane is a niche tool), matching the efficient anchor. Not 5 because phrases like "so you can focus on the integration logic rather than auth plumbing" could be trimmed.	4 / 5
Actionability	It provides many copy-paste-ready commands (login, connection ensure, action list/run, request) plus a concrete options table. Not 5 because "Popular actions" never lists a Tapform-specific action and examples rely on unfilled placeholders like CONNECTION_ID.	4 / 5
Workflow Clarity	The connection flow has strong state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED polling), but the proxy supports destructive methods (DELETE/PUT/PATCH) and action runs lack any validation or verification step. The destructive-operations-without-validation cap holds this at 3.	3 / 5
Progressive Disclosure	The single file is well organized into clear, navigable sections with no nested-reference problem. Not 5 because there are no one-level-deep references and the ~140-line file exceeds the 50-line simple-skill exception that would allow a 5 without external references.	4 / 5
	Total	15 / 20 Passed

Description

71%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 specific and distinct, naming concrete Tapform entities and an explicit use-when clause tied to a unique product name. Its main weakness is trigger-term breadth: it relies on the product name alone without task synonyms or concrete trigger phrases.

Suggestions

Expand the trigger clause with concrete phrases, e.g. "Use when the user wants to manage Tapform forms, submissions, workspaces, or users."

Add natural synonyms or file-type terms users might say so the description triggers on a wider range of phrasings.

Vary the action verbs beyond the generic "Manage" to better convey the distinct operations available (create, list, update, filter).

Dimension	Reasoning	Score
Specificity	"Manage Organizations, Pipelines, Users, Goals, Filters" lists several concrete entities with a concrete verb, matching the several-specific-actions anchor. Not 5 because the single generic verb "Manage" lacks the multiple distinct actions of the anchor-5 example.	4 / 5
Completeness	It states both a clear "what" (manage named entities) and an explicit "when" ("Use when the user wants to interact with Tapform data"). Not 5 because the trigger is generic rather than concrete trigger phrases like forms, submissions, or workspaces.	4 / 5
Trigger Term Quality	The only natural term is "Tapform"/"Tapform data", repeated without task-type synonyms or file extensions. Not 4 because coverage is limited to the product name with no common variations.	3 / 5
Distinctiveness Conflict Risk	"Tapform" is a specific named product giving it a clear niche with distinct triggers and minimal conflict risk, matching the anchor-5 example.	5 / 5
	Total	16 / 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/tapform/SKILL.md
Commit: f484c82

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