Inspect before downloading
See what is inside
These previews come from the published bundle files, so you can judge the method and writing before using it.
Tool guide
Amplitude
Defines safe, source-aware use of Amplitude in product analytics and product-management bundles.
Read the fileWorkflow
Plan Funnel Analysis
Plan an Amplitude funnel analysis with explicit steps, filters, identity logic, time windows, and caveats.
Read the fileWorkflow
Review Amplitude Event Taxonomy
Review event and property definitions before analytics interpretation or instrumentation changes.
Read the fileTemplate
Amplitude Analysis Brief
Decision-facing brief for Amplitude analysis, evidence quality, and next actions.
Read the fileIs this bundle right for your task?
Who it is for
- People who configure, operate, integrate, govern, or review work performed in Amplitude
- Teams working in software, digital-products, b2b-saas
When to use it
- A proposed Amplitude configuration or workflow change needs current IDs, permissions, dependencies, tests, and rollback evidence.
- A report, export, integration, or automation result needs to be reconciled against actual workspace state and current product documentation.
What you need to provide
- The product version or workspace scope, relevant configuration or export, desired outcome, permissions, and accountable owner.
- Current IDs, settings, records, logs, screenshots, integration details, and test evidence needed to verify the requested change.
Tasks and expected outputs
Questions it helps answer
- Plan Amplitude analysis without inventing event names, properties, chart definitions, cohorts, or account settings.
- Review product analytics evidence with explicit metric definitions, filters, identity logic, and source-of-record caveats.
- Use funnels, cohorts, experiments, and session replay as evidence without overstating causality or privacy readiness.
What it helps produce
- Amplitude analysis brief
Practical example
Use it with an agent
Load the bundle as context, provide the evidence named above, then adapt this example to your situation.
Provide the product version or workspace scope, relevant configuration or export, desired outcome, permissions, and accountable owner. Ask the agent to review Amplitude and produce Amplitude analysis brief that maps configuration evidence, dependencies, permissions, tests, rollback, and actions that still require approval. Begin with url, then confirm that the reference is current and applicable. Inspect Amplitude before drafting.
Context path: bundles/tools/amplitude
What the bundle includes
Tools
- Amplitude
Frameworks
- event taxonomy review
- funnel analysis
- cohort analysis
- experiment evidence review
- session replay evidence review
Commands
/plan-amplitude-analysis
Evaluations
- Amplitude analysis quality check
Sources used to build this bundle
These are the public references behind the role definition and operating guidance. The bundle does not replace current documentation or evidence from your site.
Limitations and safe use
Do not use this for
- Changing live configuration, records, permissions, automations, integrations, or shared data without verified scope, testing, rollback, and approval.
Known limitations
- Not a complete Amplitude product, API, SDK, pricing, plan, data governance, privacy, or administration reference.
- Requires user-provided Amplitude workspace, chart, event, property, cohort, experiment, replay, permission, and policy evidence before final conclusions.
- Does not replace data engineering, privacy, security, legal, product analytics, experimentation, or Amplitude administrator review.
Safety notes
- Require confirmation before changing instrumentation, cohorts, experiments, dashboards, alerts, permissions, exports, integrations, privacy settings, or user-facing experiences.
- Do not claim access to Amplitude projects, events, properties, users, cohorts, charts, experiments, replays, permissions, or exports unless the user provides evidence or authorized tool access.