Name: awesome-support
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

awesome-support

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

Quality

61%

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

Quality

Content

61%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 well-structured, actionable CLI integration guide with strong connection-state handling, but it carries mild marketing padding and critically lacks validation guidance for destructive action/proxy operations.

Suggestions

Add an explicit validation/verification step before destructive actions and proxy writes (e.g., confirm the target record, dry-run GET before POST/PUT/DELETE, check the response status field).

Trim marketing phrasing ("so you can focus on the integration logic rather than auth plumbing", "This is the fastest way") and deduplicate the action-list command between "Searching for actions" and "Popular actions."

Move the full clientAction object schema and the proxy flag reference into a separate reference file referenced one level deep to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with command blocks and a flag table that earn their place, but it includes marketing padding ("so you can focus on the integration logic rather than auth plumbing", "This is the fastest way to get a connection") and repeats the action-list command across "Searching for actions" and "Popular actions," fitting the 3 anchor.	3 / 5
Actionability	It provides concrete, executable CLI commands for install, login, connection, action search/run, and proxy requests with a full flag table, but placeholders (CONNECTION_ID, QUERY, <actionId>) and the absence of example output values leave minor gaps versus copy-paste-ready 5.	4 / 5
Workflow Clarity	The connection flow has explicit state checks and poll-until-ready feedback loops, but running actions and proxy requests can be destructive (POST/PUT/PATCH/DELETE) and lack any validation/verification checkpoint before execution, which caps workflow clarity at 3 per the destructive-operation rule.	3 / 5
Progressive Disclosure	The body is well-organized with clear ##/### section headers and a navigable structure; with no bundle files present it stays a single file, but reference-like material (the full clientAction schema and proxy flag table) is inlined rather than split out, holding it at 4 rather than 5.	4 / 5
	Total	14 / 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 cleanly states what the skill does and when to use it with a distinct product trigger, but the action vocabulary is generic and it misses the natural ticket/support terms a user would say.

Suggestions

Replace generic verbs with concrete Awesome Support actions, e.g. "Manage tickets, replies, and customers; search and run actions; automate support workflows."

Add natural trigger phrases to the when clause: "Use when the user wants to manage support tickets, replies, or customer records in Awesome Support."

Reference the WordPress/help-desk context to sharpen distinctiveness from generic CRM or data skills.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names 2-3 actions but the objects ("data", "records", "workflows") are generic rather than concrete like tickets or replies, so it sits at the 3 anchor rather than 4.	3 / 5
Completeness	It answers both "what" (manage data/records, automate workflows) and "when" ("Use when the user wants to interact with Awesome Support data"), but the when clause is generic rather than enumerating concrete trigger phrases, which is the 4 rather than 5 anchor.	4 / 5
Trigger Term Quality	The trigger "interact with Awesome Support data" surfaces the app name and "data" but omits the natural terms users would actually say (tickets, replies, support requests, help desk), matching the 3 anchor's "some relevant keywords but missing common variations."	3 / 5
Distinctiveness Conflict Risk	Naming the specific product "Awesome Support" gives a clear niche with minimal conflict risk, but the generic action verbs leave minor overlap with adjacent CRM/support skills, fitting 4 rather than a clean 5.	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/awesome-support/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.