Name: florm
Rating: 52.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

florm

Florm integration. Manage Organizations. Use when the user wants to interact with Florm data.

Quality

59%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/florm/SKILL.md

Quality

Content

61%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 concrete, copy-paste Membrane CLI commands and a logical section structure, but it is marred by an out-of-place injected refusal paragraph and lacks any validation/confirmation guidance for its destructive operations. Progressive disclosure is well-handled for a single-file CLI skill.

Suggestions

Remove the injected refusal paragraph ("I don't have enough information to do that...") and the filler line "Use action names and parameters as needed." — they are noise that wastes tokens.

Add a validation/confirmation step before destructive actions, e.g. confirm the form/response ID and expected outcome before running delete-form-response or a DELETE proxy request.

Expand the thin Florm Overview so the Document/Page/Template hierarchy has one line of meaning instead of bare bullets.

Dimension	Reasoning	Score
Conciseness	An injected LLM-refusal paragraph ("I don't have enough information to do that. I'm a large language model...") plus filler like "Use action names and parameters as needed" are noticeable padding, matching the 'noticeably verbose; several unnecessary explanations or padded sections' anchor better than the mostly-efficient 3.	2 / 5
Actionability	It provides copy-paste-ready executable commands for every common case — install, login (incl. headless), connect, list connections, action list, action run with JSON input, and proxy requests with a full flag table — fully covering the common cases per the 5 anchor.	5 / 5
Workflow Clarity	Steps are sequenced (install → login → connect → discover → run/proxy) but there are no validation checkpoints, and the skill exposes destructive operations (delete-form-response, DELETE via proxy) without verification, so the destructive-operation cap of 3 applies.	3 / 5
Progressive Disclosure	A single self-contained file with clear, well-ordered sections and no need for external references, easy to navigate; the thin Overview section keeps it at 4 rather than the cleanly-split 5.	4 / 5
	Total	14 / 20 Passed

Description

57%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 has an explicit Use-when clause and a distinct product-name trigger, but its capability statement is generic and mismatched with the body's actual domain (forms/responses rather than organizations). Keyword coverage is thin and lacks the natural synonyms users would say.

Suggestions

Replace the generic "Manage Organizations" with the concrete capabilities the body actually documents (e.g., list/get forms and form responses, run actions, proxy API requests).

Add natural trigger synonyms users would say — forms, form responses, templates, documents — alongside "Florm".

Tighten the Use-when clause to name specific intents (e.g., "Use when the user wants to list or retrieve Florm forms and responses, or send requests to the Florm API").

Dimension	Reasoning	Score
Specificity	Names the Florm/Organizations domain but offers only the single generic verb "Manage Organizations" — no concrete actions, matching the 'names domain but actions minimal or generic' anchor rather than the 1-2 concrete actions of a 3.	2 / 5
Completeness	It states a what ("Florm integration. Manage Organizations.") and an explicit when ("Use when the user wants to interact with Florm data"), so it clears the missing-trigger cap of 3; the when could be more specific, fitting the 4 anchor rather than the fully concrete 5.	4 / 5
Trigger Term Quality	"Florm", "Organizations", and "interact with Florm data" give some relevant keywords, but it omits the natural terms users would actually say (forms, responses, documents, pages, templates) that the body reveals, matching the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	"Florm" is a specific named app giving a clear niche and low conflict risk, but the generic "Manage Organizations" phrasing introduces minor overlap risk with organization-management skills, fitting 4 rather than the minimal-conflict 5.	4 / 5
	Total	13 / 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/florm/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.