experiment-tracker 1.0.0 Immutable snapshotLatest
Pinned to commit 5bd4f168edf7c18a8303cbfde20708ff62aabc4d, captured .
Download 1.0.0 source archive Choose something to compare with View commit on GitHub
More actions and subscriptions
Current package description (not historical)
PROACTIVELY use this agent when experiments are started, modified, or when results need analysis. This agent specializes in tracking A/B tests, feature experiments, and iterative improvements within the 6-day development cycle. Should be triggered automatically when experimental code paths or feature flags are introduced. Examples:\n\n<example>\nContext: When implementing feature flags or A/B test variants\nuser: "Add a feature flag to test the new onboarding flow"\nassistant: "I've implemented the feature flag for the onboarding flow A/B test. Let me use the experiment-tracker agent to properly document this experiment and set up tracking."\n<commentary>\nEvery feature flag represents an experiment that needs proper tracking and success metrics.\n</commentary>\n</example>\n\n<example>\nContext: After deploying experimental features\nuser: "The new viral sharing feature is now live for 10% of users"\nassistant: "Great! The viral sharing feature is deployed. I'll use the experiment-tra…
Install
This version is listed in the verified marketplace awesome-claude-code-plugins (repository ccplugins/awesome-claude-code-plugins). Run these in Claude Code, in order:
- Add the marketplace
/plugin marketplace add ccplugins/awesome-claude-code-plugins - Install the plugin
/plugin install experiment-tracker@awesome-claude-code-plugins
These commands install the marketplace's current upstream state, not the pinned commit snapshot on this page; the two can differ.
Contents 1
Agent1
-
experiment-tracker
plugins/experiment-tracker/agents/experiment-tracker.mdPermalink
Nothing matches.
Dependencies, compatibility and skill declarations
Recorded dependencies 0
No dependency requirements were recorded from plugin.json or marketplace entries. Only manifest fields saved with the snapshot are shown here; dependency declarations in other files are outside the current collection scope.
Recorded compatibility
No compatibility requirement was recorded for this snapshot from plugin.json or a marketplace entry. Only manifest fields saved with the snapshot are shown here. Declarations in a skill's SKILL.md header are collected separately and, when present, shown on their own under “Skill file declarations”; they never overwrite or fill in this value.