Name: loopify
Rating: 53.6 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

loopify

Loopify integration. Manage Organizations, Users. Use when the user wants to interact with Loopify data.

Quality

60%

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

Quality

Content

63%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 executable commands and a clear connection-flow feedback loop, but it is held back by verbosity, an inconsistent step numbering scheme, and inlined reference material that lacks external progressive-disclosure structure. No bundle files are present.

Suggestions

Fix the step numbering: 'Step 2' is referenced before the only numbered step '1b', making the connection workflow sequence incoherent — renumber as a single clear 1→2→3 flow.

Add an explicit validation/output-check step after `membrane action run` (e.g., check the `output` field and handle errors) to satisfy the feedback-loop expectation for batch/API operations.

Move the proxy flag table and clientAction schema into a separate reference file (e.g., REFERENCE.md) and link to it, reducing body length and improving progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with executable commands throughout, but sections like 'Loopify is a video hosting platform...' and verbose explanations of CLI behavior (e.g., the long clientAction bullet list) could be tightened, fitting 'Mostly efficient but includes some unnecessary explanation'.	3 / 5
Actionability	It provides copy-paste ready commands for install, login, connection, action search/run, and proxying, plus a complete options table — fully executable and covering the common cases, matching the 5 anchor.	5 / 5
Workflow Clarity	The connection setup has a clear sequence with poll-until-READY feedback, but the document jumps between numbered/lettered steps inconsistently ('Step 2' referenced before '1b'), and the action-search-then-run workflow lacks explicit validation of outputs before proceeding, matching 'Steps listed but validation gaps'.	3 / 5
Progressive Disclosure	There is reasonable section structure (Overview, Install, Auth, Searching, Running, Proxy, Best practices) but no external bundle files exist and the body inlines material that reads like reference (the full proxy flag table, the clientAction schema), matching 'Some structure but could be better organized; content that should be separate is inline'.	3 / 5
	Total	14 / 20 Passed

Description

56%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 names the target product and includes an explicit 'Use when' trigger, but the actions ('Manage') are generic and the trigger phrase lacks concrete synonyms or specific operation terms. It is solid but not comprehensive.

Suggestions

Replace the generic verb 'Manage' with concrete actions, e.g., 'Create, update, and list Organizations and Users in Loopify'.

Add natural trigger terms and synonyms a user would actually say, e.g., 'Use when the user wants to sync, query, or manage Loopify Organizations and Users'.

Tie the 'when' clause to more specific situations (e.g., 'when the user mentions Loopify contacts or video data') to reduce overlap with generic data skills.

Dimension	Reasoning	Score
Specificity	Names the domain (Loopify) and two entities ('Organizations, Users') but lists no concrete actions — 'Manage' is a generic verb, fitting the 'Names the domain but actions are minimal or generic' anchor rather than the 3 anchor which requires 1-2 concrete actions.	2 / 5
Completeness	It has a clear 'what' (manage Organizations, Users) and an explicit 'when' ('Use when the user wants to interact with Loopify data'), but the 'when' is broad rather than tied to concrete trigger phrases, fitting 'Has both what and when; when could be more explicit or specific' rather than the 5 anchor.	4 / 5
Trigger Term Quality	'interact with Loopify data' is a natural phrase a user might say, but it is generic and lacks synonyms or specific operation terms (e.g., 'sync', 'export contacts'), matching 'Some relevant keywords but missing common variations or synonyms'.	3 / 5
Distinctiveness Conflict Risk	The 'Loopify' product name is specific and unlikely to clash with other skills, but 'interact with Loopify data' is a somewhat broad trigger with minor overlap risk for generic data-skill intents, matching 'Mostly distinct; minor overlap risk'.	4 / 5
	Total	13 / 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/loopify/SKILL.md
Commit: f484c82

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