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

liveperson

Liveperson integration. Manage data, records, and automate workflows. Use when the user wants to interact with Liveperson 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/liveperson/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 body is highly actionable, with copy-paste commands and a well-sequenced connection workflow that includes explicit state-based checkpoints. Its main weaknesses are mild verbosity in the intro/marketing prose and a broken 'Step 2' reference that slightly muddies the workflow.

Suggestions

Trim the opening overview paragraph and phrases like 'so you can focus on the integration logic rather than auth plumbing' to improve token efficiency.

Fix the dangling 'skip to Step 2' reference by labeling the actual next step (e.g. rename 'Searching for actions' to 'Step 2: Search for actions').

Add a brief verification/error-handling note for `membrane action run` (e.g. check the `output` field and handle non-zero exit or error states) to complete the workflow's feedback loop.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-driven and efficient, but includes unnecessary explanation Claude does not need, such as the marketing-style opener ('Liveperson is a platform that enables businesses to communicate with customers via messaging...') and 'so you can focus on the integration logic rather than auth plumbing', fitting 'mostly efficient but includes some unnecessary explanation'; it is not 4 because several sentences could be trimmed without losing clarity.	3 / 5
Actionability	It provides copy-paste-ready commands for every common case — install, login (incl. headless completion), connection ensure, polling, action list/run, and proxy requests — plus a flags table, matching 'fully executable; copy-paste ready code or commands; specific examples cover the common cases'.	5 / 5
Workflow Clarity	The connect-to-ready flow is clearly sequenced with explicit state checkpoints (READY, BUILDING, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) and a poll-after-action feedback loop, matching 'clear sequence with most checkpoints present'; it is not 5 because of a broken 'skip to Step 2' reference to a non-existent step and the absence of verification/error-handling guidance for action execution.	4 / 5
Progressive Disclosure	Content is well organized into clearly headed sections (Overview, Working with Liveperson, Install, Authentication, Connecting, Searching, Actions, Proxy, Best practices) with no nested references, fitting 'good structure; most content appropriately placed'; it is not 5 because reference-like material (the full proxy flags table, detailed clientAction state handling) is inlined rather than split into separate reference files, though no bundle files are present.	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 is functional and includes an explicit 'Use when' trigger tied to a named product, but its capability language is generic ('manage data, records, and automate workflows') rather than concrete Liveperson actions. Strengthening specificity and trigger phrasing would raise the score.

Suggestions

Replace generic verbs with concrete Liveperson operations, e.g. 'Manage Liveperson conversations, messages, agents, skills, and queues' to lift specificity.

Add natural trigger variations and synonyms, e.g. 'Use when the user wants to send or read Liveperson messages, manage agents or queues, or automate Liveperson messaging workflows.'

Name the specific entities available (Conversation, Message, Agent, Skill, Queue) in the description so the 'what' is concrete and distinctive.

Dimension	Reasoning	Score
Specificity	The description names the Liveperson domain but the actions ('Manage data, records, and automate workflows') are generic rather than concrete Liveperson-specific operations, matching the 'names the domain but actions are minimal or generic' anchor; it does not reach 3 because no genuinely concrete, platform-specific actions are listed.	2 / 5
Completeness	Both a 'what' ('Liveperson integration. Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Liveperson data') are present, matching the 'has both what and when; when could be more explicit or specific' anchor; it is not 3 because the trigger guidance is explicit, and not 5 because the 'when' is generic rather than citing concrete trigger phrases.	4 / 5
Trigger Term Quality	It includes the natural product term 'Liveperson' and the phrase 'interact with Liveperson data', but offers only a single phrasing with no synonyms or variations, fitting the 'some relevant keywords but missing common variations' anchor rather than the broader coverage of 4.	3 / 5
Distinctiveness Conflict Risk	Tying activation to the named platform 'Liveperson' gives it a clear niche with minimal conflict risk, but the generic 'manage data, records' framing leaves minor overlap with other CRM/messaging skills, fitting 'mostly distinct; minor overlap risk' rather than the fully distinct anchor 5.	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/liveperson/SKILL.md
Commit: f484c82

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