Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Analyze Optimizely Experimentation and Web implementations for A/B testing, feature flags, and JavaScript SDK patterns
npx claudepluginhub twofoldtech-dakota/claude-marketplace --plugin optimizely-experimentation-analyzerAnalyze Optimizely Experimentation implementations for A/B testing, feature flags, and SDK patterns
Generate project-specific AI skills from Optimizely Experimentation patterns
Preview analysis scope and check for sensitive patterns in Optimizely Experimentation code
Initial configuration for Optimizely Experimentation analyzer
Analyze JavaScript/TypeScript code quality patterns for Optimizely implementations
Detect Optimizely Experimentation SDK and Web implementations
Analyze event tracking implementation and conversion patterns
Analyze A/B test implementation patterns and variation handling
Analyze feature flag implementation patterns and typed accessors
Uses power tools
Uses Bash, Write, or Edit tools
Share bugs, ideas, or general feedback.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
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-tracker agent to monitor its performance and document initial results."\n<commentary>\nLive experiments need immediate tracking setup to capture valuable data from the start.\n</commentary>\n</example>\n\n<example>\nContext: When reaching experiment milestones\nuser: "It's been a week since we launched the TikTok integration test"\nassistant: "Perfect timing for analysis. Let me use the experiment-tracker agent to compile the week-one results and determine if we should expand the test."\n<commentary>\nRegular experiment checkpoints ensure data-driven decisions about feature rollouts.\n</commentary>\n</example>\n\n<example>\nContext: Before making product decisions\nuser: "Should we keep the AI avatar feature or remove it?"\nassistant: "Let me analyze the experiment data to inform this decision. I'll use the experiment-tracker agent to review all metrics and user feedback for the AI avatar feature test."\n<commentary>\nProduct decisions should be backed by experiment data, not gut feelings.\n</commentary>\n</example>
Claude Code skill pack for PostHog (24 skills)
Core Web Vitals diagnosis and fixing skills for Claude Code — powered by CoreDash real user monitoring
LaunchDarkly agent skills and MCP servers for feature flag management, AgentControl, and metrics
Use this agent for comprehensive performance testing, profiling, and optimization recommendations. This agent specializes in measuring speed, identifying bottlenecks, and providing actionable optimization strategies for applications. Examples:\n\n<example>\nContext: Application speed testing
Access PostHog analytics, feature flags, experiments, error tracking, and insights directly from Claude Code. Optionally capture Claude Code sessions to PostHog LLM Analytics.
Claude Code plugin for Sitecore, Umbraco, and Optimizely CMS development — scaffolding, content modeling, accessibility scanning, security audits, best practices, and code generation
Sitecore XP AWS-to-Azure migration planning assistant. Guides architects through structured discovery, cross-reference analysis, phased estimation, and client-ready deliverable generation.
Analyze Umbraco 14-16 projects for architecture, security, and backoffice patterns
Analyze Optimizely CMS/Content Cloud projects for architecture, security, content modeling, and performance patterns
Analyze Sitecore 10.x projects for Helix compliance, security, and performance
Claude Code plugins that analyze your CMS codebase and make you a better developer.
Stop guessing about best practices. Get automated analysis with specific issues, exact locations, and actionable fixes for Sitecore, Umbraco, and Optimizely projects.
Working with enterprise CMS platforms is hard:
This marketplace provides platform-specific analyzers that understand your CMS deeply:
/sitecore-classic:analyze
✓ Scanned 847 files across 12 projects
✓ Detected Sitecore 10.4 with Helix architecture
Issues Found: 14 (2 Critical, 6 Warning, 6 Info)
CRITICAL: [SEC-003] Hardcoded connection string detected
Location: src/Foundation/Database/code/ConnectionFactory.cs:24
Fix: Move to environment variable or Azure Key Vault
CRITICAL: [ARCH-001] Cross-Feature dependency violates Helix
Location: src/Feature/Navigation/code/Feature.Navigation.csproj:31
Fix: Extract SharedModels to Foundation layer
Every issue includes severity, exact location, and how to fix it.
/plugin marketplace add https://github.com/twofoldtech-dakota/claude-marketplace.git
| Your CMS | Install Command |
|---|---|
| Sitecore 10.x | /plugin install sitecore-classic@cms-analyzers-marketplace |
| Sitecore XM Cloud | /plugin install xm-cloud@cms-analyzers-marketplace |
| Umbraco 14-16 | /plugin install umbraco@cms-analyzers-marketplace |
| Optimizely CMS | /plugin install optimizely@cms-analyzers-marketplace |
| Optimizely Experimentation | /plugin install optimizely-exp@cms-analyzers-marketplace |
/sitecore-classic:analyze # Full analysis with report
/xm-cloud:analyze # XM Cloud analysis
/umbraco:analyze # Umbraco analysis
/optimizely:analyze # Optimizely CMS analysis
/optimizely-exp:analyze # Experimentation analysis
That's it. You'll get a detailed markdown report with all issues, scores, and recommendations.
For on-premise and managed cloud Sitecore implementations:
| Category | What's Analyzed |
|---|---|
| Architecture | Helix compliance, layer dependencies, solution structure |
| Serialization | SCS/Unicorn conflicts, overlapping includes, field value queries |
| Security | Config credentials, CORS settings, admin paths, XSS patterns |
| Performance | HTML cache settings, Solr optimization, Sitecore.Query usage |
| Code Quality | Glass Mapper patterns, DI implementation, controller complexity |
| Dependencies | NuGet compatibility with Sitecore version |
For headless Sitecore with Next.js and JSS:
| Category | What's Analyzed |
|---|---|
| Architecture | Component organization, layout patterns, app structure |
| GraphQL | Query efficiency, N+1 detection, fragment usage |
| Security | API key exposure, environment variables, introspection risks |
| Performance | SSR vs SSG decisions, bundle size, image optimization |
| TypeScript | Type safety, JSS patterns, React best practices |
| Dependencies | npm package compatibility, JSS version alignment |
For modern Umbraco with Lit backoffice and Content Delivery API:
| Category | What's Analyzed |
|---|---|
| Architecture | Composer patterns, service registration, project structure |
| Backoffice | Lit components, property editors, TypeScript quality |
| API | Content Delivery API setup, Management API, custom endpoints |
| Security | API authentication, credentials, backoffice access |
| Performance | HybridCache (v15+), content access patterns, Examine indexes |
| Code Quality | Controllers, notification handlers, service patterns |
For Optimizely CMS 12.x and 13.x implementations:
| Category | What's Analyzed |
|---|---|
| Content Modeling | Content types, GUID requirements, block/page inheritance |
| Architecture | Content area restrictions, initialization modules |
| Security | Content Delivery API exposure, configuration secrets |
| Performance | Caching strategies, CDN configuration, N+1 queries |
| Code Quality | Service Locator anti-patterns, DI best practices |
| A/B Testing | Experimentation module integration |