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

Blog Docs Log in Get started

gupshup

Gupshup integration. Manage Users, Organizations. Use when the user wants to interact with Gupshup 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/gupshup/SKILL.md

Quality

Content

72%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 is highly actionable with complete, executable CLI commands and a well-sequenced connection flow, but it is a monolithic single file with inlined reference tables and lacks validation/verification steps for the destructive and batch action operations it supports.

Suggestions

Add a validation/verification checkpoint to the action-running workflow, e.g. re-fetching or inspecting the `output` field to confirm destructive operations (delete-subscription, send-message) succeeded before proceeding.

Move the 15-row Popular actions table and the proxy-flags table into a separate `references/actions.md` file, keeping SKILL.md a concise overview with a clearly signaled one-level-deep reference.

Trim the filler 'Use action names and parameters as needed.' line and tighten the opening overview sentence to remove marketing-style padding.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands and tables, but contains minor trimmable padding such as the marketing-style overview sentence and the filler line 'Use action names and parameters as needed.'	4 / 5
Actionability	Provides fully executable, copy-paste-ready bash commands across the common cases (install, login, connection ensure, action list/run with JSON input, proxy) plus concrete action keys and flag tables.	5 / 5
Workflow Clarity	The connection sub-workflow has explicit state checkpoints and a poll-retry loop, but the core action-running workflow (covering destructive/batch operations like delete-subscription and send-message) lacks any validation or verification step, which caps the score at 3 per the destructive-operations guideline.	3 / 5
Progressive Disclosure	The skill is a single monolithic ~160-line file with reference-style content (a 15-row popular-actions table and a proxy-flags table) inlined that could appropriately live in a separate references file, with no one-level-deep navigation to deeper material.	3 / 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 clearly named, distinctive product, but the capability list is thin (only two actions) and the trigger phrase is generic rather than rich with natural synonyms.

Suggestions

Expand the capability list beyond 'Manage Users, Organizations' to mention concrete messaging actions (send messages, templates, bot flows) that the skill actually supports.

Replace the generic 'interact with Gupshup data' trigger with concrete trigger phrases users would say, e.g. 'Use when the user wants to send WhatsApp/SMS messages, manage Gupshup templates or bots, or work with Gupshup messaging data.'

Dimension	Reasoning	Score
Specificity	Names the domain (Gupshup) and exactly two concrete entity-management actions ('Manage Users, Organizations'), matching the anchor for 1-2 concrete actions without comprehensive coverage.	3 / 5
Completeness	Both a 'what' ('Gupshup integration. Manage Users, Organizations.') and an explicit 'when' ('Use when the user wants to interact with Gupshup data.') are present, though the trigger could be more concrete and specific.	4 / 5
Trigger Term Quality	The proper-noun keyword 'Gupshup' plus the 'Use when the user wants to interact with Gupshup data' clause provide a relevant natural term, but no synonyms or related user-facing terms (WhatsApp, SMS, messaging, templates) are present.	3 / 5
Distinctiveness Conflict Risk	The named product 'Gupshup' is a distinct niche unlikely to trigger the wrong skill, but the broad 'interact with Gupshup data' trigger keeps it from minimal conflict risk.	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/gupshup/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.