Name: quentn
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

quentn

Quentn integration. Manage Persons, Organizations, Deals, Activities, Notes, Files and more. Use when the user wants to interact with Quentn data.

Quality

66%

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/quentn/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.

The body is a well-structured, actionable guide to driving Quentn through the Membrane CLI, with concrete commands and a real connection-polling feedback loop. It is slightly over-prosey in places and inlines some reference-style material, but navigation and sequencing are clear.

Suggestions

Trim explanatory prose that Claude can infer (the platform description, "auth plumbing", and the token-burning rationale) to lift conciseness.

Have the "Popular actions" section actually list a few common Quentn actions (e.g. create/update Person, list Deals, send Email) instead of only redirecting to discovery.

Add a brief validation/check step after running actions (e.g. confirm the `output` field or check the returned state) so the workflow has an explicit success checkpoint.

Dimension	Reasoning	Score
Conciseness	The bulk is efficient commands and a flag table, but several prose passages over-explain (the marketing-automation platform description, "auth plumbing", and the "burn less tokens" rationale) and could be trimmed, matching the 3 anchor rather than the minor-trim 4.	3 / 5
Actionability	Copy-paste-ready commands cover install, login, connection ensure/get with --wait, action list/run, and the proxy flag table with clearly marked placeholders; the "Popular actions" section only redirects to discovery rather than listing actions, a minor gap keeping it below 5.	4 / 5
Workflow Clarity	The install→authenticate→connect→poll→search→run sequence is clear, and connection readiness has a genuine feedback loop (poll state → act on clientAction → re-poll); step numbering is loose ("Step 2" is referenced but not labeled) and there is no post-action validation, so it stays at 4.	4 / 5
Progressive Disclosure	With no bundle files present, the skill is a single well-organized file with clear section headers and no nested references; reference-style material (the proxy flag table and detailed clientAction state breakdown) is inlined rather than split out, a minor organization gap below 5.	4 / 5
	Total	15 / 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 clearly identifies the Quentn niche with an explicit Use-when clause and concrete entity types, but its action vocabulary is generic and trigger-term coverage is thin beyond the brand name. It is solid but leaves room for more specific verbs and natural-language triggers.

Suggestions

Replace the single generic verb "Manage" with several concrete actions (e.g. "Create and update Persons, search Organizations, track Deals, log Activities, attach Files").

Expand the Use-when clause with natural trigger phrases users would actually say (e.g. "Use when the user mentions Quentn, wants to manage Quentn contacts/campaigns, or automate Quentn marketing workflows").

Add common synonyms and the platform category ("marketing automation") to improve trigger-term coverage beyond the brand name.

Dimension	Reasoning	Score
Specificity	"Manage Persons, Organizations, Deals, Activities, Notes, Files and more" names the domain with concrete entity types, but relies on a single generic verb ("Manage") rather than listing several distinct actions, so it sits below the 4 anchor.	3 / 5
Completeness	A clear "what" (manage Quentn entities) pairs with an explicit "Use when the user wants to interact with Quentn data" clause, satisfying both; the "when" is present but slightly generic, keeping it below the concrete-trigger 5 anchor.	4 / 5
Trigger Term Quality	Triggers hinge on the brand name "Quentn" and "interact with Quentn data"; the entity types are not framed as natural trigger phrases and common synonyms (e.g. contacts, campaigns, marketing automation) are missing, so it matches the 3 anchor more than 4.	3 / 5
Distinctiveness Conflict Risk	"Quentn integration" tied to a single named app gives it a clear niche with distinct, brand-specific triggers and minimal overlap with 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/quentn/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.