Name: faktoora
Rating: 56.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

faktoora

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

Quality

65%

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

Quality

Content

65%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 complete, executable CLI commands and a clear connection state machine. Its main gaps are redundancy between the search and best-practices sections, a broken step numbering scheme, a large inlined actions table that belongs in a separate file, and no validation guidance for the destructive delete operations it advertises.

Suggestions

Add a validation/confirmation checkpoint before destructive actions (delete-invoice, delete-product, delete-customer) and fix the broken "Step 2" reference by labeling the sequence steps explicitly.

Move the 20-row Popular actions table into a references file (e.g. references/actions.md) and link to it from SKILL.md to improve progressive disclosure and token efficiency.

De-duplicate the "Discover before you build" best practice against the "Searching for actions" section to remove redundant guidance.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but the "Best practices" section restates the "Searching for actions" guidance ("Discover before you build" vs. the search section) and the 20-row Popular actions table is inline bulk. It fits the mostly-efficient-with-some-tightening-needed anchor rather than the lean anchor at 4.	3 / 5
Actionability	Provides fully executable, copy-paste-ready commands (npm install, membrane login, connection ensure, action run, request) plus a concrete actions table covering common cases. It clearly matches the fully-executable top anchor.	5 / 5
Workflow Clarity	The connection flow has a state-check sequence (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) with a polling feedback loop, but the step numbering is broken (references "Step 2" with no labeled Step 2) and destructive Delete actions are listed with no validation or confirmation guidance. The destructive-operations cap holds it at 3 rather than 4.	3 / 5
Progressive Disclosure	No bundle files exist (references/scripts/assets absent) and the large Popular actions reference table is inlined in SKILL.md rather than split into a referenced file. Structure is present via clear sections, fitting the some-structure-but-could-be-better-organized anchor instead of the minimal-structure anchor at 2.	3 / 5
	Total	14 / 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 names a specific product and includes an explicit "Use when" trigger, giving it strong distinctiveness and adequate completeness. Its weakness is specificity and trigger coverage: it only mentions "Manage Organizations" and omits the invoice, customer, and product operations the skill actually supports.

Dimension	Reasoning	Score
Specificity	Names the domain ("Faktoora integration") and one concrete action ("Manage Organizations") but offers no comprehensive list, matching the anchor for a domain plus 1-2 actions. It does not reach 4 because the single action is narrow and omits the invoice/customer/product capabilities the body actually exposes.	3 / 5
Completeness	Provides both a "what" ("Faktoora integration. Manage Organizations.") and an explicit "Use when the user wants to interact with Faktoora data" trigger. It is not 5 because the "what" is thin and the trigger could be more specific about which Faktoora tasks apply.	4 / 5
Trigger Term Quality	Includes relevant keywords ("Faktoora", "Organizations", "interact with Faktoora data") but lacks natural synonyms or variations a user might say. It is above 2 because the named product term is concrete, but below 4 since common phrasings like invoices, accounting, or billing are absent.	3 / 5
Distinctiveness Conflict Risk	Targets a named, distinct product ("Faktoora") with a clear niche trigger ("interact with Faktoora data"), giving minimal overlap risk with other skills. It clearly fits the top anchor rather than the mostly-distinct anchor at 4.	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/faktoora/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.