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

xperiencify

Xperiencify integration. Manage data, records, and automate workflows. Use when the user wants to interact with Xperiencify 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/xperiencify/SKILL.md

Quality

Content

56%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 CLI integration workflow is concrete, executable, and well-checkpointed, but the body is bloated by a ~90-item inlined entity list with no actions. Moving reference material into a bundled file and trimming generic explanation would materially improve token efficiency and structure.

Suggestions

Move the entity list into a references/ file (e.g. ENTITIES.md) and link to it from the overview instead of inlining ~90 nouns.

Trim or remove the platform-intro paragraph and the generic entity list, keeping only what Claude cannot infer; add one concrete `action run` example with a real action id and input JSON.

Add a verification checkpoint before running mutating actions (e.g. inspect outputSchema or dry-run) so the search→run→proxy path matches the connection flow's rigor.

Dimension	Reasoning	Score
Conciseness	The body includes a ~90-item noun-only entity list (Course, Student, ... Setting) and an explanatory platform intro that pad the context without actionable detail, matching the anchor for noticeably verbose content with several padded sections. It is above a 1 because the CLI workflow sections themselves are efficient and command-focused, but the bulk entity dump keeps it below a 3.	2 / 5
Actionability	The workflow provides copy-paste-ready, executable commands (`npm install -g @membranehq/cli@latest`, `membrane connection ensure`, `membrane action run`, `membrane request`) plus a concrete proxy-options table. It is not a 5 because no example uses a real action id or parameter values, and the entity list section offers only the vague nudge "Use action names and parameters as needed."	4 / 5
Workflow Clarity	The connection flow is clearly sequenced (install → login → connection ensure → poll for READY) with explicit state checkpoints (READY, BUILDING, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) and a feedback loop (poll again after the user acts). It is below a 5 because the later search→run→proxy path has no verification step before executing actions.	4 / 5
Progressive Disclosure	The file has section headers and is reasonably organized, but there are no bundle files (references/scripts/assets are absent) and the large entity reference list is inlined in SKILL.md rather than split out, matching the anchor where content that should be separate is inline with only modest structure. It is above a 2 because headers and a logical flow exist, but below a 4 because nothing is offloaded to a referenced file.	3 / 5
	Total	13 / 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 correctly pairs a third-person "what" with an explicit "Use when" trigger and is distinctive via the product name, but its actions and trigger keywords are generic. Adding concrete Xperiencify-specific terms would lift specificity and trigger coverage.

Suggestions

Replace generic verbs with concrete capabilities, e.g. "Manage courses, students, enrollments, XP points, and automations in Xperiencify."

Expand the trigger clause with natural user phrasing: "Use when the user wants to manage Xperiencify courses, students, enrollments, gamification, or automation workflows."

Add file-format or entity synonyms (courses, students, XP, certificates) so activation matches varied user wording.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Xperiencify domain and lists three actions, but they are generic verbs rather than concrete capabilities, matching the anchor that lists 1-2 concrete actions without comprehensive coverage. It is above a 2 because multiple actions are named, but below a 4 because none are specific (e.g. no mention of courses, students, XP, or automations).	3 / 5
Completeness	Both halves are present: a "what" ("Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with Xperiencify data"). It is not a 5 because the "what" is generic and the single trigger phrase lacks the concrete variations seen in the top anchor.	4 / 5
Trigger Term Quality	"Use when the user wants to interact with Xperiencify data" surfaces the product name and "data" but omits the natural terms users would actually say (courses, students, enrollment, gamification, engagement, XP). This matches the anchor with some relevant keywords but missing common variations or synonyms; it falls short of a 4 due to thin keyword coverage.	3 / 5
Distinctiveness Conflict Risk	Naming the specific product ("Xperiencify integration", "interact with Xperiencify data") gives a clear niche with minimal conflict risk. It stays at 4 rather than 5 because the surrounding actions (manage data, records, automate workflows) are generic and could overlap with other data-management skills.	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/xperiencify/SKILL.md
Commit: f484c82

Reviewed: 3 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.