Name: emplifi
Rating: 64.8 (1 reviews)
Author: membranedev

emplifi

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

Quality

78%

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

Quality

Content

82%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 content is highly actionable with copy-paste commands and a strong, validated connection workflow with feedback loops. Weaknesses are minor prose padding and slightly inconsistent step numbering in the connection sequence.

Suggestions

Number the connection steps consistently (1: install, 2: authenticate, 3: connect, 4: wait for READY) and resolve the dangling 'Step 2' references to remove sequencing ambiguity.

Trim the soft justifications ('so you can focus on the integration logic rather than auth plumbing') to tighten token efficiency.

Consider moving the proxy flag table and connection state-machine details into a short reference file so the overview stays leaner.

Dimension	Reasoning	Score
Conciseness	The body is dominated by lean, executable commands with mostly relevant prose explaining the unfamiliar Membrane/Emplifi workflow rather than concepts Claude already knows; minor padding ('so you can focus on the integration logic rather than auth plumbing', 'This will burn less tokens') keeps it just below anchor 5.	4 / 5
Actionability	Fully executable, copy-paste-ready commands cover the common cases — install, login, connection ensure/get, action list/run, and request proxy — with a flags table and concrete JSON-input example, matching the 'specific examples cover the common cases' anchor.	5 / 5
Workflow Clarity	The connection flow is a clear state-driven sequence (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) with explicit feedback loops (re-poll after the user acts), but step labeling is inconsistent (a '1b' subsection and references to an unlabeled 'Step 2'), so it is just below anchor 5.	4 / 5
Progressive Disclosure	A single self-contained SKILL.md with well-organized sections and clear headers, no bundle files, and no nested references; it earns anchor 4 for good structure, falling short of 5 only because some longer material (the connection state machine, proxy flag table) could optionally live in a reference file.	4 / 5
	Total	17 / 20 Passed

Description

73%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 clearly names the product, includes an explicit 'Use when' trigger, and has minimal conflict risk. Its main weakness is generic capability language ('manage data, records') rather than concrete Emplifi-specific actions.

Suggestions

Replace generic verbs ('Manage data, records') with concrete Emplifi capabilities (e.g., 'manage social posts, comments, and authors') to lift specificity and completeness.

Add a couple of natural user phrasings or feature synonyms in the trigger clause (e.g., 'Use when the user wants to work with Emplifi posts, comments, or labels').

Dimension	Reasoning	Score
Specificity	Names the Emplifi domain and a few actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete Emplifi capabilities, so it sits at the '1-2 concrete actions, not comprehensive' anchor and not at 4 where actions become specific.	3 / 5
Completeness	Explicitly answers both 'what' ('Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with Emplifi data'), matching the anchor where both are present but the 'what' could be more concrete; it is not 5 because the capabilities are generic rather than concrete trigger phrases.	4 / 5
Trigger Term Quality	Good keyword coverage for a named product ('Emplifi', 'data', 'records', 'workflows') plus the natural trigger phrase 'Use when the user wants to interact with Emplifi data'; it is above anchor 3's single-keyword example but falls short of 5 because synonyms/variations are limited for a SaaS product name.	4 / 5
Distinctiveness Conflict Risk	Tied to a specific named product ('Emplifi integration', 'interact with Emplifi data'), giving it a clear niche with distinct triggers and minimal conflict risk with other skills.	5 / 5
	Total	16 / 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/emplifi/SKILL.md
Commit: f484c82

Reviewed: ~21 hours 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.