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

Blog Docs Log in Get started

frollo

Frollo integration. Manage data, records, and automate workflows. Use when the user wants to interact with Frollo 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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/frollo/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 action-oriented with executable Membrane CLI commands and a well-validated connection workflow, but it carries some padded prose and inconsistent step numbering that slightly weaken conciseness and workflow clarity.

Suggestions

Trim marketing-style prose (e.g. the Frollo overview paragraph and 'so you can focus on the integration logic') to assume Claude's competence.

Fix step numbering: label the connection steps consistently (1a/1b and an explicit 'Step 2') so the 'skip to Step 2' references resolve.

Merge or differentiate the 'Popular actions' and 'Searching for actions' sections to remove redundancy.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands, but includes unnecessary prose such as the marketing-style Frollo intro and phrases like 'so you can focus on the integration logic rather than auth plumbing' and 'This will burn less tokens'.	3 / 5
Actionability	Provides mostly executable, copy-paste-ready commands (install, login, connection ensure, action run, proxy with a flags table), with only minor gaps like unresolved CONNECTION_ID placeholders and the 'replace QUERY' intent.	4 / 5
Workflow Clarity	The connection setup has a clear sequence with real validation feedback loops (polling state, handling CLIENT_ACTION_REQUIRED, re-polling, error states), but step numbering is inconsistent ('Step 2' is referenced but never labeled, '1b' appears without a '1a').	4 / 5
Progressive Disclosure	Well-organized into clear sections with no external bundle files to reference, though the 'Popular actions' section partially duplicates 'Searching for actions' and the skill exceeds the 50-line simple-skill threshold.	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 answers both 'what' and 'when' and is anchored to a distinctive named app, but its action verbs are generic and its trigger terms lack synonyms. It is solid but could be sharpened with concrete Frollo capabilities.

Suggestions

Replace generic verbs ('Manage data, records') with concrete Frollo capabilities such as 'track spending, set budgets, and manage transactions'.

Expand the trigger clause with natural synonyms users might say, e.g. 'Use when the user wants to track spending, view transactions, or manage budgets in Frollo'.

Dimension	Reasoning	Score
Specificity	Names the Frollo domain plus a few actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete Frollo-specific operations like tracking spending or setting budgets.	3 / 5
Completeness	States both what it does ('Manage data, records, and automate workflows') and when to use it ('Use when the user wants to interact with Frollo data'), though the 'when' clause is somewhat generic.	4 / 5
Trigger Term Quality	Includes the distinctive keyword 'Frollo' and the natural phrase 'interact with Frollo data', but lacks common variations or synonyms users might say.	3 / 5
Distinctiveness Conflict Risk	Names a specific third-party app (Frollo) with a distinctive trigger phrase, giving it a clear niche and minimal conflict risk with other skills.	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/frollo/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.