Name: cusdis
Rating: 60 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

cusdis

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

Quality

70%

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/cusdis/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 a highly actionable CLI guide with executable commands, a clear connection-state workflow including validation feedback loops, and clean sectioning. It is held back only by minor over-explanation, a dangling "Step 2" reference, and light redundancy between the action-search sections.

Suggestions

Trim introductory over-explanation such as the "Cusdis is a privacy-focused comment system..." sentence and the "so you can focus on the integration logic" aside, which restate things Claude can infer.

Resolve the dangling "Step 2" reference: either number the sections explicitly (1a install/auth, 1b wait, 2 search/run) or replace the cross-reference with a concrete anchor.

Merge or clearly differentiate the "Searching for actions" and "Popular actions" sections, which both demonstrate `action list --intent`, to remove redundancy.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean executable commands with genuinely useful state-handling detail, but a few lines over-explain (e.g. the opening "Cusdis is a privacy-focused comment system..." and "so you can focus on the integration logic rather than auth plumbing").	4 / 5
Actionability	Copy-paste-ready commands cover the common cases end to end (install, login, connection ensure, action list/run, request proxy) with a clear flags table, fully executable with documented placeholders.	5 / 5
Workflow Clarity	The connection flow has explicit validation checkpoints and feedback loops (poll until READY, re-poll after CLIENT_ACTION_REQUIRED, inspect error on CONFIGURATION_ERROR), but a dangling "Step 2" reference with no matching numbered section introduces a minor gap.	4 / 5
Progressive Disclosure	No bundle files exist, so the single SKILL.md carries everything; sections are well-organized and easy to navigate, though the "Searching for actions" and "Popular actions" sections overlap and the >50-line body has minor structural redundancy.	4 / 5
	Total	17 / 20 Passed

Description

57%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 establishes a clear, specific niche (Cusdis) with an explicit use-when clause and third-person voice, but its action list is generic boilerplate rather than concrete Cusdis operations. Tightening the verbs and adding concrete trigger phrases would lift specificity and trigger-term quality.

Suggestions

Replace the generic "Manage data, records, and automate workflows" with concrete Cusdis actions such as "moderate comments, manage sites, configure webhooks, and handle reactions".

Expand the when-clause with concrete trigger phrases users would say, e.g. "Use when the user wants to moderate Cusdis comments, manage sites, or configure comment-system webhooks".

Add natural synonyms (e.g. "comments", "comment system", "embeddable comments") to broaden trigger-term coverage beyond the bare product name.

Dimension	Reasoning	Score
Specificity	Names the domain (Cusdis) but the actions "Manage data, records, and automate workflows" are generic and could apply to any integration, not concrete Cusdis-specific operations like moderating comments or managing sites.	2 / 5
Completeness	Both a "what" (manage data, records, automate workflows) and an explicit "when" ("Use when the user wants to interact with Cusdis data") are present, though the when-clause is generic rather than concrete trigger phrases.	4 / 5
Trigger Term Quality	The core natural term "Cusdis" / "Cusdis data" is present and would be said by a user, but coverage lacks synonyms or broader trigger phrases, fitting the "some relevant keywords but missing variations" anchor.	3 / 5
Distinctiveness Conflict Risk	The specific "Cusdis" trigger gives it a clear niche with minimal conflict against unrelated skills, but the templated generic verb set ("manage data, records, automate workflows") risks minor overlap with sibling Membrane integration skills.	4 / 5
	Total	13 / 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/cusdis/SKILL.md
Commit: f484c82

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