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

wonderchat

Wonderchat integration. Manage data, records, and automate workflows. Use when the user wants to interact with Wonderchat 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/wonderchat/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.

The body is a well-structured, mostly executable CLI integration guide with a solid connection-state workflow and feedback loop, held back by a padded intro, unfilled command placeholders, and a broken 'Step 2' cross-reference.

Suggestions

Trim the opening paragraph that explains what Wonderchat is and the 'auth plumbing' aside; Claude does not need the platform's marketing description.

Fix the dangling 'skip to Step 2' reference by labeling the actual steps (e.g. add a '## Step 1: Connect' / '## Step 2: Discover actions' structure) or remove the cross-reference.

Add a short note on verifying action results (check the `output` field and any error/state) so destructive or batch action runs have an explicit validation checkpoint.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-driven and efficient, but the opening paragraph explaining what Wonderchat is and phrases like 'so you can focus on the integration logic rather than auth plumbing' are padding Claude does not need — not a 2 because most of the doc is tight, executable material.	3 / 5
Actionability	Provides concrete, copy-paste-ready commands (install, login, connection ensure, action run, request) with a flag table; minor gaps are placeholders like CONNECTION_ID and <actionId> that the user must fill, keeping it just below fully turn-key.	4 / 5
Workflow Clarity	The connection flow has a clear sequence with state-based checkpoints (READY / BUILDING / CLIENT_ACTION_REQUIRED) and a poll-again feedback loop, but the prose references 'Step 2' which is never labeled, leaving a minor navigation gap.	4 / 5
Progressive Disclosure	Single self-contained file with well-organized headers and no nested references; action discovery is delegated to the CLI rather than to bundled files, which is appropriate for a CLI-usage skill, though some reference-style material (the proxy flag table) is fully inlined.	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 is functional and third-person with both a what and a when clause, but its actions and trigger terms are generic and brand-anchored only, leaving it short of the concrete, comprehensive examples in the top anchors.

Suggestions

Replace generic verbs with concrete capabilities, e.g. 'Search and send messages, manage conversations and users, and build chat workflows in Wonderchat.'

Add natural trigger synonyms users say, e.g. 'Use when the user wants to send or read Wonderchat messages, manage chats, or work with Wonderchat contacts.'

Make the 'when' clause more specific by naming the concrete tasks rather than the catch-all 'interact with Wonderchat data'.

Dimension	Reasoning	Score
Specificity	Names the Wonderchat domain and a couple of actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete, so coverage is not comprehensive — not a 2 because multiple actions are named.	3 / 5
Completeness	It has both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Wonderchat data'); the 'when' is present but generic, so it does not reach the concrete-trigger specificity of a 5.	4 / 5
Trigger Term Quality	The trigger 'Use when the user wants to interact with Wonderchat data' anchors on the brand name, but it lacks synonyms or variations a user might naturally say beyond 'Wonderchat data'.	3 / 5
Distinctiveness Conflict Risk	The Wonderchat brand name gives it a clear, distinct niche with minimal conflict risk, though the generic action verbs ('manage data', 'automate workflows') leave minor overlap with adjacent 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/wonderchat/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.