Name: planso-forms
Rating: 59.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

planso-forms

PlanSo Forms integration. Manage Forms. Use when the user wants to interact with PlanSo Forms data.

Quality

68%

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

Quality

Content

75%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 highly actionable with concrete CLI commands and a well-structured connection workflow including state-based checkpoints and a feedback loop. Tightening the introductory prose and adding output validation for action/proxy calls would push it higher.

Suggestions

Trim the introductory paragraph explaining what PlanSo Forms is and the "focus on integration logic rather than auth plumbing" aside to improve conciseness.

Add an explicit validation/verification step after running actions or proxy requests (e.g., check the output/error fields before proceeding) to strengthen workflow clarity.

Fix the step numbering inconsistency (e.g., label an explicit "Step 2" referenced by "skip to Step 2").

Dimension	Reasoning	Score
Conciseness	Quotes like "PlanSo Forms is a web application that allows users to create and manage online forms... Think of it as a simple, embeddable form builder" and "so you can focus on the integration logic rather than auth plumbing" are mostly efficient but include some unnecessary explanation that could be tightened; not a 4 because the padding is more than minor, not a 2 because it is not severely verbose.	3 / 5
Actionability	Concrete copy-paste commands such as "npm install -g @membranehq/cli@latest", "membrane connection ensure \"https://www.planso.net/planso-forms/\" --json", "membrane action run <actionId> --connectionId=CONNECTION_ID --input '{\"key\": \"value\"}' --json", plus a flags table, fully cover the common cases; not a 4 because the guidance is complete rather than having minor gaps.	5 / 5
Workflow Clarity	The connection flow has a clear sequence with explicit state checkpoints ("READY", "BUILDING", "CLIENT_ACTION_REQUIRED") and a feedback loop ("After the user completes the action... poll again to check if the state moved to READY"), but the action-running and proxy sections lack output validation and the step numbering is slightly inconsistent ("skip to Step 2" with no labeled Step 2); not a 5 because of these validation gaps, not a 3 because checkpoints and a feedback loop are explicitly present.	4 / 5
Progressive Disclosure	The body is well-organized with clear section headers (Install, Authentication, Connecting, Searching for actions, Running actions, Proxy requests, Best practices) and no nested references, but all content is inline with no overview-pointing-to-details split; not a 5 because there is no explicit one-level-deep reference pattern, not a 3 because the structure is good rather than merely "some".	4 / 5
	Total	16 / 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 correctly includes both a what and a Use-when clause and names a specific app, but its actions and trigger terms are thin and generic. Expanding concrete actions and adding natural trigger synonyms would raise it.

Suggestions

List concrete actions beyond "Manage Forms" (e.g., create forms, list submissions, retrieve submissions) to improve specificity.

Add natural trigger synonyms and file/URL cues (e.g., "forms, form submissions, PlanSo Forms data") to broaden trigger term coverage.

Make the "when" clause more specific with multiple concrete trigger phrases rather than a single generic statement.

Dimension	Reasoning	Score
Specificity	Quotes "PlanSo Forms integration. Manage Forms." name the domain and one concrete-but-generic action ("Manage Forms"), matching the anchor that names a domain with 1-2 actions but is not comprehensive; it is not a 2 because an action is named beyond the domain alone, and not a 4 because only one generic action is given rather than several specific ones.	3 / 5
Completeness	It states both a "what" ("PlanSo Forms integration. Manage Forms.") and an explicit "when" ("Use when the user wants to interact with PlanSo Forms data"), but the when is generic rather than concrete trigger phrases; this matches the anchor for both present with the when only somewhat explicit, not a 5 (no concrete multi-phrase triggers) and not a 3 (when is explicitly present, not missing).	4 / 5
Trigger Term Quality	Quotes "PlanSo Forms" and "Forms" provide some relevant keywords with the explicit "Use when the user wants to interact with PlanSo Forms data", but common variations, synonyms, and file extensions are missing; it is not a 2 because natural keywords are present, and not a 4 because coverage is thin rather than good.	3 / 5
Distinctiveness Conflict Risk	Naming the specific app "PlanSo Forms" gives a clear niche with minimal conflict risk, but the bare trigger "Forms" could overlap with generic form-builder skills; this fits mostly distinct with minor overlap risk, not a 5 (triggers are thin) and not a 3 (the named app makes it more specific than merely "somewhat specific").	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/planso-forms/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.