Name: wso2
Rating: 61.6 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

wso2

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

Quality

72%

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

Quality

Content

82%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 content is a lean, executable guide to driving WSO2 through the Membrane CLI with concrete commands and a clear connection workflow; main gaps are minor verbosity in the intro and the lack of explicit validation steps for proxy/action results.

Suggestions

Trim the opening descriptive paragraph ('WSO2 provides API management... Developers use WSO2...') since Claude already knows what WSO2 is, keeping the official docs link.

Add an explicit validation step after running actions or proxy requests, e.g. check the `--json` response for an `error`/non-2xx status before proceeding.

Remove or repurpose the 'WSO2 Overview' bullet list (APIs, API Manager, Applications, Users, Roles) — it is not navigational and adds tokens without actionable value.

Dimension	Reasoning	Score
Conciseness	The body is largely efficient: command snippets and a compact options table carry most of the weight, with only minor over-explanation (e.g. the opening WSO2 marketing paragraph and the Membrane auth rationale) that could be trimmed.	4 / 5
Actionability	Guidance is fully executable: copy-paste CLI commands for install, login, connection ensure, polling, action list/run, and proxy requests, plus a concrete options table and JSON input examples covering the common cases.	5 / 5
Workflow Clarity	The connection flow is clearly sequenced with a feedback loop (ensure -> wait/poll -> handle CLIENT_ACTION_REQUIRED -> re-poll until READY), and state outcomes are enumerated; however proxy/action operations lack explicit validation checkpoints against the returned JSON.	4 / 5
Progressive Disclosure	Structure is good with clear sections (Install, Authentication, Connecting, Searching, Popular actions, Proxy, Best practices) and no bundle files exist to split out; the inline proxy options table is appropriate, though the 'WSO2 Overview' bullet list adds little navigational value.	4 / 5
	Total	17 / 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 reasonably specific and clearly names the WSO2 niche with an explicit Use-when clause, but its action verbs are generic and it omits natural trigger synonyms (APIs, integration, identity) that users would actually say.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete WSO2 capabilities such as 'Manage APIs, applications, users, and roles' to lift specificity.

Expand the Use-when clause with natural trigger phrases users say, e.g. 'Use when the user wants to manage WSO2 APIs, applications, users, roles, or integrate systems via WSO2'.

Add common synonyms/file types a user might mention (API Manager, integrations, identity and access management) to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (WSO2) and two concrete action classes ('Manage data, records, and automate workflows') but the actions are generic (manage, automate) rather than enumerated, leaving coverage non-comprehensive.	3 / 5
Completeness	It states the 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with WSO2 data'), satisfying both, though the when-clause is fairly generic rather than tied to concrete triggers.	4 / 5
Trigger Term Quality	'WSO2' and 'data, records, workflows' are relevant keywords, but common natural synonyms a user would actually say (APIs, integrations, identity) are missing, so keyword coverage is partial.	3 / 5
Distinctiveness Conflict Risk	The WSO2 niche is distinct and the trigger is product-named, so conflict risk is low; only minor overlap risk remains because the underlying action verbs (manage data, automate workflows) are broad.	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/wso2/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.