Name: insightly
Rating: 64.8 (1 reviews)
Author: membranedev

insightly

Insightly integration. Manage Organizations, Deals, Projects, Activities, Notes, Files and more. Use when the user wants to interact with Insightly data.

Quality

77%

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/insightly/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 body is highly actionable with concrete executable commands and a well-structured connection workflow including state checkpoints. Its weaknesses are mild background verbosity at the top, a missing verify-before-destructive step given the proxy supports DELETE, and minor redundancy between the search and popular-actions sections.

Suggestions

Add an explicit validation/verification step before destructive proxy calls (e.g. GET to confirm the target record before running DELETE) so the destructive-operation workflow can exceed the score-3 cap.

Trim the opening CRM background paragraph to a one-line context statement to remove explanation Claude already knows.

Merge the "Searching for actions" and "Popular actions" sections to eliminate the duplicated `action list` command and reduce redundancy.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean commands and brief prose, but the opening "Insightly is a CRM and sales platform that helps businesses manage their customer relationships..." explains background Claude already knows and could be trimmed.	4 / 5
Actionability	It provides copy-paste-ready commands throughout (install, login, connection ensure, action list/run with --input JSON, request with a full flag table) covering the common cases with executable syntax.	5 / 5
Workflow Clarity	The connection flow is sequenced with state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll-again feedback loop, but the proxy section exposes DELETE without any verify-before-destructive guidance, so the destructive-operation cap of 3 applies.	3 / 5
Progressive Disclosure	No bundle files exist and none are needed since actions are discovered dynamically via the CLI; sections are well-organized with clear headers, though the "Insightly Overview" object list is sparse and "Popular actions" restates the earlier action-list command.	4 / 5
	Total	16 / 20 Passed

Description

78%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 clearly identifies the product niche and lists concrete managed entities with an explicit use-trigger, making it distinct and actionable. Its main weakness is the generic "interact with Insightly data" trigger phrasing, which lacks concrete scenario synonyms that would lift completeness and trigger-term quality.

Suggestions

Expand the "Use when..." clause with concrete scenarios, e.g. "Use when the user wants to create or update Insightly organizations, deals, projects, activities, notes, or files, or search Insightly CRM records."

Replace the generic verb "Manage" with a few specific verbs (create, update, search, list) to sharpen specificity beyond the score-4 anchor.

Drop the vague "and more" or replace it with the actual additional capabilities to avoid an over-claim.

Dimension	Reasoning	Score
Specificity	"Manage Organizations, Deals, Projects, Activities, Notes, Files and more" lists several concrete named objects the skill operates on, though the trailing "and more" and generic verb "Manage" leave minor coverage gaps.	4 / 5
Completeness	It has a clear "what" (manage the listed Insightly entities) and an explicit "when" ("Use when the user wants to interact with Insightly data"), but the "when" is generic rather than tied to concrete trigger scenarios, matching the score-4 anchor rather than 5.	4 / 5
Trigger Term Quality	"Insightly" plus the entity names (Organizations, Deals, Projects, Activities, Notes, Files) give good natural keyword coverage, but the trigger clause only restates "interact with Insightly data" and omits common synonyms or scenario phrasings.	4 / 5
Distinctiveness Conflict Risk	"Insightly integration... Use when the user wants to interact with Insightly data" carves a clear niche around a specific named CRM product with minimal overlap risk against other skills.	5 / 5
	Total	17 / 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/insightly/SKILL.md
Commit: f484c82

Reviewed: ~21 hours 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.