Creating a business context skill#35
Open
yonahdorfman wants to merge 2 commits into
Open
Conversation
…s the AI readiness score
|
Please run https://github.com/mixpanel/ai-plugins/tree/main/.claude/skills/review-skill and post passing score in the test plan. |
zoeabrams-eng
self-requested a review
July 17, 2026 22:55
| | [`manage-experiment`](plugins/mixpanel-mcp/skills/manage-experiment/) | Coaches an agent through any phase of a Mixpanel experiment — designing before launch (hypothesis, metrics, sizing, statistical model, advanced features, pre-launch checks) and interpreting after launch (read results, ship / iterate / kill / wait, health checks, segment breakdowns, session replays). | | ||
| | [`manage-feature-flags`](plugins/mixpanel-mcp/skills/manage-feature-flags/) | Coaches an agent through Mixpanel feature-flag work — picking the right flag-shaped tool (Feature Gate vs Dynamic Config vs Experiment), staged rollouts, the kill switch, exposure debugging, archive/restore, and SDK call patterns. | | ||
| | [`manage-lexicon`](plugins/mixpanel-mcp/skills/manage-lexicon/) | Audits, scores, enriches, and cleans up Lexicon metadata (events and properties) for a Mixpanel project. Supports scoring health, bulk-filling descriptions/tags, resetting metadata, triaging data quality issues, and managing tags. | | ||
| | [`mixpanel-ai-readiness`](plugins/mixpanel-mcp/skills/mixpanel-ai-readiness/) | Sets up business context (org and project level) and delegates Lexicon enrichment so Mixpanel's AI assistants understand a customer's data. Supports status scoring, importing existing context, interview-based setup, and choosing org vs. project scope. | |
There was a problem hiding this comment.
Do you mean prepare-ai-readiness?
| ## Step 1 — Research and pull schema first | ||
|
|
||
| Before asking the user anything (per `references/interview-questions.md`): | ||
| - **Web search the company** and draft the Business and Customer Segments sections from public sources — these are confirmed, not asked cold. |
There was a problem hiding this comment.
Does web search always exist where this skill will be used?
| | Glossary, acronyms, "what we mean by X" | Internal Vocabulary & Acronyms | | ||
| | Tracking plan, event spec, naming rules, casing/prefix conventions | Event Taxonomy & Naming Conventions | | ||
| | Data owner, schema owner, "ask X before adding events", RACI | Authority & Governance | | ||
| | List of canonical dashboards/reports and their purpose | Key Dashboards & Reports | |
There was a problem hiding this comment.
This and line 17 don't have consistent naming and sections throughout the diff.
| 4. **Preview + diff before every context write.** Show the full proposed document and what changes vs current. Require literal `CONFIRM`. `EXPORT` saves a local `.md` without writing. Anything else cancels. | ||
| 5. **Permission pre-check** for each target before doing unsaveable work; offer a level the user can edit, or `EXPORT`. | ||
| 6. **Never overwrite populated content silently.** Existing sections are preserved and shown; the user chooses per section. | ||
| 7. **Back up before every write.** Before writing, save the existing context to `backups/{level}-{id}-backup-{ISO-timestamp}.md` (an empty file with a note if context was empty) and report the path — so a prior version can be restored manually if a write turns out to be wrong. |
There was a problem hiding this comment.
Will agent always be able to create files in these locations?
|
There are some instructions that may depend on functionality that isn't supported. Could you do a pass over required instructions to confirm they are possible (else relax the instructions)? |
zoeabrams-eng
requested changes
Jul 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Created a skill to help customers completely fill out the context for use with Mixpanels AI
Why
This was created to make a comprehensive skill that specifically focuses on getting Mixpanels AI context set up with everything working properly. In conversations with customers they wanted to take the context from other places and make sure it is filled out properly. This skill is made to help them with that.
Type
Skill review
│ Dimension │ Score │ Weight │
├──────────────────────────────┼───────┼────────┤
│ D1 — Spec Compliance │ 90% │ 10% │
├──────────────────────────────┼───────┼────────┤
│ D2 — Description & Triggers │ 100% │ 15% │
├──────────────────────────────┼───────┼────────┤
│ D3 — Structure & Readability │ 92% │ 15% │
├──────────────────────────────┼───────┼────────┤
│ D4 — DRY & Portability │ 88% │ 20% │
├──────────────────────────────┼───────┼────────┤
│ D5 — Safety & Data Integrity │ 100% │ 10% │
├──────────────────────────────┼───────┼────────┤
│ D6 — UX & Communication │ 100% │ 10% │
├──────────────────────────────┼───────┼────────┤
│ D7 — Domain Expertise │ 100% │ 10% │
├──────────────────────────────┼───────┼────────┤
│ D8 — Content Quality │ 100% │ 10%
Testing
Tested on internal projects, output is a completed lexicon, business + project context