Name: viral-loops
Rating: 58.4 (1 reviews)
Author: membranedev

viral-loops

Viral Loops integration. Manage data, records, and automate workflows. Use when the user wants to interact with Viral Loops 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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/viral-loops/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 is well-structured and gives executable CLI commands, but it lacks Viral-Loops-specific action examples, has broken step numbering, and omits validation checkpoints for potentially destructive action/proxy operations.

Suggestions

Fix the workflow numbering: add a "1a" heading and relabel "Step 2" so the connection-to-action sequence is unambiguous.

Add a concrete Viral-Loops action example (e.g. `membrane action run <campaignListId> --connectionId=... --input '{"token":"..."}'`) instead of only generic placeholders.

Add a verification step after running actions or proxy POST/PUT/DELETE calls, e.g. re-fetching the affected record to confirm the change before reporting success.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean executable commands and a flag table, with only minor over-explanation such as the opening marketing sentence and asides like "so you can focus on the integration logic rather than auth plumbing", fitting the score-4 efficient-with-trimmable-bits anchor.	4 / 5
Actionability	It provides concrete, copy-paste-ready membrane commands for install, auth, connection, action search/run, and proxying, but every example is a generic membrane invocation with placeholders and no Viral-Loops-specific action examples (e.g. listing campaigns or creating a user), leaving a minor coverage gap at score 4 rather than 5.	4 / 5
Workflow Clarity	The connection flow has a real feedback loop (poll for READY vs CLIENT_ACTION_REQUIRED vs error states), but step numbering is broken (a "1b" with no "1a" and references to an undefined "Step 2"), and running actions or proxy POST/PUT/DELETE requests has no validation/verification step, which caps destructive/batch workflows at 3.	3 / 5
Progressive Disclosure	Content is organized into clear, well-labeled sections (Overview, Authentication, Connecting, Searching, Running actions, Proxy, Best practices) with no bundle files to reference, giving good structure with only minor organization gaps, fitting score 4.	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 covers what and when and is anchored to a distinct named platform, but its action language is generic and it misses the natural referral/campaign trigger terms a user would say.

Suggestions

Replace generic verbs with concrete Viral Loops operations, e.g. "Create and manage referral campaigns, track participants, and log referral events."

Add natural trigger synonyms such as "referral program", "referral campaign", and "campaign" so the skill matches how users actually phrase the request.

Make the "when" clause less circular by tying it to user intent, e.g. "Use when the user wants to set up or manage a referral or viral campaign in Viral Loops."

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the domain plus a couple of action areas, but the actions are generic categories rather than concrete operations, fitting the score-3 anchor of naming the domain with 1-2 non-comprehensive actions.	3 / 5
Completeness	Both "what" ("Manage data, records, and automate workflows") and "when" ("Use when the user wants to interact with Viral Loops data") are present, but the "when" is somewhat circular and could be more explicit, fitting score 4 rather than 5.	4 / 5
Trigger Term Quality	It surfaces the natural product name "Viral Loops" and the trigger "interact with Viral Loops data", but omits common synonyms a user would actually say such as "referral program", "referral campaign", or "campaign", matching the score-3 anchor of some relevant keywords missing common variations.	3 / 5
Distinctiveness Conflict Risk	"Viral Loops integration" pins a specific named platform with a distinct trigger, giving it a clear niche and minimal conflict risk with other skills, matching the score-5 anchor.	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/viral-loops/SKILL.md
Commit: f484c82

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