Name: persistiq
Rating: 52.8 (1 reviews)
Author: membranedev

persistiq

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

Quality

59%

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

Quality

Content

61%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 a well-structured, actionable guide built around concrete Membrane CLI commands and a solid connection-state feedback loop, but it carries some unnecessary explanatory padding and lacks validation checkpoints around destructive data operations. Tightening the prose and adding verify-before-mutate guidance would address the lowest dimensions.

Suggestions

Add a validation/verification checkpoint before destructive proxy requests or action runs, e.g. "For POST/PUT/DELETE, run a read-only GET first to confirm the target, then re-fetch to verify the change" — this removes the workflow_clarity cap.

Trim the opening "PersistIQ is a sales engagement platform..." paragraph and the "so you can focus on integration logic rather than auth plumbing" clause, and de-duplicate the action-discovery command between "Searching for actions" and "Popular actions".

Fix the broken "skip to Step 2" reference by labeling the post-connection steps explicitly (Step 2: Search for actions, Step 3: Run the action) so the sequence is unambiguous, and populate "Popular actions" with actual named PersistIQ actions.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient executable commands, but it opens by explaining what PersistIQ is ("PersistIQ is a sales engagement platform that helps sales teams..."), includes fluff like "so you can focus on the integration logic rather than auth plumbing," and repeats the action-discovery command in a redundant "Popular actions" section.	3 / 5
Actionability	It provides copy-paste-ready commands throughout (login, connection ensure, action run with JSON input, a thorough proxy flags table), but "Popular actions" never lists actual action names and there is no end-to-end worked example with real values, leaving minor gaps below the level-5 anchor.	4 / 5
Workflow Clarity	The connection flow has a clear sequence and a real feedback loop (poll state, handle CLIENT_ACTION_REQUIRED, re-poll), but data-mutation operations (run action, proxy DELETE/PUT) have no validation/verification step and "skip to Step 2" references an unlabeled step; missing validation for destructive/batch operations caps this at 3.	3 / 5
Progressive Disclosure	With no bundle files present, the single-file body is well-organized into a clear section hierarchy (Overview, Working with PersistIQ, Authentication, Connecting, Searching, Running, Proxy, Best practices) with no nested references and manageable inline content, matching 'good structure; most content appropriately placed'.	4 / 5
	Total	14 / 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 correctly pairs a what-statement with an explicit "Use when..." trigger and leverages a distinctive brand name, but its capability list is generic boilerplate that doesn't surface PersistIQ's actual features. Stronger, more concrete action verbs and natural synonyms would lift the weaker dimensions.

Suggestions

Replace generic verbs with concrete PersistIQ capabilities, e.g. "Manage contacts and contact lists, build campaigns and sequences, and track user activity" to raise specificity.

Add natural synonyms users actually say — "sales engagement," "outreach," "campaigns," "leads" — alongside "PersistIQ" to improve trigger term coverage.

Make the "when" clause more concrete, e.g. "Use when the user wants to manage PersistIQ campaigns, contacts, or sequences," so the trigger is unambiguous.

Dimension	Reasoning	Score
Specificity	The description names the domain ("PersistIQ integration") but its actions are generic boilerplate ("Manage data, records, and automate workflows") rather than concrete PersistIQ capabilities like campaigns, sequences, or contacts, matching the 'names the domain but actions are minimal or generic' anchor.	2 / 5
Completeness	Both "what" ("Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with PersistIQ data") are present, but the trigger phrasing is generic rather than concrete, so it sits below the level-5 anchor.	4 / 5
Trigger Term Quality	It includes the strong specific keyword "PersistIQ" (repeated as "PersistIQ data") but offers no synonyms or natural variations a user might say (sales engagement, outreach, campaigns, leads), fitting 'some relevant keywords but missing common variations or synonyms'.	3 / 5
Distinctiveness Conflict Risk	"PersistIQ" is a distinct brand niche unlikely to trigger the wrong skill, but the generic action verbs ("Manage data, records") create minor overlap risk with other data-management skills, matching 'mostly distinct; minor overlap risk'.	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/persistiq/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.