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

Blog Docs Log in Get started

q2

Q2 integration. Manage data, records, and automate workflows. Use when the user wants to interact with Q2 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/q2/SKILL.md

Quality

Content

56%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 delivers strong, executable CLI commands with a clear connection workflow and state-based feedback loop, but it is weighed down by a large padded entity list that should be externalized. Actionability and workflow clarity are its strengths; conciseness and progressive disclosure are its weaknesses.

Suggestions

Move the entity/template enumeration into a references file (e.g., references/entities.md) and replace the inline list with a one-line pointer.

Drop the redundant "X Template" duplicate list or generate it dynamically from `membrane action list` rather than hard-coding it.

Add a brief verification step after running actions or destructive proxy requests (e.g., check the `output`/error field before proceeding).

Dimension	Reasoning	Score
Conciseness	The ~100-item entity list ("Case", "User", ... plus a duplicated "X Template" entry for every entity) is a padded wall of reference data with the placeholder instruction "Use action names and parameters as needed", matching the noticeably-verbose/padded anchor rather than the mostly-efficient 3.	2 / 5
Actionability	Commands like `npm install -g @membranehq/cli@latest`, `membrane connection ensure "https://www.q2.com/" --json`, and `membrane action run <actionId> --connectionId=CONNECTION_ID --json` are concrete and executable with a thorough proxy-options table, but placeholders (CONNECTION_ID, QUERY, actionId) and the lack of a fully worked example leave minor gaps versus copy-paste-ready 5.	4 / 5
Workflow Clarity	The install → authenticate → connect → search → run sequence is clear, and the connection section has an explicit state-machine feedback loop (READY / BUILDING / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR with re-polling), but there is no verification checkpoint after running actions or destructive proxy calls, keeping it at 4 rather than 5.	4 / 5
Progressive Disclosure	Section headers are well organized and no bundle files exist, but the large inline entity/template enumeration is reference data that clearly belongs in a separate file, fitting the structure-present-but-content-should-be-separate anchor rather than a 4.	3 / 5
	Total	13 / 20 Passed

Description

62%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 answers both what and when with an explicit trigger and a distinct product niche, but its capability verbs are generic and trigger-term coverage lacks synonyms. It is solid but not exemplary.

Suggestions

Replace generic verbs with concrete Q2 capabilities (e.g., "Create and update cases, manage accounts and contacts, automate Q2 workflows").

Broaden trigger terms with natural variations a user might say (e.g., "Q2 records", "Q2 cases", "banking workflows").

Make the "when" clause more specific about the data interactions covered (read vs. write vs. automate).

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Q2 domain and a few actions, but the verbs ("manage", "automate") are generic categories rather than concrete capabilities, matching the 1-2-actions-not-comprehensive anchor rather than the comprehensive 5.	3 / 5
Completeness	It states both a "what" ("Manage data, records, and automate workflows") and an explicit "Use when..." trigger, so it clears the 3-cap for missing triggers, but the "when" is somewhat generic and could be more specific, landing at 4 rather than 5.	4 / 5
Trigger Term Quality	The trigger "Use when the user wants to interact with Q2 data" surfaces the natural term "Q2"/"Q2 data", but coverage is thin with no synonyms or common variations, fitting the some-keywords-missing-variations anchor and not the comprehensive 5.	3 / 5
Distinctiveness Conflict Risk	Q2 is a named product giving it a clear niche with distinct triggers, but the generic action phrasing ("data, records, workflows") creates minor overlap risk with general CRM/data skills, so 4 rather than the minimal-conflict 5.	4 / 5
	Total	14 / 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/q2/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.