Name: expofp
Rating: 53.6 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

expofp

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

Quality

60%

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

Quality

Content

63%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 concrete CLI commands and a clear, state-driven connection workflow with feedback loops. Its main weaknesses are mild verbosity/padding and a monolithic single-file structure that forgoes progressive disclosure.

Suggestions

Trim padded sentences such as the ExpoFP platform description and 'so you can focus on the integration logic rather than auth plumbing', and consolidate the Best practices section with the earlier guidance it repeats.

Move the proxy flag table and detailed action-schema field descriptions into a separate REFERENCE.md and link to it from the main file to apply progressive disclosure.

Add a brief upfront workflow summary (connect -> search -> run/proxy) so the end-to-end sequence is visible before the detailed steps.

Dimension	Reasoning	Score
Conciseness	The body is mostly concrete commands but includes unnecessary padding ('so you can focus on integration logic rather than auth plumbing', the generic ExpoFP platform description, and a Best practices section that restates earlier content), fitting 'mostly efficient but includes some unnecessary explanation'.	3 / 5
Actionability	It provides copy-paste-ready membrane CLI commands for install, login, connection ensure, action list/run, and proxy requests with a flag table, fitting 'mostly executable guidance; concrete code or commands with minor gaps' such as unsubstituted CONNECTION_ID placeholders.	4 / 5
Workflow Clarity	The connection setup is a clear sequence (ensure -> wait/poll for state -> handle CLIENT_ACTION_REQUIRED -> READY -> search -> run) with state-based checkpoints and an error-recovery feedback loop, fitting 'clear sequence with most checkpoints present; minor validation gaps'.	4 / 5
Progressive Disclosure	It is a single 150-line file with no bundle references and well-organized section headers, but content that could live in separate files (the proxy flag table, action-schema details) is inlined; at over 50 lines with no one-level-deep references it fits 'some structure but could be better organized' rather than a higher anchor.	3 / 5
	Total	14 / 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 is third-person, includes an explicit trigger clause, and ties to a distinct named platform, but its action verbs are generic fluff rather than concrete capabilities. Tightening 'Manage data, records, and automate workflows' into specific ExpoFP actions would raise specificity and completeness.

Suggestions

Replace generic verbs with concrete ExpoFP actions, e.g. 'Design floor plans, manage exhibitors and sessions, run check-ins and surveys'.

Add natural trigger synonyms/users, e.g. 'Use when the user mentions ExpoFP, event floor plans, exhibitor or booth management'.

Keep the explicit 'Use when...' clause but pair it with a sharper statement of what the skill does to push completeness toward 5.

Dimension	Reasoning	Score
Specificity	The description names the ExpoFP domain but the actions ('Manage data, records, and automate workflows') are generic verbs rather than concrete capabilities, matching the 'names the domain but actions are minimal or generic' anchor rather than a 3 whose example lists concrete acts like extraction.	2 / 5
Completeness	Both a 'what' (ExpoFP integration managing data/records/workflows) and an explicit 'Use when...' trigger are present, matching the anchor where both exist but the when could be more specific; it is not capped at 3 because the trigger clause is explicit.	4 / 5
Trigger Term Quality	'Use when the user wants to interact with ExpoFP data' surfaces the platform keyword but offers no common synonyms or variations, fitting the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	ExpoFP is a specific named platform giving it a clear niche and distinct trigger, but the broad 'manage data, records, automate workflows' phrasing leaves minor overlap risk with generic data skills, fitting 'mostly distinct; 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/expofp/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.