Name: enerflo
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

enerflo

Enerflo integration. Manage Organizations. Use when the user wants to interact with Enerflo data.

Quality

61%

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/enerflo/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 body gives strong, executable Membrane CLI guidance with a real connection-state feedback loop, but it is weighed down by a large redundant entity list and lacks any progressive-disclosure structure to offload bulk material.

Suggestions

Remove or collapse the ~110-line entity list, especially the duplicate "Installer X" entries; if needed, move the canonical entity list to a references/ file and link to it.

Provide one complete worked example with substituted values (real CONNECTION_ID and a sample actionId) so the commands are fully copy-paste ready.

Fix the dangling "Step 2" reference by numbering the workflow steps consistently (Step 1: connect, Step 2: search/run).

Dimension	Reasoning	Score
Conciseness	A ~110-line entity list dominated by redundant "Installer X" duplicates is pure padding Claude does not need, and phrases like "so you can focus on the integration logic rather than auth plumbing" add fluff. Not a 3 because the redundant list is a major padded section, not a minor one.	2 / 5
Actionability	Provides concrete, executable Membrane commands (login, connection ensure, action list/run, request) plus a popular-actions table. Not a 5 because placeholders (CONNECTION_ID, <actionId>, <agentType>) are never filled and no single complete worked example ties them together.	4 / 5
Workflow Clarity	Clear install -> auth -> connect -> search -> run sequence with explicit state-polling checkpoints (poll until not BUILDING, re-poll after CLIENT_ACTION_REQUIRED, handle CONFIGURATION_ERROR). Not a 5 because step numbering is inconsistent ("skip to Step 2" has no matching Step 2 header) and some checkpoints are implicit.	4 / 5
Progressive Disclosure	Single 287-line file with reasonable section headers but no external references, and the bulky entity list is inlined content that belongs in a separate reference file. Not a 4 because content that should be split out is inline; not a 2 because the section organization is otherwise coherent.	3 / 5
	Total	13 / 20 Passed

Description

66%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 includes an explicit Use-when trigger and names a distinct app, but the capability statement is thin and generic. It is distinguishable yet light on concrete actions and natural-term variety.

Suggestions

Replace the generic "Enerflo integration. Manage Organizations." with 2-3 concrete actions users request, e.g. "List and update Enerflo customers, deals, installs, and tasks."

Add natural trigger variations and synonyms, e.g. "Use when the user wants to query Enerflo leads, deals, or installation data."

Dimension	Reasoning	Score
Specificity	Names the domain (Enerflo) and one concrete action ("Manage Organizations"), but coverage is minimal and not comprehensive. Not a 2 because a concrete action is named; not a 4 because only one thin action is listed.	3 / 5
Completeness	Both a "what" ("Enerflo integration. Manage Organizations.") and an explicit "when" ("Use when the user wants to interact with Enerflo data.") are present. Not a 5 because the "what" is generic and lacks concrete trigger phrases; the explicit Use-when clause keeps it above 3.	4 / 5
Trigger Term Quality	Contains relevant keywords ("Enerflo", "Enerflo data", "interact with Enerflo") but lacks common variations or synonyms a user might say. Not a 4 because the natural-term coverage is limited to the app name and one verb.	3 / 5
Distinctiveness Conflict Risk	Targets a specific named third-party app (Enerflo) with a distinct trigger ("interact with Enerflo data"), giving it a clear niche with minimal conflict risk against other skills.	5 / 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/enerflo/SKILL.md
Commit: f484c82

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