Name: weclapp
Rating: 51.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

weclapp

Weclapp integration. Manage Organizations. Use when the user wants to interact with Weclapp data.

Quality

56%

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

Quality

Content

46%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 CLI-driven operational guidance is concrete and well-sequenced, but the document is dominated by a massive, largely spurious enumeration of entities and generic verbs that wastes tokens and adds no actionable value. Validation for destructive operations is also missing.

Suggestions

Remove the giant entity/verb list (lines 21-313) or move genuine Weclapp entities into a separate reference file; the generic verb list ('Like', 'Zoom In', etc.) should be deleted entirely.

Add explicit validation/verification steps for destructive and batch operations (e.g., verify a created sales order by re-fetching it, confirm before proxy DELETE calls).

Replace the vague 'Use action names and parameters as needed' with a concrete example of mapping a user request to an action via `membrane action list`.

Dimension	Reasoning	Score
Conciseness	Roughly 290 lines enumerate entity names and ~140 generic verbs ('Like', 'Bookmark', 'Zoom In') that Claude already knows and that are not real Weclapp actions, making the file noticeably padded despite the efficient CLI sections.	2 / 5
Actionability	The operational sections give concrete, executable commands (install, login, connection ensure, action list/run, request) with real flags and a useful popular-actions table, with only minor gaps such as the vague 'Use action names and parameters as needed'.	4 / 5
Workflow Clarity	The connection workflow is well-sequenced with state checks and polling feedback, but destructive/batch operations (create/delete via actions, proxy DELETE) have no validation or verification checkpoints, capping this dimension at 3.	3 / 5
Progressive Disclosure	The ~290-line entity/verb enumeration is inlined content that clearly belongs in a separate reference file (or should be removed), and there are no external references or clear signaling to offload it.	2 / 5
	Total	11 / 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 distinct and answers both what and when, but it is thin on concrete capabilities and trigger-term coverage. 'Manage Organizations' is generic and not even aligned with the entities listed in the body.

Suggestions

Replace the generic 'Manage Organizations' with 2-3 concrete capabilities drawn from the body (e.g., 'List and create sales orders, invoices, articles, and parties').

Broaden trigger terms beyond 'Weclapp data' to natural phrases like 'Weclapp ERP', 'Weclapp CRM', or specific entities users mention.

Tighten the 'when' clause to concrete triggers (e.g., 'Use when the user wants to query or create Weclapp sales orders, invoices, contacts, or articles').

Dimension	Reasoning	Score
Specificity	It names the domain ('Weclapp integration') and one concrete action ('Manage Organizations'), but offers only a single generic action and no broader coverage of the ERP entities the skill actually handles.	3 / 5
Completeness	Both a 'what' ('Weclapp integration. Manage Organizations.') and an explicit 'when' ('Use when the user wants to interact with Weclapp data') are present, though the 'when' could be more specific.	4 / 5
Trigger Term Quality	'Weclapp' and 'Weclapp data' are relevant natural keywords, but coverage is thin with no synonyms or related terms a user might naturally say.	3 / 5
Distinctiveness Conflict Risk	The branded term 'Weclapp' carves a clear niche with minimal overlap 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/weclapp/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.