Name: chatsonic
Rating: 64.8 (1 reviews)
Author: membranedev

chatsonic

Chatsonic integration. Manage Users, Chats, Images, Workspaces, Prompts. Use when the user wants to interact with Chatsonic data.

Quality

78%

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/chatsonic/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 body is highly actionable with executable Membrane CLI commands and a clear, state-aware connection workflow. Conciseness and workflow clarity lose a point each to minor padding and loose step numbering, and progressive disclosure is solid but operates as a monolithic single file.

Suggestions

Trim the introductory paragraph about Chatsonic's audience ("used by marketers, writers, and researchers") since it is context Claude does not need to execute the skill.

Replace the dangling "skip to Step 2" and "1b" references with an explicitly numbered Step 1 / Step 2 / Step 3 sequence so the workflow checkpoints are unambiguous.

Fill the empty Description column in the "Popular actions" table so the action list is self-explanatory without a separate search.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with copy-paste commands, but the opening paragraph about who uses Chatsonic ("marketers, writers, and researchers") and the restated best-practices section add minor over-explanation Claude does not need, fitting anchor 4 over 5.	4 / 5
Actionability	It provides fully executable, copy-paste-ready `membrane` commands (login, connection ensure, action list/run, request) with flag tables covering common cases, matching anchor 5.	5 / 5
Workflow Clarity	There is a clear install→authenticate→connect→poll→run sequence with state feedback loops (READY/BUILDING/CLIENT_ACTION_REQUIRED and re-polling), but the dangling "skip to Step 2" and "1b" references are not backed by a clearly numbered step structure, a minor gap keeping it at anchor 4 rather than 5.	4 / 5
Progressive Disclosure	The content is well-organized into labeled sections in a single file with no bundle files present, so it is not eligible for the under-50-line exception; structure is good with minor organization gaps (the loose step numbering), fitting anchor 4 over 5.	4 / 5
	Total	17 / 20 Passed

Description

73%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 the Chatsonic niche and includes both a capability list and a use-when trigger, but the action verb is the generic "Manage" and the trigger clause is not concrete. Tightening verbs and adding specific trigger phrases would lift specificity and completeness.

Suggestions

Replace the generic verb "Manage" with concrete actions per object (e.g., "List, create, and delete Users; send and retrieve Chats; generate Images").

Expand the "Use when" clause with concrete trigger phrases (e.g., "Use when the user wants to send Chatsonic messages, generate images, or manage Chatsonic workspaces").

Add file-format or synonym terms where relevant (e.g., "Chatsonic chats, generated images") to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	It names the domain objects ("Users, Chats, Images, Workspaces, Prompts") but the only verb is the generic "Manage", so the concrete actions are not enumerated; this fits anchor 3 (domain + 1-2 concrete actions) better than 4, which expects several specific actions.	3 / 5
Completeness	Both what ("Manage Users, Chats, Images, Workspaces, Prompts") and when ("Use when the user wants to interact with Chatsonic data") are present, but the when clause is generic rather than listing concrete trigger phrases, fitting anchor 4 over 5.	4 / 5
Trigger Term Quality	The trigger "Use when the user wants to interact with Chatsonic data" is natural and accompanied by domain keywords (Chats, Images, Workspaces, Prompts); good coverage with a few natural synonyms missing, matching anchor 4 rather than 5's comprehensive synonym list.	4 / 5
Distinctiveness Conflict Risk	The named app "Chatsonic integration" establishes a clear niche with distinct triggers and minimal overlap with other skills, matching anchor 5.	5 / 5
	Total	16 / 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/chatsonic/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.