Name: coupontools
Rating: 58.4 (1 reviews)
Author: membranedev

coupontools

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

Quality

67%

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

Quality

Content

68%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 highly actionable with concrete Membrane commands and a useful action catalog, and it is well structured for navigation. Its main gaps are marketing-fluff padding and the absence of verification steps after running state-changing actions.

Suggestions

Trim the opening paragraph and the feature bullet list to the essentials Claude needs to act, removing the marketing framing about who uses Coupontools.

Add a verification checkpoint after running actions, e.g. re-fetch the resource (get-coupon / get-coupon-session) or inspect the response `output` to confirm the change took effect before reporting success.

Move the Popular actions table and proxy flag reference into a separate reference file linked from the body to reduce inline weight and improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-driven and efficient, but the opening marketing paragraph ("used by marketers and businesses looking to engage customers and drive sales through gamified promotions") and the long feature bullet list pad the skill with content Claude does not need.	3 / 5
Actionability	Copy-paste-ready commands are given throughout (install, login, connection ensure, action list/run, request) with real flags and a Popular actions table of concrete action keys, fully covering the common cases.	5 / 5
Workflow Clarity	The connect-then-poll-then-act sequence is clear and the connection setup has feedback loops, but running state-changing actions (create users, send coupons, void/update sessions) lacks any validation or verification of the outcome, so the destructive/batch cap holds at 3.	3 / 5
Progressive Disclosure	No bundle files exist and all content lives in one file, but it is well organized into clearly headed sections (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices) with no nested references, fitting the 4 anchor.	4 / 5
	Total	15 / 20 Passed

Description

66%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 successfully pairs a what/when structure around a specific named platform, giving it strong distinctiveness. Its weakness is generic action verbs and a thin trigger vocabulary that miss the natural coupon/loyalty terms users would actually say.

Suggestions

Replace generic verbs with concrete Coupontools actions, e.g. "Create and send digital coupons, run contests and loyalty programs, and manage directory users."

Expand the trigger clause with natural phrases: "Use when the user wants to create coupons, run contests or instant-win campaigns, manage loyalty cards, or send coupons by email/SMS."

Mention the data types users interact with (coupons, sessions, directories, loyalty cards) to sharpen specificity.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Coupontools domain and lists a few actions, but the verbs ("manage", "automate") are generic rather than concrete coupon-specific operations, so it sits at the 3 anchor rather than 4.	3 / 5
Completeness	Both a "what" ("Manage data, records, and automate workflows") and a "when" ("Use when the user wants to interact with Coupontools data") are present and explicit, but the "when" clause is generic rather than tied to concrete trigger phrases, matching the 4 anchor.	4 / 5
Trigger Term Quality	The trigger "Use when the user wants to interact with Coupontools data" relies almost entirely on the platform name; it omits the natural terms users would say (coupons, contests, loyalty programs, vouchers), so coverage is partial.	3 / 5
Distinctiveness Conflict Risk	Naming a specific commercial platform (Coupontools) and tying the trigger to it gives the skill a clear niche with minimal overlap risk against other skills.	5 / 5
	Total	15 / 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/coupontools/SKILL.md
Commit: f484c82

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