Name: copper
Rating: 69.6 (1 reviews)
Author: membranedev

copper

Copper integration. Manage Persons, Organizations, Leads, Deals, Projects, Activities and more. Use when the user wants to interact with Copper data.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

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.

A solid, actionable integration skill with concrete commands and a well-specified connection state machine. The main weaknesses are minor verbosity in the intro and a couple of structural inconsistencies (a referenced "Step 2" that is never defined and an orphaned "1b" heading).

Suggestions

Remove or tighten the marketing-style opening paragraph about what Copper is and who uses it; Claude does not need CRM market context to run the CLI.

Fix the broken cross-reference: the body says "skip to Step 2" and labels a heading "1b", but no Step 1a/Step 2 exists — renumber the connecting-to-Copper sequence consistently.

Merge the redundant "Popular actions" section (which restates the `action list` command from "Searching for actions") to avoid duplicating the same guidance.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but the opening CRM background paragraph ("Copper is a CRM designed to help small and medium-sized businesses...") and the duplicate action-list command in "Popular actions" add minor over-explanation that could be trimmed.	4 / 5
Actionability	It provides fully executable, copy-paste-ready commands for the common cases (install, login, connection ensure, action list/run, request proxy) plus a complete flags table, covering the standard workflow end to end.	5 / 5
Workflow Clarity	The connection flow has an explicit state machine with feedback loops (poll until READY, re-poll after CLIENT_ACTION_REQUIRED), but a broken "Step 2" reference and an orphaned "1b" heading introduce a minor sequencing gap.	4 / 5
Progressive Disclosure	As a single self-contained file with no bundle references, it is well organized into clear sections; minor organization gaps (the "1b"/"Step 2" inconsistency and the redundant "Popular actions" heading) keep it just below a top score.	4 / 5
	Total	17 / 20 Passed

Description

87%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.

A concise, well-structured description that names the specific Copper CRM entities, uses third-person voice, and includes an explicit "Use when" trigger. It is largely comprehensive with only minor specificity gaps from relying on one generic verb.

Dimension	Reasoning	Score
Specificity	The description enumerates multiple concrete managed entities ("Persons, Organizations, Leads, Deals, Projects, Activities") but applies a single generic verb ("Manage") to all of them, leaving minor coverage gaps versus a fully comprehensive action list.	4 / 5
Completeness	It explicitly answers both what ("Manage Persons, Organizations, Leads, Deals, Projects, Activities...") and when ("Use when the user wants to interact with Copper data") with a concrete trigger clause, satisfying the anchor for a complete description.	5 / 5
Trigger Term Quality	Natural CRM terms appear ("Copper", "Leads", "Deals", "Persons", "interact with Copper data"), giving good keyword coverage, though common synonyms or alternate phrasings are not exhaustively listed.	4 / 5
Distinctiveness Conflict Risk	Naming a specific product (Copper) and its CRM entities carves a clear niche with distinct triggers and minimal overlap risk against unrelated skills.	5 / 5
	Total	18 / 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/copper/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.