Name: webexpenses
Rating: 56.8 (1 reviews)
Author: membranedev

webexpenses

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

Quality

65%

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

Quality

Content

67%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 delivers mostly executable, well-structured CLI guidance with a clear connection-state workflow, but it carries some redundant and marketing-style prose and lacks an explicit validation checkpoint for action-run workflows.

Suggestions

Remove the opening marketing paragraph about what Webexpenses is; Claude does not need the product pitch, and the official-docs link already covers context.

De-duplicate the action-discovery command (it appears under 'Searching for actions' and again under 'Popular actions') into a single canonical example.

Add an explicit validation/inspection step after `membrane action run` (e.g. check the `output` field and error states) to give the action workflow a feedback checkpoint.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with command examples that earn their place, but it opens with marketing-style explanation of what Webexpenses is and repeats the action-discovery command in two sections, which could be trimmed.	3 / 5
Actionability	Concrete, executable CLI commands with flags are provided throughout (install, login, connection ensure, action list/run, request), covering the common cases with minor gaps such as placeholder CONNECTION_ID handling.	4 / 5
Workflow Clarity	The connection setup is clearly sequenced with state-based branching (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a polling loop, though it lacks an explicit validate-after-action feedback checkpoint for destructive runs.	4 / 5
Progressive Disclosure	Content is well-organized into clear sections (install, auth, connecting, searching, popular actions, proxy, best practices) with no bundle files needed; minor gaps are the duplicated discovery command and no separate reference file for the proxy flag table.	4 / 5
	Total	15 / 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 identifies the product and includes an explicit use-trigger, but its capabilities are stated generically ('Manage data, records, and automate workflows') and it lacks the natural expense-domain vocabulary users would actually say.

Suggestions

Replace generic actions with concrete expense-domain verbs, e.g. 'Submit, approve, and reimburse employee expenses; manage expense reports and receipts.'

Add natural trigger phrases users would say, such as 'expenses', 'expense reports', 'receipts', or 'reimbursements'.

Make the 'Use when' clause more specific, e.g. 'Use when the user wants to submit, approve, or query Webexpenses expense reports.'

Dimension	Reasoning	Score
Specificity	The description names the domain and a couple of concrete actions ('Manage data, records, and automate workflows') but the actions are generic and not comprehensive for an expense-management product.	3 / 5
Completeness	It states what the skill does and includes an explicit 'Use when the user wants to interact with Webexpenses data' trigger, though the 'when' clause is broad rather than concrete.	4 / 5
Trigger Term Quality	'Webexpenses data' is a relevant keyword, but common natural phrases a user would say ('expenses', 'expense reports', 'reimbursements', 'receipts') and file-type triggers are missing.	3 / 5
Distinctiveness Conflict Risk	The named product 'Webexpenses' gives it a clear niche distinct from generic skills, with only minor overlap risk against other integration skills.	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/webexpenses/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.