Name: mixpanel
Rating: 59.2 (1 reviews)
Author: membranedev

mixpanel

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

Quality

68%

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

Quality

Content

75%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 copy-paste ready CLI commands and a well-sequenced connection-state workflow with feedback loops. Its main weakness is mild verbosity in the introductory overview and the lack of any external reference files for the longer API/action material.

Suggestions

Trim or remove the opening "Mixpanel is a product analytics platform..." overview paragraph and the entity hierarchy list, which restate domain knowledge Claude already has.

Fix the orphaned "#### 1b. Wait for the connection to be ready" heading by adding a corresponding step 1a or renumbering the connection flow as an explicit ordered list.

Consider moving the popular-actions discovery examples and the proxy flags table into a bundled reference file (e.g. ACTIONS.md) referenced one level deep from the body.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient command-focused content, but the opening overview paragraph ("Mixpanel is a product analytics platform that helps businesses understand user behavior...") explains what Mixpanel is, and the entity hierarchy list adds little actionable value, fitting the anchor for mostly efficient with some unnecessary explanation.	3 / 5
Actionability	It provides fully executable, copy-paste ready bash commands for the common cases (install, login, connection ensure, action run with JSON params, proxy requests) plus a concrete flags table, matching the anchor for fully executable examples covering common cases.	5 / 5
Workflow Clarity	The install → auth → connection → poll states → search → run → proxy flow is clearly sequenced with explicit state checkpoints and a feedback loop (poll again until READY; handle CLIENT_ACTION_REQUIRED and error states), but the orphaned "1b" heading without a matching "1a" and section-based rather than numbered sequencing leave a minor structural gap.	4 / 5
Progressive Disclosure	Content is well-organized into clearly headed sections with no nested references and no monolithic wall of text; however the skill is over 50 lines with no bundle files, and the popular-actions and proxy-flag reference material is inlined rather than split out, so it sits at good-but-not-ideal structure.	4 / 5
	Total	16 / 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 names a specific, distinctive domain and includes an explicit trigger clause, but its action list and trigger terms are generic and lack natural synonyms like events, funnels, or analytics. It is solid but could be sharpened with more concrete capabilities and varied trigger phrases.

Suggestions

Replace generic verbs ("Manage data, records, automate workflows") with concrete Mixpanel actions such as tracking events, building funnels, querying retention, and pulling segmentation reports.

Expand the trigger clause to include natural synonyms users say, e.g. "Use when the user wants to query Mixpanel events, funnels, retention, or user profiles."

Tighten the third-person phrasing so the "what" reads as a precise capability list rather than an abstract summary.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Mixpanel domain and a couple of actions, but the actions are generic ("manage data", "records") rather than concrete, matching the anchor that names domain plus 1-2 non-comprehensive actions.	3 / 5
Completeness	It has both a "what" ("Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with Mixpanel data"), though the trigger clause is somewhat generic rather than concrete.	4 / 5
Trigger Term Quality	"Mixpanel" and "interact with Mixpanel data" provide a relevant primary keyword, but common natural variations users say (events, funnels, retention, analytics) are missing, fitting the anchor for some relevant keywords without synonyms.	3 / 5
Distinctiveness Conflict Risk	Naming the specific product "Mixpanel" gives a clear niche with distinct triggers and low conflict risk, though the generic "interact with Mixpanel data" phrasing leaves minor overlap with adjacent analytics skills.	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/mixpanel/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.