Name: foxy
Rating: 58.4 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

foxy

Foxy integration. Manage Organizations, Users, Goals, Filters. Use when the user wants to interact with Foxy data.

Quality

68%

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

Quality

Content

68%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 copy-paste CLI commands and a clear connection/auth workflow, but it loses conciseness to a vague overview section and lacks validation feedback loops for its destructive subscription/customer actions. Progressive disclosure is good given everything is sensibly sectioned inline with no bundle files.

Suggestions

Add a verify/confirm checkpoint before destructive actions (e.g., 'Before cancel-subscription or update-customer, confirm the target ID with the user and re-fetch the record afterward to verify the change').

Remove or replace the vague "Foxy Overview" list (Email/Label/Contact/Task + 'Use action names and parameters as needed') with concrete, useful content or delete it.

Fix the broken step cross-reference — 'skip to Step 2' has no labeled Step 2, and the '1b' numbering is inconsistent with the surrounding flow.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient CLI commands and tables, but the "Foxy Overview" list (Email/Label/Contact/Task) plus "Use action names and parameters as needed" is vague filler, and the intro sentence restates what Foxy is; fits 'mostly efficient but includes some unnecessary explanation'.	3 / 5
Actionability	It provides fully executable, copy-paste-ready commands with real flags (membrane login, connection ensure, action list/run, request) plus a concrete popular-actions table, matching 'fully executable; copy-paste ready; specific examples cover the common cases'.	5 / 5
Workflow Clarity	The connect/auth flow has strong state-based checkpoints and polling, but the skill exposes destructive operations (cancel/update subscription, update customer) with no validation or verify-then-proceed feedback loop, so the destructive-operation cap of 3 applies; not a 2 because the connection sequence is clearly sequenced and branched.	3 / 5
Progressive Disclosure	Content is well-organized into clearly headed sections (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices) with no external bundle files needed; fits 'good structure; most content appropriately placed; minor organization gaps' — the odd Foxy Overview section keeps it from a 5.	4 / 5
	Total	15 / 20 Passed

Description

67%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 concise and covers both what and when with an explicit trigger clause, but the trigger phrasing is generic and the single verb 'Manage' underspecifies the concrete actions available. It is distinct thanks to the named Foxy app but loses distinctiveness from generic SaaS entity terms.

Suggestions

Replace the generic verb 'Manage' with the specific operations the skill actually performs (e.g., list/create/update stores, coupons, subscriptions, transactions, customers) to match the body's real capabilities.

Tighten the trigger clause with concrete natural phrases users would say, e.g. 'Use when the user wants to query or update Foxy stores, coupons, subscriptions, or customer data.'

Align the named entities with the skill's actual surface area — the body covers Stores/Coupons/Subscriptions/Transactions/Customers, not Organizations/Users/Goals/Filters.

Dimension	Reasoning	Score
Specificity	Names the Foxy domain and lists several concrete managed entities ("Organizations, Users, Goals, Filters"), matching the 'lists several specific actions; minor gaps' anchor; not a 5 because the single verb 'Manage' is generic rather than enumerating distinct concrete actions.	4 / 5
Completeness	It answers both 'what' ("Manage Organizations, Users, Goals, Filters") and 'when' (explicit "Use when..." clause), matching the 'has both what and when; when could be more explicit' anchor; not a 5 because the trigger phrase "interact with Foxy data" is generic rather than concrete.	4 / 5
Trigger Term Quality	The trigger "Use when the user wants to interact with Foxy data" includes the natural keyword "Foxy"/"Foxy data" but misses common variations or synonyms, fitting the 'some relevant keywords but missing common variations' anchor; not a 4 because coverage is thin beyond the app name.	3 / 5
Distinctiveness Conflict Risk	"Foxy integration" ties triggers to a specific named app, giving a mostly distinct niche with minor overlap risk from the generic entity names (Users, Goals); not a 5 because those entity terms overlap with many SaaS skills.	4 / 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/foxy/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.