Name: fusionauth
Rating: 52.8 (1 reviews)
Author: membranedev

fusionauth

FusionAuth integration. Manage data, records, and automate workflows. Use when the user wants to interact with FusionAuth data.

Quality

59%

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

Quality

Content

57%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 command-rich and actionable with a well-instrumented connection workflow, but it is padded with conceptual explanation, lacks validation around destructive proxy operations, and is monolithic with no progressive disclosure to sub-files.

Suggestions

Remove the introductory 'FusionAuth is an authentication...' paragraph and other explanatory prose that Claude already knows, to tighten conciseness.

Add an explicit validation/verification step after destructive proxy requests (e.g. re-fetch the resource or check the response status before proceeding).

Move the proxy flag reference table and clientAction state-machine details into separate reference files linked one level deep from SKILL.md to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Mostly efficient command-focused content, but it includes unnecessary padding such as the introductory 'FusionAuth is an authentication and authorization platform...' paragraph and prose like 'so you can focus on the integration logic rather than auth plumbing', matching 'Mostly efficient but includes some unnecessary explanation'.	3 / 5
Actionability	Concrete executable commands abound (npm install, membrane login, connection ensure, action run, request) with a full flag table, but placeholders like CONNECTION_ID and a few high-level descriptions leave minor gaps, matching 'Mostly executable guidance; concrete code or commands with minor gaps'.	4 / 5
Workflow Clarity	The connection workflow has clear state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and re-polling feedback, but the proxy and action-run workflows support destructive operations (DELETE) with no validation/verification step, invoking the destructive-operation cap at 3.	3 / 5
Progressive Disclosure	The single ~163-line SKILL.md has decent section headers but no bundle files or external references, and content that could live in separate files (the proxy flag table, clientAction state details) is inlined, matching 'Some structure but could be better organized'.	3 / 5
	Total	13 / 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 names a distinct product niche and includes an explicit 'Use when' trigger, but its capability phrasing ('manage data, records, automate workflows') is generic and lacks concrete actions or natural keyword variations.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete FusionAuth actions such as 'create and manage users, registrations, tenants, applications, and groups'.

Add natural trigger terms a user would say, e.g. 'Use when the user wants to manage FusionAuth users, registrations, SSO, or authentication flows'.

Tie the 'when' clause to specific FusionAuth entities (users, tenants, applications) to sharpen trigger matching.

Dimension	Reasoning	Score
Specificity	Phrases 'Manage data, records, and automate workflows' name the FusionAuth domain but the actions are minimal and generic rather than concrete, matching the 'Names the domain but actions are minimal or generic' anchor rather than the level-3 anchor which requires 1-2 truly concrete actions.	2 / 5
Completeness	It states what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with FusionAuth data'), but the 'when' could be more specific, matching the 'Has both what and when; when could be more explicit' anchor rather than the fully concrete level-5 example.	4 / 5
Trigger Term Quality	'interact with FusionAuth data' surfaces the product name as a keyword but misses common natural variations or synonyms a user might say, matching the 'Some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	'FusionAuth integration' targets a clearly named product niche with distinct triggers and minimal overlap with other skills, matching the 'Clear niche with distinct triggers; minimal conflict risk' anchor.	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/fusionauth/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.