Name: isn
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

isn

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

Quality

63%

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

Quality

Content

61%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 copy-paste CLI commands and a clear connection state machine, but is held back by prose over-explanation and a lack of validation around destructive actions. Progressive disclosure is adequate for a single-file integration skill but the large actions table could be split out.

Suggestions

Trim context Claude already knows (the ISN industry overview, 'fastest way to get a connection', and auth-plumbing commentary) to tighten conciseness.

Add an explicit confirm/verify checkpoint before running destructive actions (delete-agent, delete-contact), e.g. verify the entity exists and confirm with the user before deletion.

Fix the broken 'skip to Step 2' reference by labeling the 'Searching for actions' section as Step 2, and consider moving the 20-row Popular actions table into a reference file.

Dimension	Reasoning	Score
Conciseness	Commands and tables are lean, but several prose passages over-explain context Claude does not need (what ISN is, which industries use it, 'fastest way to get a connection', auth-plumbing benefits).	3 / 5
Actionability	Concrete, copy-paste-ready CLI commands cover connection, action search, action run, and proxying, plus a Popular actions table with keys; minor gaps remain since run examples use placeholders rather than a concrete action with real input.	4 / 5
Workflow Clarity	The connection flow is well-sequenced with a state machine and poll loop, but destructive actions (delete-agent, delete-contact) lack any confirm/verify checkpoint and 'skip to Step 2' references an unlabeled section, so the destructive-ops cap applies.	3 / 5
Progressive Disclosure	Single well-sectioned file with clear headers and no need for external references, but at over 50 lines with a 20-row actions table inlined and no reference split, it falls short of the ideal one-level-deep structure.	4 / 5
	Total	14 / 20 Passed

Description

66%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 ISN niche with an explicit 'Use when' trigger and a concrete entity list, but relies on a generic 'Manage' verb and a vague trigger phrase that limit specificity and trigger-term quality. The entity list also does not match the actions the skill actually exposes.

Suggestions

Replace the generic verb 'Manage' with the concrete CRUD actions the skill supports (e.g. 'list, get, create, update, and delete inspectors, agents, contacts, clients, and orders').

Tighten the trigger phrase to concrete natural terms a user would say, e.g. 'Use when the user wants to query or update ISN inspection orders, clients, agents, or contacts.'

Align the listed entities (Persons, Organizations, Deals, Leads, Projects, Activities) with the skill's actual actions (Users/Agents/Contacts/Clients/Orders) to avoid misleading triggers.

Dimension	Reasoning	Score
Specificity	Names the ISN domain and a broad list of concrete entities ('Persons, Organizations, Deals, Leads, Projects, Activities') but the verb 'Manage' is generic and does not enumerate specific actions like create/list/update/delete.	3 / 5
Completeness	Explicitly answers both 'what' (ISN integration; manage listed entities) and 'when' ('Use when the user wants to interact with ISN data'), though the trigger could be more specific.	4 / 5
Trigger Term Quality	Relevant domain keywords (ISN, entity names) are present, but the trigger phrase 'interact with ISN data' is generic, misses common synonyms, and the entity list mismatches the skill's actual actions.	3 / 5
Distinctiveness Conflict Risk	ISN is a specific named platform with distinct triggers, yielding a clear niche and minimal conflict risk with other skills.	5 / 5
	Total	15 / 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/isn/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.