CtrlK
BlogDocsLog inGet started
Tessl Logo

auth

Manages Mixpanel credentials for the mixpanel_headless library and the mp CLI — checks the active session, lists, adds, and switches accounts, runs OAuth login (one-shot `mp login` or the two-step flow), switches projects and workspaces, and manages saved targets. Use when Mixpanel credentials are missing or failing, when code raises AuthenticationError or reports no account or no project, when the user wants to log in, switch account, project, or workspace, or save or use a target; on 401 or "unauthorized" errors; for "which project am I on?"; or for a login in the EU or India region. Do not use for installing or upgrading the library (use setup) or for analytics questions once credentials work (use mixpanelyst).

75

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

88%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.

An excellent instruction skill: fully executable commands, explicit state-based branching, and validation with error-recovery loops throughout. The only deductions are mild token cost from repeated full command paths and keeping all per-subcommand detail in a single inline file rather than splitting the heavier wizards into references.

Suggestions

Define the interpreter path once as a shorthand after noting the allowed-tools constraint, then use a compact form in the per-subcommand prose to cut repeated full-path tokens while keeping the pre-approved command text intact.

Move the multi-step 'account add' and 'login' wizard detail (steps 1-7 with the alternate command blocks) into a reference file linked from the Routing section, keeping SKILL.md as a lean routing table plus presentation rules.

DimensionReasoningScore

Conciseness

The body is dense, operational, and assumes Claude's competence — no concept teaching — but the full interpreter path is repeated verbatim a dozen times and several subcommands state the same command twice (a 'list first, then use' pair). This sits between anchors 4 and 5: efficient with minor trimming opportunities, so 4 rather than 5.

4 / 5

Actionability

Every instruction is copy-paste ready: exact commands with full paths, exact expected output strings ("Active: `account.name` → project `project.id`"), per-state branching, and complete `!` command blocks with placeholder-replacement notes. Fully matches the anchor-5 example.

5 / 5

Workflow Clarity

Sequences are explicit and validated: the account wizard is numbered with an `account test` verification step and `result.ok` reporting, login flows re-check session then test, and every error path has a recovery route (e.g., the MP_SECRET prompt-failure fallback, `error.actionable` handling). Not below 5 because no destructive or batch operation lacks validation.

5 / 5

Progressive Disclosure

Well-organized sections (Security rules, Routing, Presentation) and the one bundle file (scripts/auth_manager.py) is real, correctly pathed, and one level deep — no nested-reference chains. However, ~230 lines of per-subcommand detail all live inline in SKILL.md; the longer wizard material could be split out. Good structure with minor organization gaps, matching anchor 4 rather than 5.

4 / 5

Total

18

/

20

Passed

Description

100%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 exemplary: concrete third-person capability list, explicit 'Use when' triggers with error-code and natural-language synonyms, and explicit do-not-use boundaries that separate it from adjacent skills. It is dense but every clause is functional rather than padded.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "checks the active session, lists, adds, and switches accounts, runs OAuth login (one-shot `mp login` or the two-step flow), switches projects and workspaces, and manages saved targets" — with comprehensive coverage and consistent third-person voice. It exceeds anchor 4 because no capability area is missing.

5 / 5

Completeness

Explicitly answers both questions: the "what" enumerates concrete capabilities, and "Use when Mixpanel credentials are missing or failing... when the user wants to log in..." provides concrete trigger phrases. The explicit 'Use when' clause removes the anchor-4 ambiguity.

5 / 5

Trigger Term Quality

Covers natural user phrasings and synonyms including "credentials are missing or failing", "log in", "switch account, project, or workspace", "401 or 'unauthorized' errors", "which project am I on?", and the EU/India region case. Matches the comprehensive-synonyms anchor exactly.

5 / 5

Distinctiveness Conflict Risk

A clear Mixpanel-credentials niche with distinctive triggers, plus explicit negative boundaries ("Do not use for installing or upgrading the library (use setup) or for analytics questions once credentials work (use mixpanelyst)") that prevent overlap with sibling skills.

5 / 5

Total

20

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository
mixpanel/mixpanel-headless
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.