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

weavr

Weavr.io integration. Manage data, records, and automate workflows. Use when the user wants to interact with Weavr.io 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/weavr/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 copy-paste-ready CLI commands and a strong, state-checked connection workflow, organized into clear sections. Its main weakness is conciseness, with a marketing-style opener and a few editorial asides that do not earn their tokens.

Suggestions

Cut the opening marketing paragraph ("Weavr is a platform that enables businesses to embed financial services...") and the "so you can focus on the integration logic rather than auth plumbing" aside; keep only what Claude needs to act.

Fix the broken step navigation by adding explicit "Step 1" / "Step 2" headers so the "skip to Step 2" and "#### 1b" references resolve clearly.

Either briefly annotate the bare Overview entity list (Journey, Step, Variable, Integration, etc.) or remove it, since a list of nouns with no explanation gives Claude little to act on.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient executable commands, but the opening marketing paragraph ("platform that enables businesses to embed financial services...") and editorial asides ("so you can focus on the integration logic rather than auth plumbing", "This is the fastest way to get a connection") are unnecessary and could be trimmed.	3 / 5
Actionability	It provides copy-paste-ready, executable membrane/npx commands covering the common cases (connect, poll, search actions, run actions, proxy) along with a concrete flag table, fitting the fully-executable anchor.	5 / 5
Workflow Clarity	The connection flow has a clear sequence with state-based checkpoints and a feedback loop (poll, handle CLIENT_ACTION_REQUIRED, poll again until READY), but "skip to Step 2" and "1b" references have no matching Step 1/Step 2 headers, leaving navigation slightly broken.	4 / 5
Progressive Disclosure	With no bundle files present, the single ~140-line file is organized into clear, well-labeled sections with one external docs link; minor gaps are the bare unexplained entity list in the Overview and the lack of any split reference material.	4 / 5
	Total	16 / 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 is well-structured with an explicit "Use when" trigger and a distinct, named-platform niche, but its capability list is generic ("manage data, records, automate workflows") rather than concrete to Weavr's financial-services surface area. It scores solidly on distinctiveness and completeness but mid-range on specificity and trigger coverage.

Suggestions

Replace generic verbs with concrete Weavr capabilities, e.g. "Create and manage Weavr end-users, accounts, and cards; initiate payments; automate onboarding journeys and workflows."

Add natural trigger phrases users would actually say, such as "Use when the user wants to manage Weavr end-users or accounts, issue cards, send or receive payments, or automate Weavr onboarding journeys."

Mention key Weavr nouns users may reference (end-users, accounts, cards, payments, journeys, passkeys) so the skill triggers on those terms too.

Dimension	Reasoning	Score
Specificity	Names the Weavr.io domain plus a few actions ("Manage data, records, and automate workflows"), but the actions are generic rather than concrete Weavr-specific capabilities such as banking or payments, so it is not comprehensive enough for a 4.	3 / 5
Completeness	It states both a "what" ("Manage data, records, and automate workflows") and an explicit "Use when the user wants to interact with Weavr.io data" trigger, but the "what" is generic rather than concrete, keeping it below a 5.	4 / 5
Trigger Term Quality	The natural trigger is essentially limited to "Weavr.io" and "interact with Weavr.io data"; relevant but missing common variations or synonyms, which fits anchor 3 rather than the broader coverage of a 4.	3 / 5
Distinctiveness Conflict Risk	Anchored to a named platform (Weavr.io) with a distinct trigger phrase, giving it a clear niche with minimal conflict risk against other skills.	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/weavr/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.