Name: apploi
Rating: 55.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

apploi

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

Quality

63%

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

Quality

Content

60%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 is highly actionable with concrete Membrane CLI commands and a clear connection workflow including error-state branching. Its weaknesses are the padded generic entity glossary and the absence of any progressive disclosure — everything is inlined in one file with no references.

Suggestions

Move the ~50-item entity glossary out of SKILL.md into a references file (e.g. references/entities.md) and link to it, since most entries are generic HR/ATS terms Claude already knows.

De-duplicate the 'Searching for actions' and 'Popular actions' sections, which both demonstrate membrane action list --intent=QUERY, and fix the inconsistent step numbering ('1b', 'Step 2') so the workflow sequence is unambiguous.

Split the bulk CLI command/proxy reference into a separate reference file so SKILL.md stays a concise overview pointing to details one level deep.

Dimension	Reasoning	Score
Conciseness	The body is mostly tight CLI documentation, but the ~50-item entity glossary (Applicant, Job, ATS, CRM, HRIS, etc.) inlines generic HR/recruiting concepts Claude already knows and the 'Searching for actions'/'Popular actions' sections repeat the same action-list command, fitting 'mostly efficient but includes some unnecessary explanation or could be tightened'.	3 / 5
Actionability	It provides concrete, copy-pasteable commands (npm install, membrane login, connection ensure, action run, request) with real flags and a proxy options table, matching 'mostly executable guidance; concrete code or commands with minor gaps' such as unresolved CONNECTION_ID placeholders.	4 / 5
Workflow Clarity	The connection setup has a clear state-driven sequence with a polling feedback loop (BUILDING -> poll -> READY/CLIENT_ACTION_REQUIRED -> act -> poll again), matching 'clear sequence with most checkpoints present', though numbering is inconsistent ('#### 1b' references an undefined 'Step 2').	4 / 5
Progressive Disclosure	No bundle files exist and all content is inlined in a 200-line SKILL.md; the entity glossary and full command reference clearly belong in separate files but are inlined with no one-level-deep references signaled, matching 'minimal structure; content that clearly belongs in separate files is inlined'.	2 / 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 is concise, third-person, and clearly answers both what and when with a distinct Apploi-specific trigger. Its main weakness is generic action verbs and limited trigger-term variation, which keep specificity and trigger quality at mid-level.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Apploi operations, e.g. 'Create and track job postings, manage applicants, and trigger onboarding workflows'.

Expand the 'when' clause with concrete trigger phrases users would actually say, e.g. 'Use when the user wants to post jobs, review applicants, or automate Apploi hiring workflows'.

Dimension	Reasoning	Score
Specificity	Quotes 'Manage data, records, and automate workflows' name the Apploi domain plus two to three actions, but the actions are generic (manage data/records) rather than concrete Apploi-specific operations, matching the 'names domain and 1-2 concrete actions, not comprehensive' anchor.	3 / 5
Completeness	It states the 'what' ('Manage data, records, and automate workflows') and the 'when' ('Use when the user wants to interact with Apploi data'), but the trigger clause is fairly generic rather than enumerating concrete trigger phrases, so it is the 'both what and when; when could be more explicit' anchor rather than a 5.	4 / 5
Trigger Term Quality	The terms 'Apploi' and 'interact with Apploi data' are the natural keyword a user would say, but coverage is thin with no synonyms or variations, fitting 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	The 'Apploi' niche trigger is highly specific with minimal overlap risk against other skills, matching 'clear niche with distinct triggers; minimal conflict risk'.	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/apploi/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.