Name: clevertap
Rating: 60.8 (1 reviews)
Author: membranedev

clevertap

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

Quality

71%

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/clevertap/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 body is a well-structured, largely executable CLI guide with clear connection-state handling, but it lists destructive and batch actions without validation or confirmation steps, which caps workflow clarity. Conciseness and actionability are strong with only minor trim and example gaps.

Suggestions

Add a validation/confirmation checkpoint before destructive and batch actions, e.g. require a dry-run or explicit user confirmation before 'delete-user-profile', 'stop-campaign', and bulk 'upload-events'/'upload-user-profiles', and verify counts afterward.

Include one end-to-end example that runs a specific popular action (e.g. get-campaign-report) with a real --input payload so the run pattern is demonstrated concretely rather than with a placeholder key/value.

Trim narrative padding such as 'so you can focus on the integration logic rather than auth plumbing' and tighten the CleverTap overview paragraph to assume Claude's familiarity.

Dimension	Reasoning	Score
Conciseness	The body is mostly executable commands, a compact actions table, and flag references with only minor prose padding (e.g. 'so you can focus on the integration logic rather than auth plumbing'), fitting the efficient-but-slightly-trimmable score-4 anchor better than the lean score-5 anchor.	4 / 5
Actionability	It provides copy-paste-ready commands for login, connection, action list/run, and proxy requests plus a table of real action keys, but no end-to-end example runs a specific popular action with a real input payload, leaving a minor gap versus the fully-covered score-5 anchor.	4 / 5
Workflow Clarity	The connection flow is well sequenced with state checks (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a poll-after-action loop, but the skill exposes destructive and batch operations (Delete User Profile, Stop Campaign, bulk Upload Events/Profiles) with no validation or confirmation steps, which caps workflow clarity at 3 per the rubric.	3 / 5
Progressive Disclosure	No bundle files exist, so scoring rests on the single-file body, which is well-organized with clear section headers and navigation across ~170 lines; the inline actions table and proxy flag reference are borderline inline reference content, keeping it at score 4 rather than the cleanly-split score-5 anchor.	4 / 5
	Total	15 / 20 Passed

Description

73%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 a distinct CleverTap niche with an explicit 'Use when' trigger, but the capability list ('manage data, records') is generic and the trigger phrase is single rather than enumerating concrete use cases. It is a solid, above-midpoint description with room to be more specific.

Suggestions

Replace the generic 'Manage data, records, and automate workflows' with concrete actions such as 'query campaigns, fetch user profiles and events, upload device tokens, and stop scheduled campaigns'.

Expand the 'Use when' clause to list concrete triggers, e.g. 'Use when the user wants to query or manage CleverTap campaigns, user profiles, events, segments, or run bulk uploads'.

Add the channel/feature nouns from the body (campaigns, push, email, SMS, WhatsApp, segments) so the natural trigger terms align with how users actually phrase requests.

Dimension	Reasoning	Score
Specificity	Names the domain ('CleverTap integration') and a couple of actions ('Manage data, records, and automate workflows'), but 'manage data/records' is generic rather than concrete, matching the score-3 anchor of domain plus 1-2 non-comprehensive actions.	3 / 5
Completeness	It explicitly answers both 'what' ('Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with CleverTap data'), but the 'when' is a single trigger phrase that could be more specific, matching score 4 rather than the multi-trigger score-5 anchor.	4 / 5
Trigger Term Quality	Good keyword coverage with the product name plus natural nouns ('CleverTap', 'data', 'records', 'workflows', 'interact with CleverTap data'); a few natural variations users might say (campaigns, profiles, events, segments) are missing, so it sits below the comprehensive score-5 anchor.	4 / 5
Distinctiveness Conflict Risk	'CleverTap integration' pins a clear, named-product niche with a distinct trigger ('interact with CleverTap data') and minimal overlap risk with other skills, matching the score-5 anchor.	5 / 5
	Total	16 / 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/clevertap/SKILL.md
Commit: f484c82

Reviewed: ~10 hours 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.