Name: extensiv-integration-manager
Rating: 56.8 (1 reviews)
Author: membranedev

extensiv-integration-manager

Extensiv Integration Manager integration. Manage data, records, and automate workflows. Use when the user wants to interact with Extensiv Integration Manager 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/extensiv-integration-manager/SKILL.md

Quality

Content

65%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 concrete executable commands and a useful actions table, but it suffers from a padded overview list and missing verification steps around destructive operations.

Suggestions

Add an explicit validation/verification checkpoint before and after running destructive actions like cancel-order or update-inventory to raise workflow clarity.

Move the 34-item flat entity list and the full popular-actions table into a separate reference file, keeping SKILL.md as a concise overview.

Trim the introductory SaaS explanation and "Use action names and parameters as needed" filler to improve token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is mostly executable commands and tables, but the flat 34-item entity list and the introductory SaaS explanation add padding that could be tightened without losing clarity.	3 / 5
Actionability	It provides copy-paste-ready commands for login, connection ensure, action list, action run, and proxy requests, plus a concrete popular-actions table with keys, covering the common cases.	5 / 5
Workflow Clarity	There is a clear install->login->connect->search->run sequence with state polling for connections, but running destructive actions (cancel-order, update-inventory) lacks explicit verification steps, which caps this dimension at 3.	3 / 5
Progressive Disclosure	Section headers organize the single-file body, but with no bundle files present, large inline blocks (the 34-entity overview and the actions table) that could live in separate references are not split out or signaled.	3 / 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 product niche and includes both a what and a when clause, but the action verbs are generic and the trigger relies almost entirely on the product name without natural task keywords.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete actions such as syncing orders, inventory, or warehouse data.

Add natural user-facing trigger phrases (e.g. "when the user mentions orders, inventory, or warehouse integrations") beyond the product name.

Mention common synonyms or adjacent terms (3PL, WMS, eCommerce integrations) to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Phrases like "Manage data, records, and automate workflows" name the domain and a few action verbs, but the actions remain generic rather than concrete (no listing of specific integration operations).	3 / 5
Completeness	It states both what ("Manage data, records, and automate workflows") and when ("Use when the user wants to interact with Extensiv Integration Manager data"), matching the anchor for both present with a slightly generic trigger clause.	4 / 5
Trigger Term Quality	"Use when the user wants to interact with Extensiv Integration Manager data" surfaces the product name as the main trigger, but it lacks common variations, synonyms, or concrete task keywords users would naturally say.	3 / 5
Distinctiveness Conflict Risk	"Extensiv Integration Manager" is a clearly named product niche with a distinct trigger ("Use when the user wants to interact with Extensiv Integration Manager"), giving 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/extensiv-integration-manager/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.