Name: formbricks
Rating: 52 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

formbricks

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

Quality

57%

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/formbricks/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 content is highly actionable with concrete executable CLI commands and a well-sequenced connection workflow, but it loses points on conciseness due to marketing-style padding and is capped on workflow clarity because destructive action operations lack validation steps. Splitting the large action table into a reference file would further improve progressive disclosure.

Suggestions

Add a validation/verification checkpoint before destructive actions (e.g., confirm the target ID with the user or fetch-then-confirm before delete-survey/delete-person/delete-response/delete-webhook).

Trim marketing-style padding such as the "used by product managers, marketers, and UX researchers" intro and the "so you can focus on the integration logic rather than auth plumbing" aside.

Move the Popular actions table into a separate reference file (e.g., references/actions.md) and keep only the most common examples inline in SKILL.md.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient CLI commands and tables, but contains unnecessary padding such as the marketing intro ("It's used by product managers, marketers, and UX researchers...") and phrases like "so you can focus on the integration logic rather than auth plumbing". Matches anchor 3 (mostly efficient, some unnecessary explanation) rather than 4 because several sentences could be trimmed.	3 / 5
Actionability	Provides concrete, executable CLI commands throughout (login, connection ensure, action run with --input, request proxy flags) that are largely copy-paste ready. It sits at anchor 4 rather than 5 because several examples use placeholders (CONNECTION_ID, '{"key": "value"}') rather than concrete realistic values.	4 / 5
Workflow Clarity	The connection flow is well-sequenced with explicit state-based branches and a polling loop, but the "Running actions" section covers destructive operations (delete-survey, delete-person, delete-response, delete-webhook) with no validation or verification checkpoint. Per the rubric cap, destructive/batch workflows without validation cannot score above 3.	3 / 5
Progressive Disclosure	The body is organized into clear, well-labeled sections (Overview, Authentication, Connecting, Searching, Popular actions, Running actions, Proxy, Best practices). It reaches anchor 4 (good structure, minor organization gaps) rather than 5 because the large Popular actions table is sizable inline content that could live in a separate reference file.	4 / 5
	Total	14 / 20 Passed

Description

53%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 names the target app and includes an explicit "Use when" trigger, but it is thin on concrete capabilities and uses generic trigger phrasing. Listing more specific actions (surveys, responses, people, webhooks) and richer trigger terms would raise both specificity and completeness.

Suggestions

Replace the generic "Manage Organizations" with the actual concrete capabilities the skill exposes (e.g., manage surveys, responses, people, webhooks, and action classes).

Expand trigger terms to include natural user phrases such as "surveys", "forms", "user feedback", and "responses", not just "interact with Formbricks data".

Make the "when" clause more concrete, e.g. "Use when the user wants to create or manage Formbricks surveys, responses, people, or webhooks."

Dimension	Reasoning	Score
Specificity	Names the domain ("Formbricks") and one concrete action ("Manage Organizations"), but coverage is not comprehensive. It sits at anchor 3 (1-2 concrete actions) and not 2 because at least one concrete action is named, and not 4 because only a single action is listed.	3 / 5
Completeness	Both a "what" ("Formbricks integration. Manage Organizations.") and a "when" ("Use when the user wants to interact with Formbricks data.") are present, but the "what" is thin and the "when" is generic. It does not reach anchor 4 because neither side is sufficiently specific or concrete.	3 / 5
Trigger Term Quality	Includes the natural keyword "Formbricks" and the phrase "interact with Formbricks data", but lacks common synonyms or variations (surveys, forms, feedback, responses). Matches anchor 3 (some relevant keywords, missing variations) rather than 4 (good coverage).	3 / 5
Distinctiveness Conflict Risk	The named brand "Formbricks" gives it a clear niche with minimal conflict risk, but the generic trigger phrasing ("interact with Formbricks data") keeps it at anchor 4 rather than 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/formbricks/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.