Name: firmao
Rating: 64 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

firmao

Firmao integration. Manage Organizations, Users. Use when the user wants to interact with Firmao data.

Quality

76%

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

Quality

Content

92%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 highly actionable with executable commands and a well-sequenced, validated connection workflow; structure and navigation are clean for a single-file skill. The only minor weakness is a brief introductory paragraph that lightly over-explains Firmao's purpose.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but the opening paragraph explaining what Firmao is and who uses it is mild over-explanation Claude largely already knows. Matches anchor 4 (efficient, minor over-explanation) rather than 5, which demands every token earn its place.	4 / 5
Actionability	Provides copy-paste-ready, fully executable commands throughout (login, connection ensure, action list/run, request) with flags and JSON-input examples covering common cases. Matches anchor 5 (fully executable, covers common cases) rather than 4, which allows minor gaps.	5 / 5
Workflow Clarity	The connection flow is a clearly sequenced state machine with explicit validation checkpoints and feedback loops (poll until not BUILDING; CLIENT_ACTION_REQUIRED → user acts → re-poll; CONFIGURATION_ERROR/SETUP_FAILED → check error). Matches anchor 5 (clear sequence, explicit validation, error-recovery loops) rather than 4.	5 / 5
Progressive Disclosure	A single well-organized file with clean section headers and no nested or buried references; no external files are needed and nothing that belongs elsewhere is inlined. Matches anchor 5 (clear overview, easy navigation, appropriately split) rather than 4.	5 / 5
	Total	19 / 20 Passed

Description

61%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 answers both what and when and is firmly scoped to Firmao, but it is sparse on concrete actions and natural trigger terms. Expanding verbs and synonyms (CRM, invoices, contacts, tasks) would lift the specificity and trigger dimensions.

Suggestions

Replace the generic verb 'Manage' with concrete actions, e.g. 'Create and list customers, invoices, tasks, and contacts in Firmao'.

Add natural trigger synonyms users would say, such as 'CRM', 'invoices', 'contacts', 'customers', or 'projects', to broaden trigger coverage.

Tighten the 'when' clause to reference concrete Firmao objects (e.g. 'Use when the user wants to manage Firmao CRM records, invoices, or tasks').

Dimension	Reasoning	Score
Specificity	Names the Firmao domain and two resource types ('Manage Organizations, Users') but the verb 'Manage' is generic with no concrete actions listed. It matches anchor 2 (domain named, actions minimal/generic) and not 3, which requires 1-2 concrete actions.	2 / 5
Completeness	Both 'what' ('Firmao integration. Manage Organizations, Users.') and 'when' ('Use when the user wants to interact with Firmao data') are present and explicit, but the trigger is generic. Matches anchor 4 (both present, 'when' could be more specific) — not 5 because trigger phrases lack concrete terms like CRM or invoices.	4 / 5
Trigger Term Quality	Includes 'Firmao' and 'interact with Firmao data' but misses natural synonyms prominent in the body (CRM, invoices, contacts, customers, tasks). Matches anchor 3 (some relevant keywords, missing common variations) rather than 4, which needs broader natural-term coverage.	3 / 5
Distinctiveness Conflict Risk	Clearly scoped to a named product (Firmao) with Firmao-specific triggers, giving a distinct niche and minimal conflict risk. Matches anchor 5 rather than 4, which still implies overlap risk with closely related skills.	5 / 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/firmao/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.