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

request

Request integration. Manage data, records, and automate workflows. Use when the user wants to interact with Request 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/request/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 content is a solid, actionable CLI guide with a well-sequenced connection workflow and validation checkpoints. Its main weaknesses are some padded/marketing prose, a stray non-instructional line, and a broken 'Step 2' cross-reference.

Suggestions

Remove the stray line 'I don't have enough information about the app to fulfill your request.' and tighten the marketing-style sentence about Membrane handling auth so it states the fact without the editorial framing.

Label the 'Searching for actions' section as 'Step 2' (or remove the 'skip to Step 2' references) so the cross-references resolve.

Move the full proxy flag table into a separate reference file and keep only the common case inline, improving token efficiency at load time.

Dimension	Reasoning	Score
Conciseness	The body is mostly concrete commands, but it includes padded prose ('Membrane handles authentication... so you can focus on the integration logic rather than auth plumbing') and a stray junk line ('I don't have enough information about the app to fulfill your request.').	3 / 5
Actionability	It provides concrete, runnable commands throughout (install, login, connection ensure, action list/run, proxy with a flags table), with only minor placeholders like CONNECTION_ID that the user must fill.	4 / 5
Workflow Clarity	The connection flow has a clear sequence with explicit state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a poll-again feedback loop, but a referenced 'Step 2' is not actually labeled in the body.	4 / 5
Progressive Disclosure	No bundle files exist, so the single SKILL.md carries everything; it is well-organized into headed sections (Overview, Connecting, Searching, Popular actions, Best practices), appropriate for a CLI usage skill, with minor room to split reference detail.	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 covers both what and when with a clear trigger tied to the Request app, but the capability list is generic ('Manage data, records, automate workflows') and trigger-term coverage is narrow. Tightening the action list and adding synonyms would lift it.

Suggestions

Replace the generic 'Manage data, records, and automate workflows' with concrete Request-specific actions (e.g., 'list, create, and update Request records; manage participants and comments').

Add natural trigger synonyms and entity names beyond 'Request data' (e.g., 'Request records', 'Request participants', 'Request comments') so users phrasing it differently still match.

Dimension	Reasoning	Score
Specificity	The description names the domain (Request) and a couple of actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete; it does not reach the 'several specific actions' bar of 4.	3 / 5
Completeness	It answers both 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Request data'), though the 'what' is somewhat generic.	4 / 5
Trigger Term Quality	It includes the natural phrase 'interact with Request data', but coverage is thin — only the app name 'Request' plus 'data' with no synonyms or common variations users would naturally say.	3 / 5
Distinctiveness Conflict Risk	'Request' is a named product with a distinct trigger ('interact with Request data'), giving mostly distinct coverage with minor overlap risk from the generic 'Manage data, records' phrasing.	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/request/SKILL.md
Commit: f484c82

Reviewed: 5 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.