Name: checkvist
Rating: 61.6 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

checkvist

Checkvist integration. Manage Lists, Tags, Users, Teams. Use when the user wants to interact with Checkvist data.

Quality

73%

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

A mostly executable and well-structured CLI guide with a real polling-based connection workflow and concrete command examples. Tightening redundant/padded prose, fixing the inconsistent step numbering, and adding one fully-worked Checkvist action example would lift the weaker dimensions.

Suggestions

Remove the redundant `membrane action list` restatement in "Popular actions" and trim editorial asides to improve token efficiency.

Fix the step numbering (label Step 1a / Step 2 or convert to a single coherent numbered sequence) so the connection flow is unambiguous.

Add one concrete end-to-end example, e.g. running a real Checkvist action such as listing tasks with actual parameter values, to make the guidance fully copy-paste ready.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands, but includes editorial asides ("so you can focus on the integration logic rather than auth plumbing"), a product-orientation paragraph on who uses Checkvist, and a redundant restatement of the `membrane action list` command in the "Popular actions" section.	3 / 5
Actionability	Provides concrete, copy-paste-ready commands for login, connection setup, and proxy requests with a complete flag table, but relies on placeholders (CONNECTION_ID, QUERY, actionId) with no fully-worked end-to-end Checkvist action example showing real parameter values.	4 / 5
Workflow Clarity	The connection flow is sequenced with a polling feedback loop and explicit state branches (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR), but step numbering is inconsistent ("skip to Step 2", "#### 1b." with no labeled Step 1a or Step 2), a minor validation-gap that keeps it below 5.	4 / 5
Progressive Disclosure	Well-organized into clear sections with headers and no nested references (no bundle files present), and the CLI guide is self-contained; however the inlined proxy-options table and action-discovery content could optionally live in a reference file, a minor organization gap versus a 5.	4 / 5
	Total	15 / 20 Passed

Description

78%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.

A solid, third-person description that states both capabilities and a clear use-when trigger, anchored to a distinct product niche. It could rise to the top anchor by replacing the generic "Manage" verb with more concrete actions and adding common user phrasings.

Suggestions

Replace the generic verb "Manage" with specific operations per entity (e.g., "Create and update Lists, add tasks, assign Tags, manage Users and Teams").

Broaden the trigger clause with natural user phrasings such as "outlines", "checklists", or "task lists" to improve trigger-term coverage.

Consider naming the OPML/outliner nature in the description to sharpen distinctiveness against generic task-manager skills.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete managed entities ("Manage Lists, Tags, Users, Teams") rather than vague actions, though "Manage" is a generic verb covering the actual operations; minor coverage gaps keep it just below a 5.	4 / 5
Completeness	Explicitly answers both "what" ("Manage Lists, Tags, Users, Teams") and "when" ("Use when the user wants to interact with Checkvist data") in third person; the "when" clause is present but could name more specific trigger scenarios, so it is not a 5.	4 / 5
Trigger Term Quality	Good keyword coverage with the product name "Checkvist" plus entity terms ("Lists, Tags, Users, Teams") and a natural "Use when the user wants to interact with Checkvist data" trigger, but missing common synonyms or task-level phrasings users might say.	4 / 5
Distinctiveness Conflict Risk	Tied to a specific named product ("Checkvist") with distinct entity triggers, giving it a clear niche with minimal risk of triggering the wrong skill.	5 / 5
	Total	17 / 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/checkvist/SKILL.md
Commit: f484c82

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