CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

apploi

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

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/apploi/SKILL.md
SKILL.md
Quality
Evals
Security

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 CLI workflow is genuinely actionable with concrete commands and good connection-state handling, but the body is dragged down by a large duplicated entity list that adds no executable value. Trimming that list and adding one or two real Apploi action examples would lift both conciseness and actionability.

Suggestions

Cut the 75-item entity list or deduplicate and compress it to the handful of Apploi entities actually used (Applicant, Application, Job, Form, Team, User), moving any full catalog to a references/ file.

Add 1-2 concrete example invocations with real Apploi actions (e.g. membrane action run <id> --input '{"jobId": ...}') instead of only QUERY/CONNECTION_ID placeholders.

Fix the dangling 'skip to Step 2' cross-reference by labeling the subsequent sections as numbered steps, and add a brief note on verifying the output field of action results.

DimensionReasoningScore

Conciseness

The 75-item entity list is pure padding containing literal duplicates ('ATS' / 'Applicant Tracking System', 'CRM' / 'Customer Relationship Management', 'HRIS' / 'Human Resources Information System'), plus filler lines like 'Use action names and parameters as needed.' — noticeably verbose with several padded sections.

2 / 5

Actionability

Concrete, copy-paste-ready commands throughout (install, login, connection ensure, action list/run, proxy flags table) with only minor gaps — no concrete Apploi action examples are shown, just QUERY/CONNECTION_ID placeholders.

4 / 5

Workflow Clarity

A clear install → login → connect → poll → search → run sequence with real checkpoints (--wait polling, CLIENT_ACTION_REQUIRED handling, poll-again-after-auth feedback loop); minor gaps include the dangling 'skip to Step 2' reference to an unlabeled section and no output-verification guidance.

4 / 5

Progressive Disclosure

There are no external reference files at all, and the ~55-line entity list and proxy flag table are inline content that should be split into a reference file or cut — some structure, but content that should be separate is inline.

3 / 5

Total

13

/

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 a clear explicit trigger and names a distinct niche product, but the capability statement is generic boilerplate that would fit almost any SaaS integration. Adding Apploi-concrete actions (jobs, applicants, onboarding) and natural synonyms would materially strengthen it.

Suggestions

Replace the generic 'Manage data, records, and automate workflows' with Apploi-specific actions, e.g. 'Manage Apploi jobs, applicants, and onboarding; automate hiring workflows.'

Expand the 'Use when' clause with natural trigger phrases users would actually say: 'Use when the user mentions Apploi, healthcare hiring, job applicants, or candidate onboarding.'

Include synonyms and concrete entity nouns (jobs, applicants, candidates, interviews) so the skill triggers on the vocabulary users naturally use.

DimensionReasoningScore

Specificity

The description names the domain ('Apploi integration') but the actions — 'Manage data, records, and automate workflows' — are generic boilerplate applicable to any SaaS tool, with no concrete Apploi-specific actions like jobs, applicants, or hiring.

2 / 5

Completeness

Both 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Apploi data') are present, but the 'when' is narrow — 'interact with Apploi data' undersells the stated workflow automation capability.

4 / 5

Trigger Term Quality

'Apploi' and 'Apploi data' are the natural terms a user would say, but the description misses common synonyms and variations such as hiring, applicants, candidates, healthcare staffing, or jobs.

3 / 5

Distinctiveness Conflict Risk

'Apploi' is a niche product name with distinct triggers, so conflict risk is low; the generic 'manage data, records' clause creates only minor overlap risk with other data-integration skills.

4 / 5

Total

13

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

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

Reviewed

Table of Contents

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.