Name: invision-community
Rating: 58.4 (1 reviews)
Author: membranedev

invision-community

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

Quality

67%

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

Quality

Content

68%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 delivers highly actionable, copy-paste CLI guidance organized in clear sections, but is let down by a padded marketing intro, a dangling 'Step 2' reference, and the absence of validation checkpoints around destructive action execution.

Suggestions

Remove the opening platform-marketing paragraph and 'auth plumbing' fluff; let the skill open with the install/connect workflow.

Define the referenced 'Step 2' explicitly (or renumber sections) so the 'skip to Step 2' instruction resolves to a concrete heading.

Add a validation/verification checkpoint before destructive or batch action runs and proxy DELETE/PUT calls (e.g. confirm scope or read-then-write) to raise workflow clarity.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient CLI commands, but the opening marketing paragraph ('platform for building online forums... used by businesses and individuals') and 'so you can focus on the integration logic rather than auth plumbing' are unnecessary padding Claude does not need.	3 / 5
Actionability	Copy-paste-ready executable commands with clearly marked placeholders (CONNECTION_ID, QUERY, actionId, <agentType>) cover install, auth, connect, search, run, and proxy use cases.	5 / 5
Workflow Clarity	The connection phase has an explicit state-machine (READY/BUILDING/CLIENT_ACTION_REQUIRED) with re-poll checkpoints, but the text references an undefined 'Step 2' and there is no validation around potentially destructive action runs or proxy DELETE requests, capping clarity at 3.	3 / 5
Progressive Disclosure	The single SKILL.md is well-organized into clear sections with no nested references and no bundle files to mis-signal; at ~150 lines it exceeds the under-50-line 5-exception, and 'Popular actions' partly duplicates 'Searching for actions', leaving minor gaps.	4 / 5
	Total	15 / 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 correctly pairs a capability statement with an explicit 'Use when' trigger and is anchored to a distinct named platform, but its action language is generic and its trigger vocabulary lacks synonyms users would naturally say.

Suggestions

Replace generic verbs with concrete Invision Community actions, e.g. 'Create and moderate forum topics, manage members and clubs, query Commerce orders and Downloads files'.

Expand the trigger with natural synonyms users say, e.g. 'Use when working with Invision Community forums, members, topics, or IPS community data'.

Dimension	Reasoning	Score
Specificity	Names the Invision Community domain plus 'Manage data, records, and automate workflows', but the actions are generic/buzzwordy ('manage data', 'automate workflows') rather than concrete, so coverage is not comprehensive.	3 / 5
Completeness	Both a 'what' ('Manage data, records, and automate workflows') and an explicit 'Use when the user wants to interact with Invision Community data' trigger are present, though the trigger is not maximally concrete.	4 / 5
Trigger Term Quality	Contains the natural product name 'Invision Community' and 'data', but misses common synonyms a user might say such as forums, topics, members, or IPS.	3 / 5
Distinctiveness Conflict Risk	It targets a named platform (Invision Community) with product-specific triggers, giving it 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/invision-community/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.