Name: quantil
Rating: 48.8 (1 reviews)
Author: membranedev

quantil

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

Quality

53%

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

Quality

Content

68%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 concrete, runnable CLI commands and clear state-handling for connections, but an off-topic filler paragraph adds noise and the multi-step workflow lacks explicit validation checkpoints and consistent step numbering.

Suggestions

Remove the off-topic opening paragraph ('I don't have enough information to do that...'); it wastes context and contradicts the skill's purpose.

Add explicit validation checkpoints to the workflow, e.g. after `connection ensure` and `action run` verify the JSON `output`/`state` before proceeding, with a fix-and-retry loop on error states.

Reconcile the step numbering: the 'Step 2' references and '1b' subsection imply a numbered sequence that is not actually rendered, so either label steps 1-2-3 or drop the dangling references.

Dimension	Reasoning	Score
Conciseness	Most of the body is lean CLI commands and tables, but it includes a stray unhelpful paragraph ('I don't have enough information to do that...') and a few explanatory lines Claude could infer (e.g. 'This is the fastest way to get a connection'). Mostly efficient with some padding, matching the 3-anchor; not a 4 because of the off-topic filler paragraph.	3 / 5
Actionability	The body is dominated by concrete, copy-pasteable commands (npm install, membrane login, connection ensure, action run, request flags) plus a flag table and JSON examples. This matches the 5-anchor of fully executable, copy-paste-ready commands covering the common cases.	5 / 5
Workflow Clarity	There is a real sequence (install -> login -> connection ensure -> wait/poll -> search actions -> run) with branching on connection state, but the step numbering is inconsistent ('1b' with no 'Step 1'/'Step 2' anchors rendered) and proxy/action workflows lack validation or error-recovery checkpoints. This lands at the 3-anchor (sequence present, checkpoints missing).	3 / 5
Progressive Disclosure	Content is well-sectioned into overview, install, auth, connecting, searching, actions, proxy, and best practices, and no bundle files exist so all detail lives inline appropriately. It is below 5 because some bulkier reference-style content (the proxy flag table, popular-actions repetition) is inlined rather than split out, but structure and navigation are otherwise good.	4 / 5
	Total	15 / 20 Passed

Description

37%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 identifies the QUANTIL domain and includes a usable 'Use when' trigger, but the action verbs are generic and trigger-term coverage is thin. It reads more as a category label than a precise capability statement.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with 3-4 concrete operations such as 'search and update Cases, Contacts, and Tasks' so capabilities are specific.

Broaden trigger coverage with natural user phrasings and synonyms, e.g. 'Use when the user wants to query, create, or update QUANTIL records, Cases, or Tasks.'

Tighten the 'Use when' clause to list concrete trigger objects (Cases, Contacts, Tasks) to improve distinctiveness from generic data-management skills.

Dimension	Reasoning	Score
Specificity	The description names the domain (QUANTIL integration) and a few actions ('Manage data, records, and automate workflows') but the verbs are generic ('manage', 'automate') with no concrete operations. It is just below the 3-anchor ('1-2 concrete actions') since the actions read as categories rather than specific capabilities.	2 / 5
Completeness	It states a 'what' ('Manage data, records, and automate workflows') and includes an explicit 'Use when the user wants to interact with QUANTIL data' trigger. Per the rubric a missing 'Use when...' caps at 3, but here the clause is present yet only weakly specific, so it sits at 3 rather than 4 (the 'when' could be more concrete).	3 / 5
Trigger Term Quality	Only the single natural phrase 'interact with QUANTIL data' appears as a trigger; there are no synonyms, variants, or file/task keywords. This matches the 2-anchor of 'one or two generic keywords; missing the natural phrases users say' and is below 3 which expects several relevant keywords.	2 / 5
Distinctiveness Conflict Risk	'QUANTIL' is a distinct niche name, but the surrounding language ('manage data, records, automate workflows') is broad and could overlap with general CRM/data skills. It is somewhat specific but could still overlap, matching the 3-anchor rather than the more clearly-distinct 4-anchor.	3 / 5
	Total	10 / 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/quantil/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.