Name: copperx
Rating: 52.8 (1 reviews)
Author: membranedev

copperx

Copperx integration. Manage Organizations, Pipelines, Users, Filters. Use when the user wants to interact with Copperx data.

Quality

59%

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

Quality

Content

56%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 content is highly actionable with concrete, executable CLI commands and a sensible connection workflow, but it is weighed down by a large non-actionable entity list and an unhelpful failure-state stub. Material that should live in separate reference files is inlined because no bundle exists.

Suggestions

Remove the ~90-item bare entity bulleted list and the 'I don't have enough information about Copperx' stub line; they consume tokens without adding actionable guidance.

Move the popular-actions table and any extended API reference into a separate references/ file and link to it from SKILL.md to improve progressive disclosure.

Add an explicit validation/check step before running create/update/delete actions (e.g., confirm the action id and input against the schema returned by 'membrane action list') to strengthen the workflow's feedback loop.

Dimension	Reasoning	Score
Conciseness	A ~90-item bare bulleted list of entity nouns ('Company', 'Person', 'Opportunity' ... 'Print') plus a 'I don't have enough information about Copperx' stub line are padded sections that add no actionable value and assume little of Claude's competence.	2 / 5
Actionability	Provides concrete executable commands for install, login, connection ensure/get, action list/run, and proxy requests, with flags explained and a popular-actions table; only minor gaps remain.	4 / 5
Workflow Clarity	A clear sequence (install -> login -> connection ensure -> wait/poll -> search actions -> run/proxy) with state handling (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a polling feedback loop, though explicit pre-execution validation for destructive runs is absent.	4 / 5
Progressive Disclosure	No bundle files exist and all content is inlined in SKILL.md; the large entity list and popular-actions table are reference material that belongs in separate files, though section headers provide some structure.	3 / 5
	Total	13 / 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 follows a reasonable structure with an explicit 'Use when' clause and a named app, but relies on a generic action verb ('Manage') and entity nouns that do not align with the skill's real actions. Trigger phrasing is generic and lacks natural synonyms.

Suggestions

Replace the generic verb 'Manage' with the concrete actions the skill actually supports (e.g., 'List and create customers, subscriptions, invoices, and products').

Expand the trigger clause with natural user phrases and synonyms (e.g., 'Use when the user wants to query or create Copperx customers, invoices, subscriptions, or payments').

Align the listed entities (Organizations, Pipelines, Users, Filters) with the actual Copperx actions documented in the body to avoid misleading the model.

Dimension	Reasoning	Score
Specificity	Names the domain and several entities ('Organizations, Pipelines, Users, Filters') but the action verb 'Manage' is generic and the named entities do not match the skill's actual billed actions, leaving coverage non-comprehensive.	3 / 5
Completeness	Both 'what' (Manage Organizations, Pipelines, Users, Filters) and an explicit 'when' clause are present, but the 'when' is generic rather than concrete.	4 / 5
Trigger Term Quality	The only trigger phrase is 'Use when the user wants to interact with Copperx data' with the generic verb 'interact'; the named entities are not natural user phrases and synonyms/extensions are missing.	3 / 5
Distinctiveness Conflict Risk	Naming the specific app 'Copperx' with an explicit trigger gives it a clear niche and low conflict risk, though the generic entity nouns overlap somewhat with related CRM/billing 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/copperx/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.