Name: eploy
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

eploy

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

Quality

66%

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

Quality

Content

75%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 a well-structured, actionable guide to driving Eploy via the Membrane CLI, with executable commands and validation feedback loops for connection setup. Its main weaknesses are a broken Step 2 reference, some light prose padding, and no concrete Eploy-specific end-to-end example.

Suggestions

Fix or remove the dangling 'skip to Step 2' reference by labeling the connection and action-discovery steps explicitly (e.g. 'Step 1: Connect', 'Step 2: Discover and run actions').

Add one concrete Eploy-specific worked example, such as listing candidates or fetching a job's applications, to replace the generic /path/to/endpoint placeholder.

Trim explanatory filler like 'so you can focus on the integration logic rather than auth plumbing' to tighten token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with copy-pasteable commands and a flags table, but includes light over-explanation such as 'so you can focus on the integration logic rather than auth plumbing' that could be trimmed.	4 / 5
Actionability	It provides concrete executable commands for install, login, connection, action list/run, and proxy requests with a flag table; the minor gap is the absence of a concrete Eploy-specific end-to-end example (only generic placeholders like CONNECTION_ID and /path/to/endpoint).	4 / 5
Workflow Clarity	The connection setup has a clear sequence with feedback loops (poll --wait, handle CLIENT_ACTION_REQUIRED, re-poll until READY), but the dangling 'skip to Step 2' reference with no defined Step 1/Step 2 labels is a minor sequencing gap.	4 / 5
Progressive Disclosure	Content is well-organized under clear section headers in a single file with no nested references; since the skill exceeds 50 lines and is monolithic rather than split into reference files, it stops short of the top anchor.	4 / 5
	Total	16 / 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 has an explicit trigger clause and is distinctive via the Eploy product name, but its action vocabulary is generic and lacks recruitment-specific concreteness. It is adequate but not comprehensive.

Suggestions

Replace generic actions ('Manage data, records, and automate workflows') with concrete Eploy capabilities such as managing jobs, candidates, applications, and tasks.

Expand trigger terms to include natural recruitment phrasing users would say, e.g. 'candidates', 'job postings', 'applications', or 'recruitment data'.

Tighten the 'what' so it lists 3-4 specific actions rather than abstract verbs to lift specificity toward the top anchor.

Dimension	Reasoning	Score
Specificity	The phrase 'Manage data, records, and automate workflows' names the domain but the actions are generic and minimal rather than concrete, much like the anchor 'Processes PDF files'; it never mentions recruitment-specific actions (jobs, candidates, applications).	2 / 5
Completeness	It states a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Eploy data'); the when-clause is present so it is not capped at 3, though the what is vague enough to keep it from a 5.	4 / 5
Trigger Term Quality	'Eploy' and 'interact with Eploy data' are relevant natural terms, but coverage is thin with no synonyms or concrete entity keywords (jobs, candidates, recruitment), matching 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	The product proper noun 'Eploy' gives it a clear niche with low conflict risk, but the generic action vocabulary ('data', 'records', 'workflows') leaves minor overlap with other integration skills.	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/eploy/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.