30f9b9a729
* feat: v2.0 skill renames and CRO consolidation BREAKING CHANGE: Users must reinstall skills after this update. ## Skill Renames (16) - ab-test-setup → ab-testing - analytics-tracking → analytics - aso-audit → aso - competitor-alternatives → competitors - email-sequence → emails - free-tool-strategy → free-tools - launch-strategy → launch - onboarding-cro → onboarding - paywall-upgrade-cro → paywalls - popup-cro → popups - pricing-strategy → pricing - product-marketing-context → product-marketing - referral-program → referrals - schema-markup → schema - signup-flow-cro → signup - social-content → social ## Consolidations (1) - page-cro + form-cro → cro (form content in references/form.md) ## Why 2.0? - Shorter, cleaner skill names - Consistent naming (no -strategy, -setup, -cro suffixes) - All cross-references updated across 100+ files Total skills: 40 Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * fix(v2.0): update evals for renamed skills, fix validate script, clear warnings - Update 32 evals.json files to reference new skill names (page-cro → cro, product-marketing-context → product-marketing, etc.) — these were missed in the initial v2.0 rename pass since only SKILL.md and marketplace.json were updated. - Fix validate-skills.sh: replace GNU-only `head -n -1` with portable awk so frontmatter extraction works on macOS. - Move Copy Editing Checklist (56 lines) to references/checklist.md to bring copy-editing SKILL.md under the 500-line limit (508 → 457). - Add "see X" pointers to marketing-psychology description for skill discovery (cro, pricing, copywriting). - Update skill-request.yml issue template placeholder (page-cro → cro). All 40 skills now pass validation with zero warnings. * fix(v2.0): add evals for 8 missing skills, strip stale frontmatter from cro/form.md Adds 48 new eval cases (6 per skill) for skills that previously had no evals: aso, co-marketing, community-marketing, competitor-profiling, directory-submissions, image, lead-magnets, video. All 40 skills now have eval coverage (251 total cases). Strips leftover frontmatter from skills/cro/references/form.md — it was inherited from the old form-cro SKILL.md before consolidation. Reference files don't need frontmatter. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * fix(v2.0): rename paid-ads → ads One more v2.0 simplification — drops the redundant 'paid-' qualifier. Updates the skill directory, SKILL.md frontmatter, evals.json, README skill table, the v2.0 rename table in VERSIONS.md (now 17 renames), and all cross-references in related skills (ad-creative, aso, competitor-profiling, customer-research, lead-magnets, marketing-ideas) plus the tools/integrations guides. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * fix(v2.0): bump SKILL.md frontmatter version to 2.0.0 for all 40 skills VERSIONS.md was already updated to 2.0.0 but the metadata.version field inside each SKILL.md was still on 1.x. That mismatch would have caused the update-check flow to perpetually report 'update available' since it compares VERSIONS.md against local SKILL.md metadata versions. Caught by codex review (P1). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * fix(v2.0): add legacy product-marketing-context.md filename fallback Before this fix, users upgrading from v1.x who had a `product-marketing-context.md` file would lose automatic context loading — every skill only checked the new `product-marketing.md` filename. Now all 40 skills also accept the legacy filename (in either `.agents/` or `.claude/`), and the README migration command covers both legacy and current filenames. Caught by codex review (P1 + P2). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * fix(v2.0): re-sort README skills table alphabetically, fix ads box width The skills table had a few entries out of alphabetical order from the renames (co-marketing was after cold-email, ads was at the renamed position). Re-sorted alphabetically per sync-skills.js. Also padded the 'ads' cell in the ASCII flow diagram to keep the box width consistent. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * fix(v2.0): document folder cleanup on upgrade, stop sync-skills from re-adding skills array README upgrade guide now includes: - A clear cleanup step for stale v1.x skill folders (renamed + consolidated) so users don't end up with both old and new folders side-by-side after upgrading - The full v1 to v2 rename map for reference - Existing product-marketing-context.md migration steps (preserved) sync-skills.js no longer (re-)introduces a `skills` array on marketplace.json -- Claude Code's plugin schema discovers skills via the `skills/` directory, and the explicit array was failing validation. The script now refreshes the description count and strips the stale array if present. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
3.9 KiB
3.9 KiB
Optimizely
A/B testing and experimentation platform with a REST API for managing projects, experiments, campaigns, and results.
Capabilities
| Integration | Available | Notes |
|---|---|---|
| API | ✓ | Projects, Experiments, Campaigns, Audiences, Results |
| MCP | - | Not available |
| CLI | ✓ | optimizely.js |
| SDK | ✓ | JavaScript, Python, Ruby, Java, Go, C#, PHP, React, Swift, Android |
Authentication
- Type: Bearer Token (Personal Access Token or OAuth 2.0)
- Header:
Authorization: Bearer {personal_token} - Get token: https://app.optimizely.com/v2/profile/api > Generate New Token
Common Agent Operations
List Projects
GET https://api.optimizely.com/v2/projects
Get Project
GET https://api.optimizely.com/v2/projects/{project_id}
List Experiments
GET https://api.optimizely.com/v2/experiments?project_id={project_id}
Get Experiment
GET https://api.optimizely.com/v2/experiments/{experiment_id}
Get Experiment Results
GET https://api.optimizely.com/v2/experiments/{experiment_id}/results
Create Experiment
POST https://api.optimizely.com/v2/experiments
{
"project_id": 12345,
"name": "Homepage CTA Test",
"type": "a/b",
"variations": [
{ "name": "Control", "weight": 5000 },
{ "name": "Variation 1", "weight": 5000 }
],
"metrics": [{ "event_id": 67890 }],
"status": "not_started"
}
Update Experiment
PATCH https://api.optimizely.com/v2/experiments/{experiment_id}
{
"status": "running"
}
List Campaigns
GET https://api.optimizely.com/v2/campaigns?project_id={project_id}
Get Campaign Results
GET https://api.optimizely.com/v2/campaigns/{campaign_id}/results
List Audiences
GET https://api.optimizely.com/v2/audiences?project_id={project_id}
List Events
GET https://api.optimizely.com/v2/events?project_id={project_id}
List Pages
GET https://api.optimizely.com/v2/pages?project_id={project_id}
Key Metrics
Experiment Results
variation_id- Variation identifiervariation_name- Variation display namevisitors- Unique visitors per variationconversions- Conversion countconversion_rate- Rate as decimalimprovement- Percentage improvement vs. controlstatistical_significance- Confidence levelis_baseline- Whether this is the control
Experiment Properties
name- Experiment namestatus- not_started, running, paused, archivedtype- a/b, multivariate, personalizationtraffic_allocation- Percentage of traffic (0-10000 = 0-100%)variations- Array of variations with weights
Parameters
List Experiments
project_id(required) - Project to list experiments forpage- Page numberper_page- Results per page (default: 25)status- Filter by status
Get Results
start_time- Results start time (ISO 8601)end_time- Results end time (ISO 8601)
Create Experiment
project_id(required) - Parent projectname(required) - Experiment nametype- Experiment type (default: a/b)variations(required) - Array of variations with name and weightmetrics- Array of metric/event configurationsaudience_conditions- Targeting conditionstraffic_allocation- Traffic percentage (0-10000)
When to Use
- Running A/B tests on web pages and features
- Managing experimentation programs at scale
- Pulling experiment results for analysis
- Automating experiment creation and monitoring
- Feature flag management
- Personalization campaigns
Rate Limits
- 50 requests/second per personal token
- Pagination via
pageandper_pageparameters - OpenAPI spec available at https://api.optimizely.com/v2/swagger.json
Relevant Skills
- ab-testing
- cro
- landing-page
- personalization
- analytics