Name: spiritme
Rating: 52 (1 reviews)
Author: membranedev

spiritme

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

Quality

57%

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

Quality

Content

57%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 solid connection-readiness polling loop, but it is weakened by a marketing-flavored intro, confusing step references (an undefined Step 2, a 1b without 1a), and a thin redundant "Popular actions" section. No bundle files are present, so progressive disclosure is single-file only.

Suggestions

Fix the step numbering: define a labeled "Step 1"/"Step 2" or replace "skip to Step 2" with an explicit anchor so the connection-to-action flow is unambiguous.

Trim the product-marketing intro and the "burn less tokens" prose; keep only what Claude needs to run the CLI commands.

Either populate the "Popular actions" section with concrete named SpiritMe actions or remove it to avoid duplicating the "Searching for actions" guidance.

Dimension	Reasoning	Score
Conciseness	The bulk is efficient executable commands and a flags table, but the marketing-style opening ("SaaS platform that uses AI to create personalized video messages...") and prose like "so you can focus on the integration logic rather than auth plumbing" and "burn less tokens" could be trimmed.	3 / 5
Actionability	It provides concrete, copy-paste-ready commands for install, login, connection, action search/run, and proxying, plus a flags table; minor gaps such as the thin "Popular actions" section keep it from a 5.	4 / 5
Workflow Clarity	A real sequence exists with a polling feedback loop for connection states, but "skip to Step 2" references a Step 2 that is never labeled and the "1b" heading has no corresponding 1a, leaving checkpoints implicit and navigation confusing.	3 / 5
Progressive Disclosure	The single file is reasonably sectioned with headers, but no bundle/reference files exist, the connection-state and proxy-flag detail could live in separate references, and the "Popular actions" section duplicates earlier content.	3 / 5
	Total	13 / 20 Passed

Description

57%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 clearly targeted at a distinct product and includes an explicit Use-when trigger, but its capability list is generic and omits SpiritMe's actual features (avatars, videos). Tightening the action list to concrete capabilities would lift specificity and trigger quality.

Suggestions

Replace generic verbs with concrete SpiritMe capabilities, e.g. "Create avatar videos, manage avatars and outfits, and render personalized video messages."

Add natural trigger synonyms users might say, such as "avatar video," "AI video message," or "SpiritMe video."

Keep the explicit "Use when..." clause but tie it to those concrete capabilities rather than the vague "interact with SpiritMe data."

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the SpiritMe domain but the actions are generic abstractions rather than concrete capabilities, and the actual SpiritMe features (avatars, videos) are never mentioned.	2 / 5
Completeness	It states both a what ("Manage data, records, and automate workflows") and an explicit when ("Use when the user wants to interact with SpiritMe data"), though the what is somewhat generic.	4 / 5
Trigger Term Quality	"SpiritMe" and "interact with SpiritMe data" give a relevant keyword, but common natural variations or synonyms users might say are missing.	3 / 5
Distinctiveness Conflict Risk	"SpiritMe integration" carves a clear niche tied to a specific SaaS product with a distinct trigger, with only minor overlap risk against other integration skills.	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/spiritme/SKILL.md
Commit: f484c82

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