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

whatfix

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

Quality

58%

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/whatfix/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 Membrane integration workflow is concrete and well-sequenced with real validation checkpoints for connection state. The skill is dragged down by a ~270-line generic keyword list that is pure padding and by the absence of output validation around action execution.

Suggestions

Delete the 'Whatfix Overview' bullet list (or move it to a reference file): it is duplicated, non-actionable padding that wastes context.

Add a validation/verification step after `membrane action run` (e.g., inspect the `output` field, check for error states) especially for destructive or batch actions.

Resolve the placeholder values (CONNECTION_ID, actionId) in examples with a short note on where they come from, or show a concrete end-to-end example.

Dimension	Reasoning	Score
Conciseness	The 'Whatfix Overview' section is ~270 lines of generic, often duplicated bullet terms (Backup, Certificate, Log each repeat) with no explanatory value — a heavily padded keyword dump; not a 1 only because the Membrane CLI sections are reasonably efficient.	2 / 5
Actionability	Provides concrete, copy-paste-ready commands (install, login, connection ensure, action list/run, request) with a flags table; not a 5 because some examples leave placeholders (CONNECTION_ID, actionId) and the overview list contributes no executable guidance.	4 / 5
Workflow Clarity	Clear install→auth→connect→discover→run sequence with an explicit validation checkpoint (polling connection state through READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR); not a 5 because there is no validation/verification of action-run output for potentially destructive or batch actions.	4 / 5
Progressive Disclosure	Section headers organize the CLI content and no external references are used, but the large inline overview list is content that should be removed or split out, leaving structure that could be better organized; not a 4 because of that misplaced inline bulk.	3 / 5
	Total	13 / 20 Passed

Description

61%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 cleanly states both what the skill does and when to use it, anchored to a distinct named platform. Its main weakness is generic, non-concrete action language ('manage data, records, automate workflows') that could name specific Whatfix capabilities.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with 2-3 concrete Whatfix capabilities (e.g., flows, tasks, segments, analytics) to lift specificity.

Add natural trigger synonyms users say (e.g., 'Whatfix flows', 'Whatfix guides', 'Whatfix analytics') to broaden trigger-term coverage.

Tighten the 'when' clause to reference concrete Whatfix objects rather than the vague 'interact with Whatfix data'.

Dimension	Reasoning	Score
Specificity	Names the Whatfix domain but the actions ('Manage data, records, and automate workflows') are minimal and generic rather than concrete, matching the 'names the domain but actions are minimal or generic' anchor; not a 3 because no genuinely concrete capability is listed.	2 / 5
Completeness	Both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Whatfix data') are present; not a 5 because the 'what' is generic and the 'when' is not tied to concrete trigger phrases.	4 / 5
Trigger Term Quality	'Whatfix' and 'interact with Whatfix data' give some natural keywords a user would say, but common variations/synonyms are missing, fitting the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Naming the specific Whatfix platform with a Whatfix-scoped trigger creates a clear niche with minimal conflict risk against other skills.	5 / 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/whatfix/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.