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

repliq

RepliQ integration. Manage Leads, Persons, Organizations, Deals, Projects, Activities and more. Use when the user wants to interact with RepliQ 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

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/repliq/SKILL.md

Quality

Content

67%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.

A well-structured, highly actionable CLI integration guide with a strong connection-state workflow and feedback loop. It loses points mainly on a padded marketing intro, an unexplained overview list, generic action placeholders, and a dangling "Step 2" reference.

Suggestions

Cut the marketing-style intro paragraph and the unexplained "RepliQ Overview" list (Replicate/Source/Destination/Schedule), or replace them with concise operational context Claude cannot infer.

Fix the dangling "skip to Step 2" reference by labeling the workflow steps explicitly (e.g., Step 1: Connect, Step 2: Discover and run actions).

Add a concrete worked example for `action run` with a real actionId and input, and include a verification step before destructive proxy calls (POST/PUT/DELETE).

Dimension	Reasoning	Score
Conciseness	Mostly efficient operational detail, but the opening marketing paragraph ("sales engagement platform... close more deals"), the unexplained generic "RepliQ Overview" list (Replicate/Source/Destination/Schedule), and a repeated `action list --intent` command between sections are unnecessary padding that could be tightened.	3 / 5
Actionability	Concrete, copy-paste-ready commands cover the main flows (install, login, connection ensure, action list/run, request) with a full proxy-options table; minor gaps remain in the form of generic placeholders like `<actionId>` and `<id>` with no concrete example action.	4 / 5
Workflow Clarity	The connection flow is a clear sequence with a genuine state-machine checkpoint and a feedback loop (poll `--wait`, handle `CLIENT_ACTION_REQUIRED`, re-poll), though the dangling "skip to Step 2" reference and the absence of verification after running actions or destructive proxy calls are minor validation gaps.	4 / 5
Progressive Disclosure	No bundle files exist and the body is a single cohesive CLI guide organized under clear section headers; structure is good, but at ~140 lines all content is inline with no references, and the out-of-place "RepliQ Overview" list is a minor organization gap.	4 / 5
	Total	15 / 20 Passed

Description

73%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.

A solid description that pairs a concrete "what" with an explicit "Use when" trigger and is clearly anchored to a distinct product. Its main weakness is the single generic action verb "Manage" where more specific actions would improve specificity.

Suggestions

Replace or expand the generic verb "Manage" with specific concrete actions (e.g., "create, update, search, and sync Leads, Deals, and Organizations").

Broaden the trigger clause beyond "interact with RepliQ data" to include natural user phrasings like "when the user wants to search, create, or update RepliQ records".

Dimension	Reasoning	Score
Specificity	The description names the domain (RepliQ) and lists six concrete entity types ("Leads, Persons, Organizations, Deals, Projects, Activities"), but the only action verb is the generic "Manage", so actions are not comprehensive or distinct.	3 / 5
Completeness	It explicitly answers both "what" ("Manage Leads, Persons, Organizations, Deals, Projects, Activities and more") and "when" ("Use when the user wants to interact with RepliQ data"), but the single trigger phrase is somewhat generic and could be more specific.	4 / 5
Trigger Term Quality	Good keyword coverage via the product name "RepliQ" plus natural entity terms users would say (Leads, Deals, Persons, Organizations) and the trigger "interact with RepliQ data"; a few common synonyms or phrasings are missing.	4 / 5
Distinctiveness Conflict Risk	Tying the skill explicitly to the named product "RepliQ" with a RepliQ-specific trigger gives it a clear niche and minimal conflict risk with other skills.	5 / 5
	Total	16 / 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/repliq/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.