Name: checkmarket
Rating: 60 (1 reviews)
Author: membranedev

checkmarket

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

Quality

70%

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

Quality

Content

82%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 body is highly actionable with executable commands and a well-structured connection workflow including error-state feedback loops. It is concise and well-organized, with only minor verbosity and a missing verification step for action results.

Suggestions

Add a verify step after running actions (e.g. inspect the 'output' field and handle error states) to add a feedback loop for potentially destructive data operations.

Move the proxy flag reference table and detailed clientAction state descriptions into a separate REFERENCE.md to keep SKILL.md as a lean overview.

Trim minor filler phrases like 'so you can focus on the integration logic rather than auth plumbing' and de-duplicate the action-list command shown in both 'Searching for actions' and 'Popular actions'.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient command-driven guidance, with only minor over-explanation (e.g. 'so you can focus on the integration logic rather than auth plumbing' and a repeated action-list command in 'Popular actions') that could be trimmed.	4 / 5
Actionability	It provides copy-paste-ready, fully executable commands throughout — install, login, connection ensure, action list/run, and request — plus a concrete flags table, covering the common cases.	5 / 5
Workflow Clarity	The connection flow is clearly sequenced with explicit state checks (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and a poll-again feedback loop, but running actions lacks an explicit verify-result step for potentially destructive data operations.	4 / 5
Progressive Disclosure	Content is well-organized into clearly headed sections, but at ~140 lines with no bundle files some detail (the full proxy flag table, clientAction state reference) is inlined that could live in a one-level-deep reference.	4 / 5
	Total	17 / 20 Passed

Description

57%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 is third-person and covers both capability and an explicit trigger, but it relies on generic verbs ('manage', 'automate') instead of the concrete survey-domain actions that would sharpen it. Adding survey-specific trigger terms would notably improve it.

Suggestions

Replace generic verbs with concrete CheckMarket actions, e.g. 'Create and distribute surveys, manage respondents, send email/SMS invitations, and pull reports.'

Expand the 'Use when' clause with natural user phrases such as 'creating surveys', 'sending survey invitations', or 'pulling CheckMarket reports'.

Mention key entities (surveys, respondents, invitations, reports) so the description distinguishes itself from generic data-integration skills.

Dimension	Reasoning	Score
Specificity	The description names the CheckMarket domain but the actions ('Manage data, records, and automate workflows') are generic and not tied to concrete survey-specific operations like creating surveys or sending invitations.	2 / 5
Completeness	It states both what the skill does ('Manage data, records, and automate workflows') and when to use it ('Use when the user wants to interact with CheckMarket data'), though the 'when' clause could name more specific triggers.	4 / 5
Trigger Term Quality	It includes the brand keyword 'CheckMarket' and 'CheckMarket data' but misses the natural task terms a user would say ('survey', 'respondents', 'email/SMS invitations') that appear in the body.	3 / 5
Distinctiveness Conflict Risk	Naming a specific product ('CheckMarket integration') gives it a clear niche with low conflict risk, though the generic 'interact with data' phrasing leaves minor overlap with other data-integration skills.	4 / 5
	Total	13 / 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/checkmarket/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.