Name: loopsso
Rating: 60 (1 reviews)
Author: membranedev

loopsso

Loops.so integration. Manage Persons, Organizations, Deals, Activities, Notes, Files and more. Use when the user wants to interact with Loops.so data.

Quality

70%

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/loopsso/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 delivers strong, executable Membrane CLI commands across the full integration lifecycle with decent section organization. It is held back by an unnecessary marketing intro, a broken 'Step 2' cross-reference, and duplicated action-discovery guidance.

Suggestions

Cut the opening marketing paragraph ('Loops.so is an email marketing platform specifically designed for SaaS...') and the 'so you can focus on the integration logic' padding; keep only operationally necessary context.

Fix the dangling 'skip to Step 2' references — either label an explicit 'Step 2: Search for actions' section or replace the references with the actual section name/link.

Merge the 'Searching for actions' and 'Popular actions' sections, which both demonstrate `membrane action list --intent`, to remove the duplicated guidance.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but opens with marketing-flavored padding ('specifically designed for SaaS and product-led growth companies... onboarding, engage, and retain customers') and soft phrasing like 'so you can focus on the integration logic rather than auth plumbing' that Claude does not need.	3 / 5
Actionability	Provides copy-paste-ready commands for install, login, connection ensure, polling, action list/run, and proxy requests plus a full flag table; minor gaps remain around the abstract '--intent QUERY' placeholder and unresolved CONNECTION_ID substitution.	4 / 5
Workflow Clarity	A rough sequence exists (install, login, connect, poll, search, run) with polling-based state checks, but the repeated 'skip to Step 2' references a Step 2 that is never defined, and the 'Searching for actions' and 'Popular actions' sections overlap, leaving checkpoints implicit and navigation broken.	3 / 5
Progressive Disclosure	Single-file skill with no bundle directories, but content is organized into clearly headed sections (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices); minor redundancy between the two action-discovery sections prevents a 5.	4 / 5
	Total	14 / 20 Passed

Description

78%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 is third-person, concise, and clearly names a specific product with an explicit 'Use when' trigger and a concrete list of managed entities. Its main weakness is a generic trigger clause and a single broad verb ('Manage') rather than multiple concrete actions.

Dimension	Reasoning	Score
Specificity	Names the Loops.so domain plus several concrete entity types ('Persons, Organizations, Deals, Activities, Notes, Files'), though the single verb 'Manage' and the vague 'and more' leave minor coverage gaps rather than multiple distinct actions.	4 / 5
Completeness	Explicitly answers both 'what' (Loops.so integration managing listed entities) and 'when' ('Use when the user wants to interact with Loops.so data'), but the 'when' clause is generic rather than packed with concrete trigger phrases, keeping it below a 5.	4 / 5
Trigger Term Quality	Includes the natural product name 'Loops.so' and entity keywords with an explicit 'Use when' trigger, but misses common synonyms or variations a user might actually say (e.g. 'email marketing', 'contacts', 'subscribers').	4 / 5
Distinctiveness Conflict Risk	Targets a specific named product (Loops.so) with distinct triggers, creating a clear niche with minimal risk of firing for unrelated skills.	5 / 5
	Total	17 / 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/loopsso/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.