CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

awesome-support

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

Quality

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/awesome-support/SKILL.md
SKILL.md
Quality
Evals
Security

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.

A solid, executable guide with concrete commands, a sensible connection-readiness state machine, and good feedback loops. Main weaknesses are duplicated/verbose passages, a 'Popular actions' section that promises but does not deliver, and a dangling 'Step 2' reference that slightly breaks the workflow narrative.

Suggestions

Remove the padding ('Use action names and parameters as needed', the user-persona intro sentence, the awkward Agent Types sentence) and deduplicate the 'action list' command between 'Searching for actions' and 'Popular actions', replacing the latter with actual commonly-used actions for tickets, replies, and customers.

Fix the broken navigation: define Step 1/Step 2 explicitly or replace 'skip to **Step 2**' with the actual section name ('Searching for actions').

Standardize CLI invocation (the doc mixes 'membrane ...' and 'npx @membranehq/cli@latest ...') and add one complete worked example, e.g., searching for and running a ticket-creation action with realistic input and expected output fields.

DimensionReasoningScore

Conciseness

Mostly efficient command-driven prose, but it carries unnecessary padding: the intro paragraph about who uses the plugin, the filler line 'Use action names and parameters as needed', and a duplicated 'action list' command under both 'Searching for actions' and 'Popular actions'. The 'Agent Types' sentence is also awkwardly explained.

3 / 5

Actionability

Concrete, copy-paste-ready CLI commands cover install, login (including headless completion), connection ensure, readiness polling, action search/run with --input, and proxy usage with a flags table. Not a 5 because there is no worked example with a real action (e.g., an actual ticket query) and the 'Popular actions' section lists no actions, only repeating the discovery command.

4 / 5

Workflow Clarity

A clear sequence (install → login → connect → poll → discover → run → proxy fallback) with explicit state-machine checkpoints (READY, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) and a re-poll feedback loop after user actions. Not a 5 because 'skip to **Step 2**' references a step that is never defined (steps are unlabeled or '1b'), and there is no verification of action run results.

4 / 5

Progressive Disclosure

A single self-contained file with well-organized sections and no nested or buried references; no bundle files exist. Not a 5 because at ~140 lines the generic Membrane auth/connection machinery (roughly half the document) could be split into a shared reference file, keeping SKILL.md focused on Awesome Support specifics.

4 / 5

Total

15

/

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.

A middling description: it has an explicit 'Use when...' trigger and a distinctive product name, but the capability statement is generic ('manage data, records, and automate workflows') and it omits the domain vocabulary users would naturally say. Naming the actual entities and operations (tickets, replies, customers, help desk) would lift both specificity and trigger quality.

Suggestions

Replace 'Manage data, records, and automate workflows' with concrete capabilities, e.g., 'Create and reply to support tickets, manage customers, and automate help desk workflows in the Awesome Support WordPress plugin'.

Add natural trigger vocabulary users would say: tickets, help desk, support requests, WordPress support plugin — e.g., 'Use when the user mentions Awesome Support, support tickets, or their WordPress help desk'.

DimensionReasoningScore

Specificity

'Manage data, records, and automate workflows' names the domain but the actions are minimal or generic — no concrete operations like creating tickets, replying to customers, or managing support requests appear. Not a 3 because none of the stated actions is concrete in the way 'extracts content' is.

2 / 5

Completeness

Both halves are present: the what ('Manage data, records, and automate workflows') and an explicit when ('Use when the user wants to interact with Awesome Support data'). Not a 5 because the what is generic and the when is narrow and slightly circular, without concrete trigger phrases.

4 / 5

Trigger Term Quality

'Awesome Support' is a strong, specific product keyword, but the natural phrases a user would actually say — tickets, help desk, support requests, WordPress — are all missing. Not a 4 because keyword coverage beyond the product name is essentially absent.

3 / 5

Distinctiveness Conflict Risk

The product name 'Awesome Support' carves out a clear niche with minimal conflict risk. Not a 5 because the generic action phrasing ('manage data, records, automate workflows') overlaps with virtually any data-integration skill if the product name is absent from the user's request.

4 / 5

Total

13

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

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

Reviewed

Table of Contents

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.