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

insites

Insites integration. Manage Organizations, Pipelines, Users, Filters, Activities, Notes and more. Use when the user wants to interact with Insites data.

Quality

78%

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

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.

The body is highly actionable with concrete, copy-paste-ready CLI commands and a well-sequenced connection workflow featuring real validation and feedback loops. Its main weaknesses are minor padding in the intro and no validation guidance for destructive delete operations.

Suggestions

Trim the marketing-style opening paragraph ('helps businesses identify and target potential customers...') since Claude does not need it to operate the integration.

Add a validation/checkpoint step before running destructive actions (e.g. confirm the record id and re-fetch before delete-* operations).

Consider moving the 20-row popular-actions table into a separate ACTIONS.md reference and keeping only a few key examples inline, to reduce SKILL.md length.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with lean CLI commands and reference tables, but a few padded bits could be trimmed: the marketing-style intro ('helps businesses identify and target potential customers') and phrases like 'so you can focus on the integration logic rather than auth plumbing'.	4 / 5
Actionability	Provides copy-paste-ready, fully executable commands for every stage (install, login, connect, poll, search, run, proxy) plus a 20-row action table and a proxy-flag table that cover the common cases.	5 / 5
Workflow Clarity	The connection flow is clearly sequenced with explicit validation via state polling and a feedback loop (poll again after CLIENT_ACTION_REQUIRED), but there is no validation/checkpoint guidance before destructive operations such as delete-* actions, leaving a minor validation gap.	4 / 5
Progressive Disclosure	Well-organized into clear sections with no problematic nested references, but at ~160 lines it exceeds the simple-skill threshold and inlines a large 20-row actions table that could live in a separate reference file, so it stops short of anchor 5's 'appropriately split' bar.	4 / 5
	Total	17 / 20 Passed

Description

73%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 its niche (Insites) and includes an explicit 'Use when' trigger, but its action language is generic ('Manage ... and more') and the trigger phrase lacks concrete specificity. Strong on distinctiveness, adequate on the rest.

Suggestions

Replace the generic verb 'Manage' with concrete actions, e.g. 'List, create, update, and delete Organizations, Pipelines, Users, Filters, Activities, and Notes'.

Drop the vague filler 'and more' or replace it with the remaining specific entities.

Make the 'Use when' trigger more concrete, e.g. 'Use when the user wants to query, create, or update Insites CRM records, pipelines, or activities.'

Dimension	Reasoning	Score
Specificity	Names the Insites domain and six concrete entities ('Organizations, Pipelines, Users, Filters, Activities, Notes') but relies on a single generic verb 'Manage' plus vague filler 'and more', rather than several distinct concrete actions as anchor 4 requires.	3 / 5
Completeness	Provides a clear 'what' and an explicit 'Use when the user wants to interact with Insites data' clause, but the trigger phrase is generic rather than concrete, so it stops short of anchor 5.	4 / 5
Trigger Term Quality	Good keyword coverage with the brand term 'Insites' (repeated) plus six entity nouns a user would naturally name, though common action-word synonyms (list/create/update) are absent.	4 / 5
Distinctiveness Conflict Risk	Tightly anchored to the named 'Insites' SaaS with brand-specific triggers, giving it a clear niche and minimal conflict risk with other skills.	5 / 5
	Total	16 / 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/insites/SKILL.md
Commit: f484c82

Reviewed: 5 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.