Name: dots
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

dots

Dots! integration. Manage Organizations, Users, Filters. Use when the user wants to interact with Dots! data.

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/dots/SKILL.md

Quality

Content

61%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 actionable CLI guidance with a well-sequenced connection state-machine, but it is held back by a misplaced puzzle-game intro and the absence of validation steps before destructive/batch actions. Organization into sections is good and no external references are needed.

Suggestions

Add a validation/verification step before running destructive or batch actions (e.g. retrieve-user to confirm identity before delete-user, or a dry-run/review step for create-payout-batch).

Remove or correct the "simple connection puzzle game" intro and the "Dot / Connections / Board" overview, which do not describe the Dots! payments API the skill actually wraps.

Fix the broken step references ("skip to Step 2" with no labeled Step 1/2) by numbering the connection flow consistently.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient command-driven content, but the intro paragraph ("Dots! is a simple connection puzzle game...Players connect adjacent dots") and the terse "Dot / Connections / Board" overview are unnecessary padding that does not advance the integration task.	3 / 5
Actionability	It provides concrete, copy-paste-ready commands throughout (install, login, connection ensure, action list/run, request) plus flag tables, with only minor gaps such as unresolved <actionId> and CONNECTION_ID placeholders.	4 / 5
Workflow Clarity	The connection flow has a clear state-machine with checkpoints (READY, BUILDING, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) and a poll-after-action feedback loop, but destructive and batch operations (Delete User, Create Payout Batch of 1-5000) are run with no validation/verification step, capping this dimension at 3.	3 / 5
Progressive Disclosure	There are no bundle files and the body is organized into clear, well-labeled sections (Install, Authentication, Connecting, Searching, Popular actions, Running, Proxy, Best practices); the inlined actions and flag tables are reasonable inline reference for this skill size.	4 / 5
	Total	14 / 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 "Use when" clause and names a distinct app, but it leans on the generic verb "Manage"/"interact" rather than concrete action terms and lacks natural user phrasings like payouts or transfers. It is solid but not comprehensive.

Suggestions

Replace the generic "Manage" with specific verbs users say, e.g. "Create and retrieve payouts, transfers, and users".

Expand the trigger clause with concrete phrases: "Use when the user wants to send payouts, manage Dots users, or create transfer flows."

Confirm the entity list (Organizations, Users, Filters) matches the actual API surface, since the body emphasizes payouts/transfers/users instead.

Dimension	Reasoning	Score
Specificity	"Manage Organizations, Users, Filters" names the Dots! domain and three concrete entities but relies on a single generic verb ("Manage") rather than listing multiple specific actions, matching the anchor that names a domain with 1-2 concrete actions.	3 / 5
Completeness	It states both the what ("Dots! integration. Manage Organizations, Users, Filters") and an explicit when ("Use when the user wants to interact with Dots! data"), but the when clause is generic and could be more specific with concrete trigger phrases.	4 / 5
Trigger Term Quality	"Use when the user wants to interact with Dots! data" supplies a usable trigger and the app name, but the verb "interact" is generic and natural action phrases users would say (e.g. "create payout", "send money", "list users") are missing.	3 / 5
Distinctiveness Conflict Risk	Naming the specific app "Dots!" with a dedicated trigger gives it a clear niche and low conflict risk, though "Manage Organizations, Users, Filters" is broad enough to cause minor overlap with other integration 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/dots/SKILL.md
Commit: f484c82

Reviewed: ~18 hours 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.