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

Blog Docs Log in Get started

phaxio

Phaxio integration. Manage Accounts. Use when the user wants to interact with Phaxio 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/phaxio/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 highly actionable with copy-paste Membrane CLI commands and a well-structured connection workflow that includes real validation checkpoints. Its main weaknesses are an unnecessary introductory explanation of faxing and small polish issues like a duplicated overview entry and an unreferenced 'Step 2'.

Suggestions

Cut the three-sentence fax-101 introduction; assume Claude knows what a fax API is and lead directly with what the skill does.

Fix the duplicated 'Account' entry in the Phaxio Overview list and align the 'Step 2' reference with an actual numbered step.

Add a brief validation note after `membrane action run` (e.g. check the `output`/`error` field before proceeding) to close the workflow-clarity gap.

Dimension	Reasoning	Score
Conciseness	The body opens by explaining that Phaxio is 'a cloud-based fax API' that 'eliminates the need for traditional fax machines' — concept padding Claude already knows — and the overview list duplicates an 'Account' entry, so it is mostly efficient but includes unnecessary explanation that could be trimmed.	3 / 5
Actionability	It provides concrete, executable commands throughout (install, login, connection ensure, action list/run, request) plus a flags table; minor gaps remain since no worked example shows a fully populated action run with real input values.	4 / 5
Workflow Clarity	The connect-to-Phaxio flow is clearly sequenced with explicit state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll-until-ready feedback loop; the gap is that running actions lacks result validation, and 'Step 2' is referenced without a matching numbered step.	4 / 5
Progressive Disclosure	Sections are well organized (Overview, Working with Phaxio, Install, Auth, Connecting, Searching, Actions, Proxy, Best practices) with no bundle files to reference; the proxy flags table and detailed clientAction handling are reasonable inline content rather than separate files, leaving only minor organization gaps.	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 correctly pairs a 'what' with an explicit 'Use when...' trigger and leverages a distinctive brand name, but it is thin on concrete capabilities and omits the obvious 'fax' trigger term. Tightening the 'what' to mention sending/receiving faxes would lift specificity and trigger quality.

Suggestions

Replace the generic 'Manage Accounts' with concrete fax actions, e.g. 'Send and receive faxes, manage phone numbers and PhaxCode media.'

Add the natural trigger term 'fax' to the 'Use when' clause so users who say 'send a fax' surface the skill.

Mention that Phaxio is a fax API in the description so the 'what' is self-explanatory without the body.

Dimension	Reasoning	Score
Specificity	The phrase 'Manage Accounts' names the Phaxio domain but offers only a single, generic action and ignores the core fax send/receive capabilities, fitting 'names the domain but actions are minimal or generic' rather than the more comprehensive anchor 3.	2 / 5
Completeness	It states a 'what' ('Phaxio integration. Manage Accounts.') and an explicit 'when' ('Use when the user wants to interact with Phaxio data.'), satisfying both; the 'when' is present but the 'what' is narrow, so it falls short of the fully concrete anchor 5.	4 / 5
Trigger Term Quality	It includes the strong brand keyword 'Phaxio' and 'Accounts', but never surfaces the most natural user term 'fax' (send/receive fax), so it has relevant keywords while missing common synonyms.	3 / 5
Distinctiveness Conflict Risk	The Phaxio brand name and 'interact with Phaxio data' create a mostly distinct niche with minor overlap risk from the generic 'Manage Accounts' phrasing, rather than the minimal-conflict anchor 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/phaxio/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.