Name: upviral
Rating: 62.4 (1 reviews)
Author: membranedev

upviral

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

Quality

74%

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

Quality

Content

75%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 highly actionable with executable Membrane CLI commands and a well-sequenced connection workflow featuring state-based validation checkpoints. Its main weakness is conciseness — a long entity bullet list and some duplicated content add tokens without proportional value.

Suggestions

Trim the ~30-item entity bullet list to the handful users actually act on, or move the full catalog to a separate reference file linked from the overview.

Remove the duplicated action-discovery command in 'Popular actions' since the same `membrane action list --intent` invocation already appears in 'Searching for actions'.

Resolve the dangling 'Step 2' reference (and the lone '1b' subsection) with consistent numbered steps so the connection workflow reads as one coherent sequence.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete CLI commands, but the ~30-item entity bullet list, the introductory platform paragraph, and a duplicated action-list command in 'Popular actions' add padding that could be trimmed.	3 / 5
Actionability	Fully executable, copy-paste-ready commands cover the common cases (install, login, connection ensure, action list/run, request) with concrete flag tables and JSON-output guidance.	5 / 5
Workflow Clarity	The connection setup is a clear sequenced workflow with state-based checkpoints (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and an explicit poll-again feedback loop; minor gaps like the unresolved 'Step 2' reference keep it just below anchor 5.	4 / 5
Progressive Disclosure	Single file with clear section headers and no bundle files to reference; structure is good and content is mostly well-placed, though the large inline entity overview could arguably live in its own reference file.	4 / 5
	Total	16 / 20 Passed

Description

73%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 identifies the UpViral niche and includes an explicit 'Use when' trigger, but the capability statement relies on generic verbs ('manage', 'automate') rather than concrete UpViral-specific actions. It is solid and distinct, just not maximally specific.

Suggestions

Replace generic verbs with concrete UpViral actions, e.g. 'Create and manage campaigns, referral programs, leads, and rewards' instead of 'Manage data, records, and automate workflows'.

Add natural feature-level trigger terms users would say, such as 'referral programs', 'contests', 'leads', or 'viral campaigns'.

Dimension	Reasoning	Score
Specificity	Names the UpViral domain and a couple of actions ("Manage data, records, and automate workflows"), but the actions are generic rather than concrete like 'extract' or 'create campaign', so it sits at the domain-plus-1-2-actions anchor rather than above.	3 / 5
Completeness	Both halves are present — "Manage data, records, and automate workflows" answers what and "Use when the user wants to interact with UpViral data" answers when explicitly; the 'what' is somewhat vague, so it does not reach the fully-concrete anchor 5.	4 / 5
Trigger Term Quality	The brand term "UpViral" plus "interact with UpViral data" gives good natural keyword coverage a user would actually say; a few synonyms or feature-level terms (campaigns, referrals, contests) are missing, keeping it just below comprehensive.	4 / 5
Distinctiveness Conflict Risk	"UpViral integration" targets a specific named SaaS product with a distinct brand trigger, giving it a clear niche and minimal overlap with other skills.	5 / 5
	Total	16 / 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/upviral/SKILL.md
Commit: f484c82

Reviewed: ~21 hours 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.