Name: regfox
Rating: 59.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

regfox

RegFox integration. Manage Events. Use when the user wants to interact with RegFox data.

Quality

69%

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

Quality

Content

76%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 executable commands and a solid connection workflow, but workflow clarity is capped by missing validation before destructive proxy operations and a dangling step reference. It is well-structured and mostly concise.

Suggestions

Add an explicit validation/verification checkpoint before destructive proxy requests (DELETE/PUT/PATCH) — e.g. dry-run or confirm-then-retry guidance — to lift workflow_clarity above 3.

Fix the dangling 'skip to Step 2' reference by numbering the connecting/running sections as Step 1 and Step 2 (or remove the cross-reference).

Tighten filler lines like 'Use action names and parameters as needed.' and the typo 'burn less tokens' (fewer tokens) to improve conciseness.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean executable bash commands with justified context for the niche RegFox/Membrane tooling. Minor trimmable filler exists (e.g. "Use action names and parameters as needed.", "This will burn less tokens"), keeping it just below 5.	4 / 5
Actionability	Provides fully executable, copy-paste-ready commands for install, login, connection, action listing/running, and proxying, plus a complete proxy flag table and concrete state-handling examples. Examples cover the common cases.	5 / 5
Workflow Clarity	A clear sequence (install, auth, connect, poll until READY, search, run, proxy) exists with state feedback, but destructive proxy methods (DELETE/PUT/PATCH) have no validation/verification checkpoint, which caps workflow_clarity at 3 per the destructive-operations guideline. A dangling 'skip to Step 2' reference also breaks the sequence.	3 / 5
Progressive Disclosure	Well-organized into clearly labeled sections with no external bundle references and nothing that clearly demands splitting into separate files. It is not 5 because there is no explicit one-level-deep reference structure and a few sections (e.g. the thin 'RegFox Overview') could be better integrated.	4 / 5
	Total	16 / 20 Passed

Description

62%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 is short and includes both a 'what' and a 'Use when' trigger, but it is thin on concrete capabilities and natural trigger variations. It is clear enough to avoid most conflicts thanks to the RegFox product name.

Suggestions

Add 2-3 concrete actions beyond 'Manage Events' (e.g. 'create events, manage registrations, pull attendee reports') to raise specificity.

Expand the 'Use when' clause with natural trigger phrases users say (e.g. 'when the user mentions RegFox events, registrations, or ticketing').

Confirm third-person voice is preserved throughout; the current phrasing already complies, so keep new additions in the same voice.

Dimension	Reasoning	Score
Specificity	Names the domain ("RegFox integration") and one action ("Manage Events"), but the action is generic and coverage is not comprehensive. It sits at the '1-2 concrete actions' anchor rather than 4 because no further specific capabilities are listed.	3 / 5
Completeness	Both 'what' ("Manage Events") and 'when' ("Use when the user wants to interact with RegFox data") are present and the trigger is explicit. It is not 5 because the 'what' is thin and the trigger could be more specific.	4 / 5
Trigger Term Quality	Includes the natural term "RegFox" and an explicit "Use when the user wants to interact with RegFox data" trigger, but lacks synonyms or variations (e.g. registration, ticketing, .xlsx-like extensions) users might say.	3 / 5
Distinctiveness Conflict Risk	RegFox is a distinct product giving it a clear niche and minimal conflict risk, but "Manage Events" alone is generic enough to risk minor overlap with other event-management skills, keeping it below 5.	4 / 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/regfox/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.