Name: cometly
Rating: 62.4 (1 reviews)
Author: membranedev

cometly

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

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/cometly/SKILL.md

Quality

Content

82%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 copy-paste commands and explicit state-handling feedback loops for connection setup, and is well-organized into clear sections. Its weaknesses are minor: a little explanatory padding and ambiguous step numbering ('Step 2', '1b') that slightly muddies the workflow sequence.

Suggestions

Replace the dangling 'skip to Step 2' reference and lone '1b' heading with an explicit numbered sequence (1. Install, 2. Authenticate, 3. Connect, 4. Search actions, 5. Run) so the workflow is unambiguous.

Trim padding like 'so you can focus on the integration logic rather than auth plumbing' to tighten token efficiency.

Consider moving the popular-actions and proxy-flag tables into a reference file (e.g. ACTIONS.md) referenced from the overview to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean — concrete commands and tables dominate — with only minor padding such as 'so you can focus on the integration logic rather than auth plumbing' and a brief product-description paragraph, fitting the 'efficient; minor instances of over-explanation that could be trimmed' anchor rather than the every-token-earns-its-place bar of a 5.	4 / 5
Actionability	It provides fully executable, copy-paste-ready commands for every common case (install, login, connection ensure/get with --wait, action list/run, request proxy) plus flag tables and a popular-actions table with real keys, matching the 'fully executable; copy-paste ready; specific examples cover the common cases' anchor.	5 / 5
Workflow Clarity	The connection flow has a clear sequence with explicit state-based validation and feedback loops (poll until READY, handle CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR), but step references are ambiguous ('skip to Step 2' with no labeled Step 2, a lone '1b' heading), so it sits at 'clear sequence with most checkpoints present; minor validation gaps' rather than the fully numbered, checklist-driven 5.	4 / 5
Progressive Disclosure	No bundle files exist, so the skill is a single well-sectioned file with clearly labeled headers and inline tables; structure is good and content is appropriately placed, matching the 'good structure; most content appropriately placed; minor organization gaps' anchor — it is not a 5 because there are no one-level-deep references to signal and the popular-actions/proxy tables could arguably live in reference files.	4 / 5
	Total	17 / 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 cleanly answers both what the skill does and when to use it, and its Cometly-specific framing makes it highly distinct. Its main weakness is generic action verbs ('manage data, records, automate workflows') that under-specify concrete capabilities and offer few keyword variations.

Suggestions

Replace generic verbs with concrete Cometly actions (e.g., 'Send purchase, sign-up, and checkout attribution events; query campaign and ad-set performance') to lift specificity.

Add natural trigger synonyms users might say, such as 'marketing attribution', 'ad spend', or 'campaign tracking', to broaden keyword coverage.

Tighten the 'when' clause to name concrete intents, e.g. 'Use when the user wants to send tracking events to Cometly or report on marketing attribution.'

Dimension	Reasoning	Score
Specificity	The description names the domain (Cometly) and a few actions ('Manage data, records, and automate workflows'), but those actions are generic verbs rather than concrete capabilities, matching the 'names domain and 1-2 concrete actions, but not comprehensive' anchor and falling short of the specific-action list required for a 4.	3 / 5
Completeness	Both halves are present — a 'what' clause ('Manage data, records, and automate workflows') and an explicit 'when' trigger ('Use when the user wants to interact with Cometly data'), matching the 'has both what and when; when could be more explicit or specific' anchor; it is not a 5 because neither clause is comprehensive with concrete trigger phrases.	4 / 5
Trigger Term Quality	It surfaces the primary natural keyword 'Cometly' (and 'Cometly data'), but offers no synonyms or variations a user might say, fitting the 'some relevant keywords but missing common variations or synonyms' anchor rather than the broad coverage of a 4.	3 / 5
Distinctiveness Conflict Risk	'Cometly integration' and 'interact with Cometly data' carve out a clear product-specific niche with distinct triggers and minimal overlap with other skills, matching the 'clear niche with distinct triggers; minimal conflict risk' anchor.	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/cometly/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.