Name: formaloo
Rating: 55.2 (1 reviews)
Author: membranedev

formaloo

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

Quality

62%

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/formaloo/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 is a strong, executable runbook with concrete CLI commands and a genuine connection-state feedback loop. Its weaknesses are minor padding/marketing prose, an inconsistent membrane-vs-npx invocation convention, and a dangling "Step 2" reference that fragments the workflow.

Suggestions

Trim marketing filler (the Google Forms/SurveyMonkey comparison and the "auth plumbing" framing) to lift conciseness toward the lean anchor.

Standardize on one invocation style (either `membrane` or `npx @membranehq/cli@latest`) across the action-search and run sections, and resolve the dangling "Step 2" reference by labeling the next step.

Make action selection actionable by giving a short worked example of translating a user intent into a `--intent` query and reading `inputSchema`/`outputSchema`.

Dimension	Reasoning	Score
Conciseness	The body is mostly tight, command-driven prose, but padded lines like "Think of it as a more versatile alternative to Google Forms or SurveyMonkey" and "so you can focus on the integration logic rather than auth plumbing" add explanation/marketing Claude does not need.	3 / 5
Actionability	It supplies copy-paste-ready bash commands for install, login, connection, action search/run, and proxy requests with a flag table, but mixes `membrane` and `npx @membranehq/cli@latest` invocation styles and leaves action selection vague ("Use action names and parameters as needed").	4 / 5
Workflow Clarity	The install→login→connect→poll→search→run sequence is clear and includes a real feedback loop (poll BUILDING/CLIENT_ACTION_REQUIRED until READY), but the dangling "skip to Step 2" reference with no matching Step 2 header is a minor sequencing gap.	4 / 5
Progressive Disclosure	No bundle files exist, so this is a single-file skill; section headers (Overview, Authentication, Connecting, Proxy requests, Best practices) are well organized and easy to navigate, but at ~140 lines with no one-level-deep references and some redundancy between the "Searching for actions" and "Popular actions" sections it stops short of the score-5 anchor.	4 / 5
	Total	15 / 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 cleanly pairs a what/when structure and anchors on a distinctive named product, but its action language is generic and its trigger terms miss the concrete Formaloo concepts (forms, surveys, databases) users actually mention. It is solid but not exemplary.

Suggestions

Replace generic verbs with concrete Formaloo capabilities, e.g. "Create forms, surveys, and quizzes; manage workspace records and databases; run workflow automations."

Broaden the trigger clause to capture natural phrasing: "Use when the user wants to work with Formaloo forms, surveys, quizzes, or database records."

Add the file/asset terms users say (forms, surveys, .formaloo) to raise trigger-term coverage toward the comprehensive anchor.

Dimension	Reasoning	Score
Specificity	The description names the Formaloo domain but relies on generic verbs ("Manage data, records, and automate workflows") rather than concrete capabilities like forms, surveys, or database operations; not as vacuous as a score-1 anchor, but the actions are minimal and generic.	2 / 5
Completeness	It has an explicit "Use when the user wants to interact with Formaloo data" trigger and a stated "what", satisfying both halves; the "when" is somewhat narrow and the "what" generic, so it stops short of the fully concrete, multi-trigger score-5 anchor.	4 / 5
Trigger Term Quality	"Formaloo" and "Formaloo data" are the relevant natural keywords, but common variations users would actually say (forms, surveys, quizzes, databases) are absent, so coverage is partial rather than comprehensive.	3 / 5
Distinctiveness Conflict Risk	The named platform "Formaloo" gives it a clear niche with low conflict risk, but the generic trailing actions ("manage data, records, automate workflows") leave minor overlap risk with other data/sales skills, keeping it just below the distinct-trigger score-5 anchor.	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/formaloo/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.