CtrlK
BlogDocsLog inGet started
Tessl Logo

mixpanel-automation

Automate Mixpanel tasks via Rube MCP (Composio): events, segmentation, funnels, cohorts, user profiles, JQL queries. Always search tools first for current schemas.

53

Quality

60%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/mixpanel-automation/SKILL.md

The canonical home for this skill is mixpanel-automation in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

50%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill provides a comprehensive catalog of Mixpanel operations via Rube MCP with clear tool naming and parameter documentation. Its main weaknesses are the lack of concrete executable examples (tool calls with realistic parameters), repeated information across sections (especially date format and expression syntax warnings), and missing validation steps for destructive batch operations. The content would benefit from being more concise and splitting detailed reference material into separate files.

Suggestions

Add concrete, copy-paste ready tool invocation examples with realistic parameter values for at least the most common workflows (e.g., aggregate events, segmentation)

Consolidate repeated pitfalls (date formats, expression syntax, case sensitivity) into the 'Known Pitfalls' section and remove duplicates from individual workflow sections

Add explicit validation/verification steps to the batch update workflow (e.g., 'Query updated profiles to confirm changes applied correctly')

Split the expression syntax reference and detailed workflow guides into separate bundle files, keeping SKILL.md as a concise overview with links

DimensionReasoningScore

Conciseness

The skill is moderately verbose with repeated pitfall sections across each workflow that share overlapping information (e.g., date format warnings appear multiple times). The expression syntax is documented both inline in workflows and in a dedicated section. The 'When to Use' footer is vacuous. However, much of the content is genuinely useful reference material Claude wouldn't know.

3 / 5

Actionability

The skill provides tool names, parameter lists, and expression syntax examples, which is helpful. However, there are no executable code examples or copy-paste ready tool invocations with actual parameter values. The 'Common Patterns' section uses pseudocode-style numbered lists rather than concrete tool call examples with realistic parameters.

3 / 5

Workflow Clarity

Each workflow has a clear tool sequence with prerequisite/required labels, which is good. However, the batch update workflow (Section 4) involves destructive operations on user profiles but lacks explicit validation/verification steps or feedback loops. There's no 'verify the update succeeded' step or error recovery guidance for batch operations, which should cap this at 3.

3 / 5

Progressive Disclosure

The content is a single monolithic file with no bundle files or external references. At ~200+ lines covering 6 distinct workflows plus common patterns and a quick reference table, some of this content (like the expression syntax reference or detailed workflow guides) would benefit from being split into separate files. The internal structure with headers is reasonable but the file is dense.

3 / 5

Total

12

/

20

Passed

Description

70%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 effectively identifies the specific domain (Mixpanel via Composio/Rube MCP) and lists several concrete task areas, making it distinctive and reasonably specific. Its main weakness is the absence of an explicit 'Use when...' clause that would help Claude know exactly when to select this skill. Adding natural trigger phrases and a 'when' clause would significantly improve selection accuracy.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Mixpanel analytics, product metrics, event tracking, or funnel analysis.'

Include broader synonyms and natural user phrases such as 'analytics', 'product analytics', 'tracking', 'retention analysis' to improve trigger term coverage.

DimensionReasoningScore

Specificity

Lists several specific actions: events, segmentation, funnels, cohorts, user profiles, JQL queries. These are concrete Mixpanel concepts. Minor gap in not elaborating what actions are performed on each (e.g., create, query, analyze).

4 / 5

Completeness

The 'what' is clear — automate Mixpanel tasks across several domains. However, there is no explicit 'Use when...' clause or equivalent trigger guidance, which caps this at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

Includes strong natural keywords like 'Mixpanel', 'events', 'segmentation', 'funnels', 'cohorts', 'user profiles', 'JQL queries', and 'Composio'. Missing some natural user phrases like 'analytics', 'tracking', 'product analytics', or 'retention'.

4 / 5

Distinctiveness Conflict Risk

Highly distinctive with specific tool references (Mixpanel, Rube MCP, Composio) and domain-specific terms (JQL queries, cohorts, funnels). Very unlikely to conflict with other skills.

5 / 5

Total

16

/

20

Passed

Validation

90%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
Reviewed

Table of Contents

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.