Name: dingconnect
Rating: 60.8 (1 reviews)
Author: membranedev

dingconnect

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

Quality

71%

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

Quality

Content

75%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 is highly actionable with concrete, executable Membrane CLI commands and a solid connection-state feedback loop, but it opens with unnecessary marketing background and has a few broken step cross-references. Tightening the intro and labeling the steps would improve conciseness and workflow clarity.

Suggestions

Trim the opening marketing paragraph to a one-line description of what DingConnect is, removing audience background ('Marketing teams and businesses... use it') that Claude does not need.

Label the workflow steps consistently (e.g. 'Step 1: Connect', 'Step 2: Discover actions') so the dangling 'skip to Step 2' and '1b' references resolve to actual headers.

Add a brief validation note after running actions (e.g. check the `output` field for errors / empty results before proceeding) to close the post-run checkpoint gap.

Dimension	Reasoning	Score
Conciseness	Mostly efficient CLI command blocks, but the opening marketing paragraph ('helps businesses manage and automate their SMS marketing campaigns... Marketing teams... use it') and editorializing like 'so you can focus on the integration logic rather than auth plumbing' are unnecessary explanation; not 4 because the padding is more than minor.	3 / 5
Actionability	Fully executable, copy-paste-ready commands throughout (install, login, connection ensure, action list/run, request) plus a complete flag table, covering the common cases; placeholders like CONNECTION_ID are clearly meant to be substituted.	5 / 5
Workflow Clarity	Clear install→auth→connect→poll→search→run sequence with strong state-machine checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a re-poll feedback loop; not 5 because cross-references like 'Step 2' and '1b' are unlabeled and there is no post-run validation guidance.	4 / 5
Progressive Disclosure	Single, well-sectioned file with clear headers and no nested references; not 5 because the ~30-item entity list is inline overview content that could be split into a reference, representing a minor organization gap for a file over 50 lines.	4 / 5
	Total	16 / 20 Passed

Description

68%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 clearly identifies a distinct named-product niche and includes an explicit 'Use when' trigger, but its capability statement is generic ('manage data, records, automate workflows') rather than naming concrete actions. Strengthening the action verbs would lift specificity and completeness.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete actions specific to DingConnect, e.g. 'Send SMS campaigns, track delivery results, manage contacts and automations'.

Expand the 'when' clause with concrete trigger phrases users would say, e.g. 'Use when the user wants to send or schedule SMS campaigns, check delivery status, or manage DingConnect contacts and workflows.'

Add common synonyms/extensions of the trigger term (e.g. 'SMS marketing', 'bulk SMS') to broaden natural keyword coverage.

Dimension	Reasoning	Score
Specificity	Names the DingConnect domain but the actions ('Manage data, records, and automate workflows') are generic rather than concrete, matching the anchor where actions are minimal or generic; it does not reach 3 because no specific concrete action is named.	2 / 5
Completeness	Both 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with DingConnect data') are present, but the 'when' could be more specific, matching anchor 4 rather than 5.	4 / 5
Trigger Term Quality	The named product 'DingConnect' plus 'interact with DingConnect data' gives good keyword coverage of the natural term users would say, with only minor synonyms missing; not 5 because variations/extensions are limited.	4 / 5
Distinctiveness Conflict Risk	DingConnect is a specific named product giving a clear niche with distinct triggers and minimal conflict risk, matching the top anchor.	5 / 5
	Total	15 / 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/dingconnect/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.