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.

56

Quality

65%

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-claude/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

61%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 a well-structured, actionable MCP-tool playbook with concrete tool sequences, parameters, and pitfalls. Its main weaknesses are redundant pitfall duplication, a missing verification checkpoint on the destructive batch-profile update, and some inline reference material that could be split out.

Suggestions

Add an explicit verification/dry-run step to the batch profile-update workflow (e.g., query affected profiles first and confirm count before applying BATCH_UPDATE) to lift workflow clarity above the cap.

De-duplicate the 'Known Pitfalls' section against the per-workflow 'Pitfalls' blocks, or collapse one into a pointer to the other, to reduce token redundancy.

Consider moving the Quick Reference table and Mixpanel Expression Syntax reference into a separate references/ file, keeping SKILL.md a lean overview.

DimensionReasoningScore

Conciseness

The body is mostly actionable with no beginner-concept padding, but the 'Known Pitfalls' section repeats date-format and expression-syntax details already covered in per-workflow 'Pitfalls', and the Quick Reference table re-lists tool slugs/params, so it could be tightened.

3 / 5

Actionability

Concrete tool slugs, explicit parameter lists, prerequisite/required/optional tags, and worked expression-syntax examples give mostly executable guidance; minor gaps are the absence of a single complete end-to-end query example.

4 / 5

Workflow Clarity

Workflows are well sequenced with numbered tool steps and a setup validation checkpoint ('Confirm connection status shows ACTIVE'), but the destructive PROFILE_BATCH_UPDATE workflow lacks a verify/dry-run checkpoint before applying batch operations, capping clarity at 3.

3 / 5

Progressive Disclosure

No bundle files exist and the skill is a single inline document; sections are well-organized with clear headers, no nested references, and a reasonable overview-to-detail split, though the Quick Reference and expression-syntax blocks could live in a separate reference file.

4 / 5

Total

14

/

20

Passed

Description

70%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 is specific and distinctive, naming a clear Mixpanel-automation niche with natural trigger terms, but it omits any explicit 'Use when...' trigger guidance, which caps completeness. Adding a when-to-use clause would lift it from good to excellent.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the user wants to query Mixpanel analytics, build funnels/cohorts, or run JQL/segmentation reports.'

Convert the capability nouns into verb-object actions (e.g. 'query events, run segmentation, analyze funnels, list cohorts, update user profiles') to push specificity toward the top anchor.

DimensionReasoningScore

Specificity

The description lists six concrete capability areas ('events, segmentation, funnels, cohorts, user profiles, JQL queries') but they are nouns rather than verb-object actions, leaving minor gaps versus the comprehensive verb-led anchor 5.

4 / 5

Completeness

The 'what' is clear ('Automate Mixpanel tasks... events, segmentation, funnels...') but there is no 'Use when...' clause; 'Always search tools first' is operational guidance, not when-to-use, so completeness is capped at 3.

3 / 5

Trigger Term Quality

Natural analytics terms ('Mixpanel', 'funnels', 'cohorts', 'segmentation', 'JQL') match what users would say, though 'Rube MCP (Composio)' is technical jargon and a few synonyms are missing.

4 / 5

Distinctiveness Conflict Risk

'Mixpanel' coupled with 'Rube MCP (Composio)' is a clear, narrow niche with distinct triggers and minimal conflict risk with other skills.

5 / 5

Total

16

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

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.