Name: disqo
Rating: 56.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

disqo

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

Quality

65%

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/disqo/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 skill delivers concrete, runnable Membrane CLI guidance with a strong connection-setup workflow, but destructive/batch operations (proxy requests, action runs) lack validation checkpoints, and content is monolithic with no reference split. Adding verification steps and offloading detail to reference files would improve it.

Suggestions

Add an explicit validation/verification checkpoint after batch action runs and proxy requests (e.g. inspect output.error, confirm expected record count) to satisfy the destructive/batch workflow-clarity bar.

Move the proxy flag table and action-list details into a separate reference file linked from SKILL.md to achieve a cleaner one-level-deep progressive disclosure structure.

Provide one fully-resolved end-to-end example that binds CONNECTION_ID, actionId, and a real QUERY so the guidance is copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The body is dominated by lean, executable CLI commands and a flag table, though the opening "Disqo is a customer experience..." overview and the "Use action names and parameters as needed." line are mild over-explanation Claude largely knows.	4 / 5
Actionability	Concrete commands cover install, login, connection ensure/get, action list/run, and proxy requests with flags and JSON examples; minor gaps remain in placeholders like CONNECTION_ID, actionId, and "QUERY" that are never bound to a concrete end-to-end example.	4 / 5
Workflow Clarity	The connection setup is well sequenced with polling and state feedback loops (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but destructive/batch action runs and proxy requests lack validation checkpoints, capping workflow clarity at 3 per the rubric guideline.	3 / 5
Progressive Disclosure	A single well-sectioned SKILL.md with clear headers and one external docs link, no nested references; bulk content is inline which is reasonable for a CLI skill but keeps it short of an ideal one-level-deep reference split.	4 / 5
	Total	15 / 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 correctly pairs a what-and-when structure with an explicit trigger clause, but the capabilities are generic ("manage data, records") and the trigger terms are thin. Tightening the verbs and adding concrete Disqo domain terms would lift it.

Suggestions

Replace generic verbs with concrete Disqo actions, e.g. "List surveys and members, fetch responses, and automate CX workflows".

Expand the trigger clause with natural user phrases, e.g. "Use when the user wants to pull survey responses, manage Disqo members, or analyze CX data."

Reference file formats or domain objects (surveys, responses, members) to improve trigger-term coverage and distinctiveness.

Dimension	Reasoning	Score
Specificity	Names the domain (Disqo) plus a few actions ("Manage data, records, and automate workflows"), but the verbs ("manage") and nouns ("data", "records") are generic rather than concrete capabilities.	3 / 5
Completeness	Both a "what" (manage data/records, automate workflows) and an explicit "Use when the user wants to interact with Disqo data" trigger are present, though the "when" is generic rather than tied to concrete trigger phrases.	4 / 5
Trigger Term Quality	Only the brand name "Disqo" and the word "data" serve as keywords; common natural task phrases a user would say (surveys, responses, CX, members) are absent.	3 / 5
Distinctiveness Conflict Risk	The "Disqo integration" brand anchor carves a clear niche with low conflict risk, though the generic data-management verbs create minor overlap potential with other data skills.	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/disqo/SKILL.md
Commit: f484c82

Reviewed: 4 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.