Name: frontegg
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

frontegg

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

Quality

64%

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

Quality

Content

73%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 ready-to-run CLI commands and a clear state-driven connection workflow. The main gaps are some padding in the intro/overview and missing validation feedback loops for state-mutating actions.

Suggestions

Trim the opening paragraph explaining what Frontegg is — Claude already knows this — and cut the generic 'Use action names and parameters as needed' line.

Add an explicit validation/verify step after running actions or proxy POSTs, e.g. re-query or inspect the `output` field to confirm the change took effect.

Move the 16-entity overview list into a separate reference file and link to it from SKILL.md to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with executable commands throughout, but the opening paragraph restates what Frontegg is ('a user management and authentication platform...') and the overview lists 16 entities with the filler line 'Use action names and parameters as needed' that could be trimmed; fits 'mostly efficient but could be tightened', not a 4 due to the padded intro and entity list.	3 / 5
Actionability	Provides copy-paste-ready CLI commands for install, login, connection ensure, polling, action search/run, and proxy requests, plus a complete options table — fully executable covering the common cases; matches the anchor 'fully executable, copy-paste ready'.	5 / 5
Workflow Clarity	The connection flow is well sequenced with state-based branching (READY / BUILDING / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and explicit polling checkpoints, but operations that modify Frontegg state (running actions, proxy POSTs) lack validation or verify-the-result feedback loops, so it sits at 4 rather than 5.	4 / 5
Progressive Disclosure	Good section structure (Overview, Working with Frontegg, Popular actions, Best practices) with the inlined content appropriately scoped to CLI usage and no nested multi-level references; not a 5 only because the 16-entity overview list could live in a separate reference file and no bundle exists to offload it.	4 / 5
	Total	16 / 20 Passed

Description

55%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 the Frontegg domain and includes an explicit 'Use when' trigger, but its actions are generic ('manage data, records, automate workflows') rather than reflecting Frontegg's actual capabilities (auth, roles, SSO, billing). Strengthening specificity and trigger-term coverage would lift it from good to strong.

Suggestions

Replace generic verbs with Frontegg-specific capabilities, e.g. 'Manage users, roles, SSO, audit logs, and subscriptions in Frontegg'.

Add natural trigger terms users would say, such as 'when the user mentions authentication, user management, SSO, or permissions in Frontegg'.

Tighten the 'when' clause to concrete triggers rather than the vague 'interact with Frontegg data'.

Dimension	Reasoning	Score
Specificity	Names the Frontegg domain but the actions are generic ('Manage data, records, and automate workflows') rather than concrete Frontegg capabilities (roles, SSO, audit logs, billing), fitting the 'Names domain but actions minimal/generic' anchor; not a 3 since no genuinely Frontegg-specific concrete actions are listed.	2 / 5
Completeness	Has both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Frontegg data'), but the 'when' is fairly generic rather than a concrete trigger phrase, so it sits at 4 rather than 5.	4 / 5
Trigger Term Quality	Includes 'Frontegg' as the primary natural term and 'interact with Frontegg data', but offers no synonyms or common variations users would say (auth, SSO, user management, permissions); matches 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	The 'Frontegg' niche is specific and unlikely to trigger for the wrong skill, though 'Manage data, records, and automate workflows' is broad and could overlap with other data skills; mostly distinct with minor overlap risk.	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/frontegg/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.