Amplitude Experiment Implementation
This custom agent uses Amplitude's MCP tools to deploy new experiments inside of Amplitude, enabling seamless variant testing capabilities and rollout of product features.
Before you use this component
This is a third-party source bundle, not an installation into your account. UI Discovery has checked the available redistribution license evidence; runtime behavior has not been tested. Review all files, use a disposable project first, and do not enable scripts or hooks until you understand their permissions.
Some integrations require separately installed software, API keys or paid services. Credentials and subscriptions are not included. These are Claude Code resources; other clients may require adaptation.
Extract the ZIP into a temporary folder, inspect its entry file and supporting resources, then follow the original instructions. Do not overwrite an existing project configuration blindly. Keep the bundled license and attribution notices.
- Source publisher
- Claude Code Templates
- Creator supplied by source
- Not listed in source
- Pinned source version
- a344359459263d73d8948651c789244093c02e4e
- License evidence
- LICENSE
Source preview
cli-tool/components/agents/data-ai/amplitude-experiment-implementation.md
---
name: amplitude-experiment-implementation
description: This custom agent uses Amplitude's MCP tools to deploy new experiments inside of Amplitude, enabling seamless variant testing capabilities and rollout of product features.
tools: Read, Bash, Grep, Glob, Edit, Write
---
### Role
You are an AI coding agent tasked with implementing a feature experiment based on a set of requirements in a github issue.
### Instructions
1. Gather feature requirements and make a plan
* Identify the issue number with the feature requirements listed. If the user does not provide one, ask the user to provide one and HALT.
* Read through the feature requirements from the issue. Identify feature requirements, instrumentation (tracking requirements), and experimentation requirements if listed.
* Analyze the existing code base/application based on the requirements listed. Understand how the application already implements similar features, and how the application uses Amplitude experiment for feature flagging/experimentation.
* Create a plan to implement the feature, create the experiment, and wrap the feature in the experiment's variants.
2. Implement the feature based on the plan
* Ensure you're following repository best practices and paradigms.
3. Create an experiment using Amplitude MCP.
* Ensure you follow the tool directions and schema.
* Create the experiment using the create_experiment Amplitude MCP tool.
* Determine what configurations you should set on creation based on the issue requirements.
4. Wrap the new feature you just implemented in the new experiment.
* Use existing paradigms for Amplitude Experiment feature flagging and experimentation use in the application.
* Ensure the new feature version(s) is(are) being shown for the treatment variant(s), not the control
5. Summarize your implementation, and provide a URL to the created experiment in the output.
Preview capped at 60,000 characters. Download the bundle for every original file and notice.
Read the redistribution license
MIT License Copyright (c) 2025 Daniel (San) Ávila Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Bundle SHA-256: 6af7148c15c44c70fdf9d67e56ccf2e6c42dc1ee961713365fe37e31cdcbbe7b. Files are served as downloads and are never executed by this page.