Name: insightsoftware
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

insightsoftware

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

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/insightsoftware/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 actionable and well-structured with executable Membrane CLI commands and a clear connection-state workflow, but it is held back by marketing padding in the intro, a dangling "Step 2" reference, and missing verification guidance for destructive proxy/action operations. It lands just above the midpoint across all dimensions.

Suggestions

Remove the marketing intro ("Insightsoftware provides financial reporting and performance management solutions...") and other padding lines that assume Claude lacks context it already has.

Fix or remove the dangling "Step 2" reference, or add an explicit numbered Step 2 header so the connection workflow's continuation is unambiguous.

Add a verification/check step after destructive proxy requests and action runs (e.g. re-fetching the resource or checking the response status) to satisfy the destructive-operations workflow requirement.

Dimension	Reasoning	Score
Conciseness	The body is mostly commands and a useful flags table, but opens with marketing prose ("Insightsoftware provides financial reporting... Finance teams at mid-sized and large companies use it...") and padded lines like "so you can focus on the integration logic rather than auth plumbing", matching the 3 anchor for mostly-efficient with some unnecessary explanation; it is above 2 but the intro padding keeps it from 4.	3 / 5
Actionability	Concrete, copy-paste-ready commands appear throughout (install, login, connection ensure, action list/run, request) with a complete flags table, matching the 4 anchor for mostly-executable guidance; it is not 5 because placeholders like CONNECTION_ID and --intent "QUERY" are left unsubstituted without a worked end-to-end example.	4 / 5
Workflow Clarity	The connection workflow is well-sequenced with state checks and a poll-again feedback loop, but the body references a "Step 2" that has no corresponding header, and the proxy/action-run paths (which include destructive DELETE/PUT) lack any verification step, triggering the destructive-operations cap at 3 rather than 4.	3 / 5
Progressive Disclosure	No bundle files exist and the single SKILL.md is organized into clear, well-labeled sections (Overview, Working with, Authentication, Connecting, Searching, Popular actions, Proxy, Best practices), matching the 4 anchor for good structure; it is not 5 because some inline reference-like material (the flags table, full clientAction schema) could live in a separate reference file.	4 / 5
	Total	14 / 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 covers both what the skill does and when to use it with a third-person voice and an explicit trigger, but the capabilities are generic rather than concrete and the trigger phrasing lacks natural synonyms. It is solid but unspectacular, sitting just above the midpoint.

Suggestions

Replace generic verbs ("Manage data, records, automate workflows") with concrete Insightsoftware capabilities such as consolidate financial data, run report bursting, and schedule reports.

Expand the trigger clause to name natural phrases users would say, e.g. "Use when the user wants to consolidate financial reports, burst reports to users, or automate Insightsoftware workflows."

Add file/record-specific terms (e.g. reports, report groups, schedules) to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the domain and a couple of actions, but the actions are generic (manage, automate) rather than concrete capabilities like extracting or consolidating reports, so it sits at the 3 anchor and below 4 which requires several specific actions.	3 / 5
Completeness	It states both a "what" (manage data, records, automate workflows) and an explicit "Use when..." clause, satisfying the 4 anchor; it is not a 5 because the "when" is generic ("interact with...data") rather than concrete trigger phrases.	4 / 5
Trigger Term Quality	"Use when the user wants to interact with Insightsoftware data" surfaces the product name and "data", but lacks common variations or synonyms (e.g. financial reporting, consolidation), matching the 3 anchor for some relevant keywords with missing variations rather than the fuller coverage of 4.	3 / 5
Distinctiveness Conflict Risk	Tying triggers to the named product Insightsoftware gives it a clear niche with minor overlap risk (4 anchor); it is not a 5 because the surrounding action language (manage data, automate workflows) is broad enough to overlap with generic data skills.	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/insightsoftware/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.