Name: chaport
Rating: 50.4 (1 reviews)
Author: membranedev

chaport

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

Quality

55%

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/chaport/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 is a strongly actionable CLI integration guide with good sequencing and state-handling checkpoints, held back by some marketing padding and an absence of validation guidance for its destructive/batch operations.

Suggestions

Add a validation/confirmation checkpoint before destructive actions, e.g. 'Before running delete-* actions, confirm the target ID with the user and verify via the corresponding get-* action.'

Trim marketing fluff such as 'so you can focus on the integration logic rather than auth plumbing' and the generic Chaport intro sentence about sales/support teams.

Provide one fully concrete worked example of `membrane action run` using a real popular action key (e.g. list-visitors) with actual output handling.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-dense and efficient, but includes padded/marketing lines ('Membrane handles authentication... so you can focus on the integration logic rather than auth plumbing') and a generic 'what Chaport is' intro that could be trimmed.	3 / 5
Actionability	It provides copy-paste-ready commands for install, auth, connection, action search, action run, and proxy with flag tables, but the 'action run' example uses generic placeholders (<actionId>, CONNECTION_ID) rather than a worked example against a real popular action.	4 / 5
Workflow Clarity	The connect-to-ready flow is well sequenced with state-polling checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but the skill exposes destructive operations (delete-visitor, delete-operator) and batch list operations with no validation/verification step before them, which caps this dimension at 3.	3 / 5
Progressive Disclosure	Content is well-organized with clear section headers and no nested references, and a CLI guide reasonably keeps commands inline; the only gap is the sizable 20-row 'Popular actions' catalog that could optionally live in a reference file.	4 / 5
	Total	14 / 20 Passed

Description

48%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 correctly names the Chaport niche and includes a 'Use when' clause, but its actions and triggers are generic rather than concrete, leaving both specificity and trigger quality underdeveloped.

Suggestions

Replace generic verbs with concrete Chaport actions, e.g. 'List and manage Chaport visitors, operators, webhooks, and chats; send messages and update tickets.'

Expand the trigger clause with natural phrases users say, e.g. 'Use when the user wants to manage Chaport visitors, operators, chat messages, webhooks, or tickets.'

Drop the padded 'automate workflows' phrasing in favor of specific capabilities to sharpen the 'what'.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Chaport integration') but its actions are generic ('Manage data, records, and automate workflows') rather than concrete Chaport operations like visitors, operators, webhooks, or messaging, matching the anchor for minimal/generic actions.	2 / 5
Completeness	Both a 'what' and a 'Use when...' clause are present, but the 'what' is vague ('Manage data, records, and automate workflows') and the 'when' simply rephrases the domain, so neither reaches the concrete, specific level of the 4-anchor.	3 / 5
Trigger Term Quality	It surfaces the natural keyword 'Chaport' and 'Chaport data', but the trigger phrase 'interact with Chaport data' restates the domain rather than listing concrete variations users would say (visitors, operators, chat, tickets), so coverage is partial.	3 / 5
Distinctiveness Conflict Risk	Naming the specific app 'Chaport' gives it a clear, distinct niche with low conflict risk, but the generic verbs ('manage data, records, automate workflows') keep it from the minimal-conflict, concrete-trigger level of the 5-anchor.	4 / 5
	Total	12 / 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/chaport/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.