Name: coperniq
Rating: 59.2 (1 reviews)
Author: membranedev

coperniq

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

Quality

69%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/coperniq/SKILL.md

Quality

Content

76%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 executable CLI commands and a well-structured connection workflow including state-based validation. Its main weaknesses are missing verification steps for destructive action runs and a long inline actions table that would benefit from externalization.

Suggestions

Add a verification step after destructive/batch actions (e.g., re-fetch with get-client to confirm a delete or update took effect) so workflow clarity can exceed 3.

Move the full 'Popular actions' table into a references file and keep only a few representative examples inline in SKILL.md.

Trim marketing-style asides ('focus on the integration logic rather than auth plumbing', 'fastest way to get a connection') for tighter token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is largely code-forward with tables and commands, but contains minor padding such as 'so you can focus on the integration logic rather than auth plumbing' and 'This is the fastest way to get a connection.' that could be trimmed.	4 / 5
Actionability	It provides copy-paste-ready, fully executable commands throughout (install, login, connection ensure/get with --wait, action list/run, proxy) with concrete flags and JSON examples covering the common cases.	5 / 5
Workflow Clarity	The connection flow has a clear sequence with state-checking and a poll-after-action feedback loop, but the skill exposes destructive/batch actions (delete-client, update-*) with no validation or verification guidance after running them, capping this dimension at 3.	3 / 5
Progressive Disclosure	The body is well-organized into clear sections with no nested references, but the 20-row 'Popular actions' table is reference-style content inlined in SKILL.md that could live in a separate file.	4 / 5
	Total	16 / 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 cleanly states what the skill does and when to use it with third-person voice, but it leans on a single generic verb ('Manage') and a narrow, product-name-only trigger. Expanding the action verbs and natural trigger phrases would raise specificity and trigger quality.

Suggestions

Replace the generic 'Manage' with specific verbs (e.g., 'List, create, update, and delete Organizations, Pipelines, Users, and Filters') to lift specificity.

Broaden the trigger clause with natural phrases users say (e.g., 'Use when the user wants to query Coperniq clients, projects, work orders, or contacts').

Add concrete trigger nouns from the actual API (clients, projects, requests, work orders) so the skill surfaces for the right requests.

Dimension	Reasoning	Score
Specificity	It names the domain and several concrete entities ('Manage Organizations, Pipelines, Users, Filters'), but the only action verb is the generic 'Manage', so coverage of distinct actions is not comprehensive.	3 / 5
Completeness	It states both a clear 'what' ('Coperniq integration. Manage Organizations, Pipelines, Users, Filters.') and an explicit 'when' ('Use when the user wants to interact with Coperniq data.'), though the 'when' could be more specific with concrete trigger phrases.	4 / 5
Trigger Term Quality	The trigger relies on the proper-noun product name plus 'interact with Coperniq data'; relevant but missing common natural-language variations or synonyms users might say.	3 / 5
Distinctiveness Conflict Risk	The unique proper-noun product name gives it a clear niche with minimal conflict risk, but the limited trigger variety leaves minor overlap risk among sibling integration 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/coperniq/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.