Name: qntrl
Rating: 67.2 (1 reviews)
Author: membranedev

qntrl

Qntrl integration. Manage Organizations, Pipelines, Users, Goals, Filters. Use when the user wants to interact with Qntrl data.

Quality

81%

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

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 concrete, executable CLI commands and a clear connection-state workflow with validation. The main weakness is conciseness, where several explanatory asides and a product overview pad the token budget without adding guidance Claude needs.

Suggestions

Trim explanatory asides like "so you can focus on the integration logic rather than auth plumbing" and "This is the fastest way to get a connection"; keep only the command and its observable behavior.

Remove or shorten the opening product description of what Qntrl is (lines 17-19); assume Claude's competence and link the official docs instead.

Replace the loose "Step 2" references with an explicitly numbered/labeled step sequence so the connect → search → run flow is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with copy-paste commands, but includes unnecessary commentary Claude does not need, e.g. "so you can focus on the integration logic rather than auth plumbing", "This is the fastest way to get a connection", and a generic product description of what Qntrl is.	3 / 5
Actionability	It provides fully executable, copy-paste-ready commands covering the common cases (install, login, connection ensure, action list/run, request proxy) plus a concrete flag table, matching the top anchor.	5 / 5
Workflow Clarity	The install → auth → connect → search → run sequence is clear with validation checkpoints (polling connection state, the --wait flag, retrying after clientAction), but "Step 2" is referenced without a correspondingly labeled header, leaving a minor sequencing gap.	4 / 5
Progressive Disclosure	Content is organized under clear, well-labeled section headers in a single self-contained file with no bundle references; the structure is good but the "Qntrl Overview" entity bullet list and the long clientAction explanation add inline bulk that a reference split could offload.	4 / 5
	Total	16 / 20 Passed

Description

87%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 the skill does and when to use it, anchored to a distinct named product. It is slightly held back from perfection only by the generic "Manage" verb and limited trigger-term variation.

Dimension	Reasoning	Score
Specificity	"Manage Organizations, Pipelines, Users, Goals, Filters" lists several concrete capabilities, though the single verb "Manage" is generic and coverage is not exhaustive, so it sits below the comprehensive 5 anchor.	4 / 5
Completeness	It explicitly states what ("Manage Organizations, Pipelines, Users, Goals, Filters") and when ("Use when the user wants to interact with Qntrl data") with a concrete trigger phrase, matching the top anchor.	5 / 5
Trigger Term Quality	"Use when the user wants to interact with Qntrl data" surfaces the natural product-name trigger with a few associated entity terms; good coverage but missing variations such as "workflow management" or "automation" that users might also say.	4 / 5
Distinctiveness Conflict Risk	"Qntrl integration" targets a single named SaaS product niche with distinct triggers, making conflict with other skills minimal.	5 / 5
	Total	18 / 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/qntrl/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.