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

Blog Docs Log in Get started

fonoa

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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/fonoa/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 content is a well-structured, actionable CLI guide with a clear connection state machine and feedback loop. Its main weaknesses are marketing-fluff padding, redundant sections, and slightly inconsistent step labeling.

Suggestions

Remove marketing-fluff sentences (e.g. "so you can focus on the integration logic rather than auth plumbing", "burn less tokens and make communication more secure") that do not aid execution.

Merge the redundant "Searching for actions" and "Popular actions" sections into a single action-discovery section.

Fix the step labeling so "skip to Step 2" and "1b" map to clearly numbered, labeled steps in the connection workflow.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but includes marketing-fluff sentences ("so you can focus on the integration logic rather than auth plumbing", "burn less tokens and make communication more secure") and a redundant overlap between the "Searching for actions" and "Popular actions" sections.	3 / 5
Actionability	It provides concrete, executable commands throughout (membrane login, connection ensure, action list/run, request) plus a full proxy flag table, but placeholders like CONNECTION_ID and a generic JSON input example leave minor gaps versus fully copy-paste end-to-end cases.	4 / 5
Workflow Clarity	The connection flow is a clear state machine with polling and a feedback loop (CLIENT_ACTION_REQUIRED -> user acts -> poll again), but the labels "skip to Step 2" and "1b" reference steps that are not cleanly numbered, a minor clarity gap.	4 / 5
Progressive Disclosure	The body is well-organized into clear sections with an overview, and there are no problematic nested references (no bundle files exist), but the redundancy between the two action-listing sections is a minor organization gap.	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 provides an explicit Use-when clause and names the Fonoa domain, but its action verbs are generic and it lacks concrete trigger synonyms. It is mostly distinct and complete without being comprehensive.

Suggestions

Replace generic verbs with concrete Fonoa actions, e.g. "Calculate tax, issue invoices, and manage transactions via Fonoa."

Add natural trigger synonyms to the when-clause, e.g. "Use when the user wants to calculate tax, issue invoices, manage VAT/GST, or interact with the Fonoa API."

Tighten the what-clause so it lists 1-2 specific capabilities rather than the abstract "manage data, records, and automate workflows".

Dimension	Reasoning	Score
Specificity	Names the domain ("Fonoa integration") but the verbs are generic ("Manage data, records, and automate workflows") with no concrete actions like calculate tax, issue invoices, or query transactions, matching the anchor where actions are minimal or generic.	2 / 5
Completeness	It has both a what ("Manage data, records, and automate workflows") and an explicit when ("Use when the user wants to interact with Fonoa data"), but the when could name more concrete trigger phrases, matching the anchor for both present with the when improvable.	4 / 5
Trigger Term Quality	"Fonoa" and "Fonoa data" are relevant natural keywords, but common variations/synonyms a user might say (tax, VAT, invoices, transactions, API) are absent, fitting the anchor for some relevant keywords missing common variations.	3 / 5
Distinctiveness Conflict Risk	The trigger is tied to the named app Fonoa, giving a mostly distinct niche with minimal conflict risk, though the generic "manage data" phrasing leaves minor overlap with similar data skills.	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/fonoa/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.