Name: transform
Rating: 51.2 (1 reviews)
Author: membranedev

transform

TransForm integration. Manage data, records, and automate workflows. Use when the user wants to interact with TransForm data.

Quality

56%

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/transform/SKILL.md

Quality

Content

50%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 provides executable, well-structured CLI guidance for connecting to and acting on TransForm via Membrane. Its major drag is a large padded concept list and the absence of validation checkpoints around destructive action/proxy operations.

Suggestions

Remove or relocate the ~200-item generic noun/verb list; it adds tokens without actionable value and severely hurts conciseness.

Add a validation/verification step before running mutating actions or proxying POST/PUT/DELETE requests (e.g., confirm target, dry-run, check output) to lift workflow clarity above the destructive-operation cap of 3.

If detailed per-action reference is needed, split it into a separate reference file linked from the body to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The ~200-item bullet list of generic nouns and verbs (Form, Field, ... Innovate) is heavily padded with concepts Claude already knows, making the body noticeably verbose despite the reasonably efficient CLI sections.	2 / 5
Actionability	Concrete, copy-paste-ready commands cover the common cases (install, login, connection ensure, action list/run, request proxy) with a flags table, with only minor gaps such as unsubstituted placeholders and light output-handling detail.	4 / 5
Workflow Clarity	The connection sequence is clearly state-gated (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR with polling), but running actions and proxying arbitrary POST/PUT/DELETE requests lack validation or verification checkpoints for these destructive-capable operations, capping this dimension at 3.	3 / 5
Progressive Disclosure	There are no bundle files and section headers provide some structure, but the inlined 200-item concept list is content that should be split out or removed, leaving organization only partially effective.	3 / 5
	Total	12 / 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 clearly identifies the TransForm niche and includes an explicit 'Use when' trigger, satisfying both the what and when requirements in third person. Its main weakness is generic action language and limited keyword variation, which keep specificity and trigger quality at mid-range.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete capabilities (e.g., 'query records, create submissions, trigger workflows') to lift specificity.

Expand the trigger clause with natural synonyms and entities users actually say (e.g., 'forms, submissions, TransForm records, workflows') to improve trigger term coverage.

Add a concrete trigger-phrase list in the 'when' clause to push completeness from 4 toward 5.

Dimension	Reasoning	Score
Specificity	Names the TransForm domain plus a few actions ("Manage data, records, and automate workflows"), but the actions are generic verbs rather than concrete capabilities, matching the anchor that lists 1-2 actions without comprehensive coverage.	3 / 5
Completeness	It states both a 'what' ("Manage data, records, and automate workflows") and an explicit 'when' ("Use when the user wants to interact with TransForm data"), but the trigger could be more specific with concrete phrases, matching the anchor for both present with room to improve.	4 / 5
Trigger Term Quality	Relevant keywords (TransForm, data, records, workflows) appear, but common variations or synonyms a user might say are missing, fitting the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Tying activation to a named product (TransForm) gives it a clear niche with mostly distinct triggers and only minor overlap risk with other data-integration skills, fitting the 'mostly distinct' anchor.	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/transform/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.