Name: pliance
Rating: 60 (1 reviews)
Author: membranedev

pliance

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

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/pliance/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 executable Membrane CLI commands and a solid connection-state workflow, but its conciseness is dragged down by a large generic term list and a dangling Step 2 reference.

Suggestions

Remove or drastically trim the 'Pliance Overview' bullet list of ~60 generic terms, which reads as padding and adds no actionable guidance.

Fix the dangling 'skip to Step 2' reference by either labeling the next section 'Step 2' or rewording to 'skip to Searching for actions'.

Add a validation/check step before destructive proxy requests (e.g. confirm the HTTP method and target with the user before DELETE/PUT).

Dimension	Reasoning	Score
Conciseness	The operational sections (install, auth, connect, search, proxy) are efficient and executable, but the ~50-line 'Pliance Overview' bullet list of generic nouns/verbs (Create, Read, Search, Filter, Tag, Log) is padded content that adds no actionable value and could be trimmed.	3 / 5
Actionability	Provides copy-paste-ready commands throughout (npm install, membrane login, connection ensure, action list/run, request) plus a complete proxy flag table, covering the common integration cases concretely.	5 / 5
Workflow Clarity	A clear connect-to-run sequence with an explicit state machine (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and polling feedback loops, but the dangling 'skip to Step 2' reference (no Step 2 exists) and absence of validation before destructive proxy calls are minor gaps.	4 / 5
Progressive Disclosure	Well-organized into logical sections with clear headers and no nested references; the only organizational weakness is the inline 'Pliance Overview' term dump that would be better removed or moved to a reference file.	4 / 5
	Total	16 / 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 cleanly answers both what and when and is highly distinct thanks to the named product, but its action list and trigger terms are generic rather than reflecting Pliance's actual compliance/AML domain.

Suggestions

Replace generic actions ('manage data, records, automate workflows') with concrete Pliance capabilities such as 'run KYC/AML screening, manage compliance cases, and automate screening workflows'.

Add domain trigger terms users would naturally say, e.g. 'compliance screening', 'KYC checks', 'AML monitoring', or 'sanctions screening'.

Tighten the 'Use when...' clause to reference compliance/AML scenarios rather than the vague 'interact with Pliance data'.

Dimension	Reasoning	Score
Specificity	Names the Pliance domain and a couple of actions ('Manage data, records, and automate workflows'), but those actions are generic rather than concrete compliance-specific operations, so coverage is not comprehensive.	3 / 5
Completeness	Explicitly states both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Pliance data'), though the 'when' trigger is somewhat generic and could be more specific.	4 / 5
Trigger Term Quality	Includes the core product keyword 'Pliance' plus 'data' and 'records', but lacks common variations or compliance-domain synonyms (AML, KYC, screening) a user might actually say.	3 / 5
Distinctiveness Conflict Risk	The 'Pliance' product name and 'interact with Pliance data' trigger define a clear niche with minimal overlap risk against other skills.	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/pliance/SKILL.md
Commit: f484c82

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