Name: coterie-insurance
Rating: 56.8 (1 reviews)
Author: membranedev

coterie-insurance

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

Quality

65%

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

Quality

Content

68%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 an efficient, actionable guide to driving Coterie via the Membrane CLI, with a well-sequenced connection flow and good validation around connection states. Its main weaknesses are the lack of verification guidance for destructive proxy/action operations and a monolithic single-file structure.

Suggestions

Add a verification/feedback step for destructive operations, e.g. after a proxy DELETE or action run, suggest re-fetching the resource to confirm the change and handling non-2xx responses.

Move the detailed proxy options table and agent-type list into a short reference file linked from the body to improve progressive disclosure and trim the main SKILL.md.

De-duplicate the action-discovery command, which appears nearly verbatim in both 'Searching for actions' and 'Popular actions'.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean, relying on code blocks and an options table rather than prose, with only minor padding ('so you can focus on the integration logic rather than auth plumbing') and a small redundancy between the 'Searching for actions' and 'Popular actions' sections.	4 / 5
Actionability	It provides concrete, copy-paste-ready CLI commands with flags and a full proxy-options table; placeholders like CONNECTION_ID and <actionId> are expected and clearly marked, leaving only minor gaps around composing complex inputs.	4 / 5
Workflow Clarity	The connection setup has a clear sequence with strong validation checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR with re-polling), but the proxy section exposes destructive methods (DELETE) with no verification step, triggering the destructive-operations cap of 3.	3 / 5
Progressive Disclosure	Content is well organized under clear section headers and there are no bundle files to reference, but at ~140 lines everything is inlined with no one-level-deep references, so some material (e.g. full proxy options, agent types) could be split out.	4 / 5
	Total	15 / 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 a niche (Coterie Insurance) and includes an explicit 'Use when' clause, but its action verbs are generic and its trigger vocabulary is limited to the brand name. It is solid but could be sharper by borrowing concrete operations from the body.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Coterie operations such as 'get quotes, bind policies, and manage claims and billing'.

Expand the 'Use when' clause with natural trigger phrases users would say, e.g. 'Use when the user wants to get a business insurance quote, bind a policy, or manage Coterie claims and payments'.

Dimension	Reasoning	Score
Specificity	Names the domain (Coterie Insurance) plus a few actions ('Manage data, records, and automate workflows'), but the actions are generic business-app verbs rather than concrete operations like 'get quotes' or 'bind policies' that appear in the body.	3 / 5
Completeness	It explicitly answers both 'what' (manage data, records, automate workflows) and 'when' ('Use when the user wants to interact with Coterie Insurance data'), though the 'when' clause is fairly generic and could name concrete triggers.	4 / 5
Trigger Term Quality	The natural keyword 'Coterie Insurance' is present and repeated, but there are no synonyms, related terms (quotes, policies, claims), or file extensions; coverage is limited to the brand name.	3 / 5
Distinctiveness Conflict Risk	Naming a specific insurance provider gives it a clear niche with minimal conflict risk against other skills, though the generic action verbs leave slight overlap with any data-management skill.	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/coterie-insurance/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.