Name: weweb
Rating: 59.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

weweb

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

Quality

68%

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/weweb/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 concrete, executable Membrane CLI commands and a clear connection workflow with state checkpoints and a feedback loop. It loses points for an unnecessary intro paragraph and some inlined detail that could be split into references.

Suggestions

Trim the opening paragraph explaining what WeWeb is and remove filler like 'so you can focus on the integration logic rather than auth plumbing'.

Label the workflow steps explicitly (e.g. 'Step 1: Connect', 'Step 2: Discover and run actions') so the 'skip to Step 2' references resolve clearly.

Consider moving the detailed connection-state handling and proxy flag table into a reference file linked from the overview to reduce inline length.

Dimension	Reasoning	Score
Conciseness	Mostly command-focused and efficient, but it opens by explaining what WeWeb is ('no-code front end development platform... used by marketers, designers, and entrepreneurs') and includes filler like 'so you can focus on the integration logic rather than auth plumbing', matching the 'mostly efficient but includes some unnecessary explanation' anchor.	3 / 5
Actionability	It provides copy-paste-ready, executable commands across install, login, connection ensure, polling, action list/run with JSON input, and a proxy flag table, covering the common cases comprehensively as in the 'fully executable; copy-paste ready' anchor.	5 / 5
Workflow Clarity	The connection flow is sequenced with state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a feedback loop ('poll again after the user completes the action'), but 'skip to Step 2' references an unlabeled step, leaving minor gaps consistent with 'clear sequence with most checkpoints present'.	4 / 5
Progressive Disclosure	Content is well-organized into clear sections with no nested references and no bundle files, but the detailed connection-state handling and proxy flag table are inlined in a ~155-line body rather than split into one-level-deep reference files, fitting 'good structure; minor organization gaps'.	4 / 5
	Total	16 / 20 Passed

Description

62%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 short, in third person, and includes both a 'what' and a 'Use when' clause anchored to a distinct product name. Its main weakness is generic action verbs and limited trigger-term variation rather than concrete, comprehensive capabilities.

Suggestions

Replace generic verbs with concrete actions, e.g. 'Manage WeWeb collections, variables, workflows, and elements; run and automate workflow actions'.

Expand the trigger clause with natural phrasings users would say, e.g. 'Use when the user wants to manage WeWeb collections, elements, variables, or automate WeWeb workflows'.

Mention key resource nouns (collections, elements, workflows) that distinguish this skill from generic data-integration skills.

Dimension	Reasoning	Score
Specificity	Names the WeWeb domain and a few action areas ('Manage data, records, and automate workflows'), but the verbs are generic rather than concrete; not comprehensive, matching the 'names domain and 1-2 concrete actions' anchor.	3 / 5
Completeness	It states both what ('WeWeb integration. Manage data, records, and automate workflows') and when ('Use when the user wants to interact with WeWeb data'); the 'when' is explicit but could be more specific, matching the 'has both what and when' anchor rather than the fully concrete level 5.	4 / 5
Trigger Term Quality	The trigger relies essentially on the single keyword 'WeWeb' in 'interact with WeWeb data'; relevant but missing common variations or synonyms, fitting the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The named product 'WeWeb' gives it a clear, distinct niche with minimal conflict risk, but the generic action phrasing ('manage data, records, automate workflows') leaves minor overlap with other data-handling skills, fitting 'mostly distinct; minor overlap risk'.	4 / 5
	Total	14 / 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/weweb/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.