Name: snowplow-analytics
Rating: 56.8 (1 reviews)
Author: membranedev

snowplow-analytics

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

Quality

65%

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

Quality

Content

67%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 concrete CLI commands and a well-sequenced connection workflow that includes state-polling validation. Its main weaknesses are conciseness padding at the top, broken step cross-references, and a 'Popular actions' section that underdelivers.

Suggestions

Trim the opening platform description and filler phrases ('so you can focus on the integration logic rather than auth plumbing', 'This is the fastest way to get a connection') to assume Claude's competence.

Fix the broken cross-references: label the 'Searching for actions' section as 'Step 2' and add a '1a' heading for connection ensure, or remove the dangling 'Step 2' references.

Flesh out 'Popular actions' with 3-5 concrete example Snowplow actions (e.g. query events, list data sources, run a data quality test) with real input examples, or remove the empty heading.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with executable command blocks, but opens by explaining what Snowplow is ('a behavioral data platform that helps businesses track and understand user interactions...') and includes filler like 'so you can focus on the integration logic rather than auth plumbing' and 'This is the fastest way to get a connection', matching the 'mostly efficient but some unnecessary explanation' anchor.	3 / 5
Actionability	Provides concrete, executable commands throughout (install, login, connection ensure, action list/run, request proxy) plus a flag table; examples use placeholders like <actionId> and /path/to/endpoint rather than real Snowplow endpoints, leaving minor gaps versus fully copy-paste-ready coverage.	4 / 5
Workflow Clarity	The connection workflow is clearly sequenced with an explicit validation feedback loop (poll until READY, act on CLIENT_ACTION_REQUIRED, re-poll), but cross-references are broken ('skip to Step 2' with no Step 2 label, '1b' with no 1a) and action results lack verification, matching 'clear sequence with most checkpoints present; minor validation gaps'.	4 / 5
Progressive Disclosure	Content is well-organized into clear sections with headers and no external bundle files to navigate; however the 'Popular actions' heading promises a catalog that is not delivered and the unexplained entity overview list is inline, giving 'good structure; minor organization gaps' rather than a clean overview with one-level references.	4 / 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 cleanly answers both 'what' and 'when' and is well-anchored by a specific product name, but its action list is generic and it omits the natural Snowplow vocabulary (events, tracking, pipeline) that users would actually invoke. It is solid but not comprehensive.

Suggestions

Replace generic verbs with concrete Snowplow capabilities, e.g. 'Query event data, manage pipelines and data sources, run data quality tests, and transform records' to lift specificity.

Add natural trigger terms users say, such as 'events', 'tracking', 'pipeline', or 'data quality', so the skill surfaces for real Snowplow requests.

Tighten the 'Use when' clause to concrete triggers, e.g. 'Use when the user wants to query Snowplow events, inspect pipeline health, or run data quality tests.'

Dimension	Reasoning	Score
Specificity	Names the domain ('Snowplow Analytics integration') and a few actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete—closer to the anchor listing 1-2 non-comprehensive actions than to the multi-specific-action anchors.	3 / 5
Completeness	Explicitly states both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Snowplow Analytics data'); the 'when' trigger is present but generic, fitting the anchor where 'when' could be more explicit rather than the fully concrete anchor 5.	4 / 5
Trigger Term Quality	Includes the product name and 'data' but misses the natural Snowplow terms users would actually say (events, tracking, pipeline, enrichment); keyword coverage is relevant but lacks common variations, matching the 'some relevant keywords but missing synonyms' anchor.	3 / 5
Distinctiveness Conflict Risk	The specific product name 'Snowplow Analytics' gives a clear niche with minimal conflict risk, but the generic action verbs ('manage data, records, workflows') create minor overlap with other data/analytics skills, matching 'mostly distinct; minor overlap 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/snowplow-analytics/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.