Name: wuf
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

wuf

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

Quality

66%

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/wuf/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 an efficient, highly actionable integration guide with concrete Membrane CLI commands and a clear connection-state workflow including a feedback loop, weakened only by minor marketing padding, placeholder-dependent commands, broken step numbering, and a slightly redundant actions section.

Suggestions

Fix the broken step numbering: label the connect step '1a', make '1b' consistent, and replace 'skip to Step 2' with a labeled anchor such as 'skip to Searching for actions'.

Trim marketing fluff such as 'so you can focus on the integration logic rather than auth plumbing' and 'This is the fastest way to get a connection' to improve token efficiency.

Add a brief validation note before running actions that may mutate Wuf data (e.g. confirm the action is non-destructive or re-read the record after running), and merge 'Popular actions' into 'Searching for actions' to remove redundancy.

Dimension	Reasoning	Score
Conciseness	The body is lean and command-driven with no over-explanation of concepts Claude already knows, but it carries a few marketing phrases ('so you can focus on the integration logic rather than auth plumbing', 'This is the fastest way to get a connection', 'burn less tokens') that are minor instances of over-explanation trimming could remove, fitting the efficient-with-minor-padding anchor.	4 / 5
Actionability	It provides many real, executable commands (install, login, connection ensure/get, action list/run, request proxy) with a flags table, but commands rely on placeholders (CONNECTION_ID, QUERY, <id>, <actionId>, <agentType>) the user must substitute, leaving minor gaps that keep it just short of fully copy-paste-ready.	4 / 5
Workflow Clarity	The install→auth→connect→poll→search→run sequence is clear and includes an explicit state-based feedback loop (CLIENT_ACTION_REQUIRED → user acts → re-poll), but the 'skip to Step 2' reference points to an unlabeled step, '1b' has no '1a', and the action-running step lacks validation, so it is clear-with-most-checkpoints rather than fully validated.	4 / 5
Progressive Disclosure	No bundle files exist; the single SKILL.md is well-organized with clear section headers and content appropriately placed inline (overview, CLI setup, connection states, actions, proxy, best practices), with only minor organization gaps such as the redundant 'Popular actions' section echoing 'Searching for actions'.	4 / 5
	Total	16 / 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 correctly pairs a what-statement with an explicit 'Use when…' trigger and leverages a distinct brand name, but its capability verbs are generic ('Manage data, records, automate workflows') and trigger terms are limited to the brand name with no synonyms.

Suggestions

Replace generic verbs with concrete Wuf actions, e.g. 'Create and update pet and vet profiles, book walkers and sitters, and automate pet-care workflows.'

Broaden trigger terms beyond the brand name, e.g. 'Use when the user wants to manage pet profiles, vet records, or bookings in Wuf.'

Make the 'when' clause more specific by listing the concrete entities (pets, vets, bookings) users will mention.

Dimension	Reasoning	Score
Specificity	The description names the Wuf domain but its actions ('Manage data, records, and automate workflows') are minimal and generic rather than concrete, matching the 'names the domain but actions are minimal or generic' anchor rather than the 1-2 concrete actions of a 3.	2 / 5
Completeness	It states a 'what' (Wuf integration managing data/records/workflows) and an explicit 'Use when the user wants to interact with Wuf data' trigger, satisfying both, but the 'when' is generic and the 'what' is vague, so it is not the explicit-and-concrete level 5.	4 / 5
Trigger Term Quality	The natural keywords are essentially 'Wuf' and 'Wuf data' — relevant but narrow, missing common variations or synonyms a user might say, which fits the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The 'Wuf' brand name carves a clear niche with minimal conflict risk, but the surrounding verbs (manage data, automate workflows) are generic and could overlap with other data-management skills if the brand name were absent, so it is mostly-distinct rather than fully distinct.	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/wuf/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.