Name: typless
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

typless

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

Quality

66%

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/typless/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 body provides concrete, executable Membrane CLI guidance with a well-structured connection workflow and validation checkpoints. Its main weaknesses are conceptual preamble that pads tokens, thin Popular-actions content, and broken step numbering.

Suggestions

Trim the opening conceptual paragraph ("Typless is a no-code platform...") and filler phrases like "so you can focus on the integration logic rather than auth plumbing" to reduce token overhead.

Fix the workflow numbering: label the connection-ensure step "1a" to match the existing "1b", and either add a real "Step 2" or replace the "skip to Step 2" references with a concrete next action.

Populate "Popular actions" with 2-3 actual common Typless actions (e.g. list records, create record) instead of only restating the discovery command.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but includes unnecessary explanation such as the opening "Typless is a no-code platform... Think of it as a low-code alternative" and filler like "so you can focus on the integration logic rather than auth plumbing" and "This is the fastest way to get a connection." This fits anchor 3 (mostly efficient, some unnecessary explanation that could be tightened) rather than 4, which requires only minor trims.	3 / 5
Actionability	Most guidance is executable copy-paste commands ("npm install -g @membranehq/cli@latest", "membrane connection ensure ...", "membrane action run <actionId> ...") plus a flag table, matching anchor 4. It does not reach 5 because the "Popular actions" section only restates a discovery command rather than listing concrete common actions.	4 / 5
Workflow Clarity	The connection flow has explicit state-based checkpoints and a feedback loop (poll with --wait, re-poll after CLIENT_ACTION_REQUIRED, check error on CONFIGURATION_ERROR/SETUP_FAILED), matching anchor 4. It is not 5 because numbering is incoherent ("Step 2" and "1b" are referenced without matching labels), creating minor gaps.	4 / 5
Progressive Disclosure	With no bundle files present, the single SKILL.md is organized into clear sections (Overview, Working with Typless, Popular actions, Best practices) with one external docs link and no nested references, matching anchor 4 (good structure, minor organization gaps). It is not 5 because "Typless Overview" is a bare hierarchy plus the vague line "Use action names and parameters as needed," and "Popular actions" is thin.	4 / 5
	Total	15 / 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 cleanly answers both what the skill does and when to use it, and is highly distinct thanks to the named Typless platform. Its weakness is generic capability language and limited trigger-term variety.

Suggestions

Replace generic verbs with concrete Typless actions, e.g. "Create and query records, build tables, and trigger automation workflows in Typless."

Broaden trigger terms with natural variations a user might say, such as "Typless records", "Typless tables", or "Typless automation", to improve activation recall.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Typless domain plus a few action areas, but the actions are generic rather than concrete capabilities, matching anchor 3 (names domain and 1-2 actions, not comprehensive). It does not reach 4 because no specific concrete operations (e.g. create record, query table, sync workflow) are enumerated.	3 / 5
Completeness	Both halves are present: the "what" ("Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with Typless data"), matching anchor 4. It stops short of 5 because the "what" is generic rather than a comprehensive list of concrete trigger phrases.	4 / 5
Trigger Term Quality	The description surfaces "Typless", "data", "records", "workflows", and "automate", but is missing common variations, synonyms, or a file extension that a user would naturally say. It fits anchor 3 (some relevant keywords, missing common variations) rather than 4, which expects fuller natural-term coverage.	3 / 5
Distinctiveness Conflict Risk	"Typless integration ... Use when the user wants to interact with Typless data" carves out a clear named-platform niche with a distinct trigger, giving minimal conflict risk per anchor 5. It is not 4 because the named app makes overlap with other skills unlikely.	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/typless/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.