Ab Testing
coreyhaines31/marketingskills
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program.
Implement the Entrepreneurial Operating System (EOS) to align vision and execution across a company.
$ npx skills add wondelai/skills --skill traction-eos -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install wondelai/skills traction-eos --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/wondelai/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/traction-eos .claude/skills/traction-eos && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "traction-eos" agent skill from https://github.com/wondelai/skills/tree/main/traction-eos into .claude/skills/traction-eos/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "traction-eos", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/wondelai/skills/tree/main/traction-eosType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add wondelai/skills --skill traction-eos -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install wondelai/skills traction-eos --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/wondelai/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/traction-eos .agents/skills/traction-eos && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "traction-eos" agent skill from https://github.com/wondelai/skills/tree/main/traction-eos into .agents/skills/traction-eos/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "traction-eos", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add wondelai/skills --skill traction-eos -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install wondelai/skills traction-eos --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/wondelai/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/traction-eos .cursor/skills/traction-eos && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "traction-eos" agent skill from https://github.com/wondelai/skills/tree/main/traction-eos into .cursor/skills/traction-eos/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "traction-eos", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/wondelai/skills.git --path traction-eos--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add wondelai/skills --skill traction-eos -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install wondelai/skills traction-eos --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/wondelai/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/traction-eos .gemini/skills/traction-eos && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "traction-eos" agent skill from https://github.com/wondelai/skills/tree/main/traction-eos into .gemini/skills/traction-eos/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "traction-eos", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install wondelai/skills traction-eosInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add wondelai/skills --skill traction-eos -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/wondelai/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/traction-eos .github/skills/traction-eos && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "traction-eos" agent skill from https://github.com/wondelai/skills/tree/main/traction-eos into .github/skills/traction-eos/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "traction-eos", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add wondelai/skills --skill traction-eos -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install wondelai/skills traction-eos --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/wondelai/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/traction-eos .opencode/skills/traction-eos && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "traction-eos" agent skill from https://github.com/wondelai/skills/tree/main/traction-eos into .opencode/skills/traction-eos/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "traction-eos", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
traction-eosImplement the Entrepreneurial Operating System (EOS) to align vision and execution across a company.
Traction Eos is an agent skill from wondelai/skills. Implement the Entrepreneurial Operating System (EOS) to align vision and execution across a company. Use when the user mentions "EOS", "Entrepreneurial Operating System", "V/TO", "quarterly rocks", "Level 10 meetings", "accountability chart", "IDS process", "my company feels chaotic", "we keep having the same problems", or "get the whole team aligned". Also trigger when a growing company needs meeting structure, goal-setting frameworks, or a systematic way to solve recurring organizational issues. Covers the six…
Its SKILL.md is about 3.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 10 other files, including reference files (for example `references/case-studies.md`, `references/data.md` and `references/implementation.md`).
It sits in Marketing & SEO, covering A/B testing. The repository describes itself as: Wondel.ai Agent Skills — Business, Marketing, UX & Coding Frameworks from Bestselling Books. 50 skills + 12 guided journeys for Claude Code, Codex, Cursor & other agentskills.io… The licence is MIT.
6 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit c172996. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Links to these hosts (documentation or services it may open):
amazon.comFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Traction Eos loads about 3.5k tokens when it runs, and up to ~36k if it reads all its reference files. Until then it costs about 172 tokens; SKILL.md has 1,703 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from wondelai/skills at commit c172996, republished under its MIT licence (© wondelai). 1,703 words, ~3,533 tokens.
.claude/skills/traction-eos/SKILL.md (or your agent's skills folder). This skill also uses 9 other files; get the full folder from GitHub.A complete system for running a business with six key components. Designed for entrepreneurial companies ($2M-$50M revenue, 10-250 employees) that want to align vision and execution.
Most businesses suffer from the same core issues: people, vision, traction. Great vision without traction is hallucination; traction without vision is aimless. EOS connects the two through a practical weekly operating rhythm that strengthens the Six Key Components of any organization.
Goal: 10/10. Score the business by how many of the six Quick Diagnostic rows pass (each component is either in place or not), mapped to the bands below. Bands: 9-10 = all six diagnostic rows pass and rocks consistently hit 80%+ completion; 7-8 = five rows pass, one component weak; 5-6 = three to four rows pass; 3-4 = one to two rows pass; <=2 = no operating rhythm in place. Always state the current score, the failing diagnostic rows, and the next action for each.
Vision → People → Data → Issues → Process → TractionQuestion: Does everyone in the organization know where you're going and how you plan to get there?
Tool: Vision/Traction Organizer (V/TO) — answers eight questions on two pages:
| Question | What It Defines | Example |
|---|---|---|
| Core Values | 3-7 non-negotiable beliefs | "Own it", "Do the right thing", "Grow or die" |
| Core Focus | Purpose/cause/passion + niche | "Simplify small business" + "Cloud accounting" |
| 10-Year Target | Big, hairy, audacious goal | "$100M revenue" or "10,000 customers" |
| Marketing Strategy | Target market, 3 uniques, proven process, guarantee | Who you serve, why you're different |
| 3-Year Picture | What the company looks like in 3 years | Revenue, profit, headcount, key metrics |
| 1-Year Plan | Revenue, profit, measurables, goals | Specific targets for this year |
| Quarterly Rocks | 3-7 priorities for this quarter | Most important things in 90 days |
| Issues List | All unresolved obstacles | Problems, ideas, opportunities |
Process: Leadership completes the V/TO together (2-day off-site), shares it with the entire organization, reviews quarterly, updates annually.
Key insight: If the leadership team can't agree on the V/TO, you have a bigger problem — alignment comes first.
See references/vto.md when filling in the V/TO — the eight-question template and the off-site exercise sequence.
Question: Do you have the right people in the right seats?
Tool: Accountability Chart — not an org chart; it defines the structure and who owns what.
Visionary ←→ Integrator
├── Sales/Marketing
├── Operations
└── FinanceTool: People Analyzer — evaluate every person on two dimensions:
People decisions:
See references/people.md when building the accountability chart or running People Analyzer — templates plus GWC scoring guidance.
Question: Are you managing based on objective data, or subjective opinions?
Tool: Scorecard — a weekly report card of 5-15 numbers that tell you how the business is doing. Weekly data spots problems 2-4 weeks earlier than monthly and replaces gut-feel management with accountability.
Scorecard rules:
Example:
| Metric | Owner | Goal | W1 | W2 | W3 | W4 |
|---|---|---|---|---|---|---|
| Revenue | Sales Lead | $50K/wk | ✓ | ✓ | ✗ | ✓ |
| New Leads | Marketing | 100/wk | ✓ | ✗ | ✓ | ✓ |
| Cash Balance | Finance | >$200K | ✓ | ✓ | ✓ | ✓ |
Metric selection: If you had to go on vacation for 4 weeks, what 5-15 numbers would tell you how the business is doing?
See references/data.md when building the scorecard — templates plus how to pick leading-indicator metrics.
Question: Are you identifying, discussing, and solving issues quickly?
Tool: Issues Solving Track (IDS) — Identify → Discuss → Solve:
Three types of issues:
| Type | Examples | Action |
|---|---|---|
| Problems | Customer churn, team conflict, outage | IDS → solve |
| Ideas | New feature, process change, opportunity | IDS → decide (yes/no/later) |
| Obstacles | Blocked rock, resource constraint | IDS → remove or escalate |
Issues list rules: Anyone can add issues; prioritize most important first; unsolved issues carry forward — not everything gets solved each meeting.
Common IDS failures: discussing symptoms instead of root cause, rehashing the same issue weekly, ending without clear action items.
See references/issues.md when facilitating IDS — a Five Whys worked example and tangent-control tactics.
Question: Have you documented and consistently followed your core processes?
Tool: Core Process Documentation — the 20/80 rule: document 20% of your processes to get 80% consistency.
Core processes to identify: HR (hiring, onboarding, reviews), sales (lead → close), operations (delivery, fulfillment), customer service (support → resolution), finance (invoicing, collections).
Documentation format: Name the process, list 5-20 major steps with just enough detail (not a 50-page manual), make it visual where possible.
Example: Sales Process "The Closer"
Followed By All (FBA): Document it, train on it, measure compliance, update quarterly.
See references/process.md when documenting a core process — full templates and a worked HR/sales/ops example.
Question: Are you executing on your vision every day?
The 3-7 most important things to accomplish in the next 90 days. Ninety days is long enough to achieve something meaningful, short enough to maintain urgency.
Rock-setting process:
SMART rocks: Specific ("Launch new pricing page", not "improve pricing"), Measurable (clear completion criteria), Achievable in 90 days, Realistic given resources, Time-bound (due end of quarter).
Rock scoring: Done = checked off (no partial credit); not done = carried forward or dropped. Target 80%+ completion. Beware rocks that are just "business as usual" — they don't move the needle.
See references/rocks.md when setting quarterly rocks — the binary done-test, the nine-row mistakes table, and a mid-quarter check-in.
The most important meeting in EOS. Every week, same day, same time, same agenda — 90 minutes, never longer.
| Time | Section | Purpose |
|---|---|---|
| 5 min | Segue | Good news, personal and professional |
| 5 min | Scorecard | Review weekly numbers |
| 5 min | Rock Review | On track / off track per rock |
| 5 min | Headlines | Customer/employee quick updates |
| 5 min | To-Do List | Last week's to-dos: done or not done |
| 60 min | IDS | Identify, Discuss, Solve issues |
| 5 min | Conclude | Recap to-dos, rate meeting 1-10 |
Rules:
See references/level-10.md when running or fixing a Level 10 — facilitation script and how to interpret the meeting rating.
Typical rollout: 2 years to full implementation.
| Phase | Timeline | Focus |
|---|---|---|
| Focus Day | Day 1 (8 hours) | Accountability chart, rocks, scorecard, Level 10 |
| Vision Building Day 1 | Month 1 | V/TO: core values, core focus, 10-year target |
| Vision Building Day 2 | Month 2 | V/TO: marketing strategy, 3-year, 1-year, rocks |
| Quarterly Sessions | Every 90 days | Review rocks, set new rocks, IDS major issues |
| Annual Planning | Yearly | Full V/TO review, 1-year plan, Q1 rocks |
Self-implementation (read the book, follow the tools — free, slower) vs. EOS Implementer (certified facilitator — faster, expensive).
See references/implementation.md when planning the rollout — phase-by-phase sequencing and the self-vs-Implementer decision. For examples of how real companies sequenced it, see references/case-studies.md.
Rate the company 1-5 on each statement:
| Component | Statement | Score (1-5) |
|---|---|---|
| Vision | Leadership team agrees on where we're going and how to get there | |
| People | We have the right people in the right seats | |
| Data | We manage from a weekly scorecard of 5-15 numbers | |
| Issues | We solve issues quickly and permanently | |
| Process | Core processes are documented and followed by all | |
| Traction | We set and achieve 90-day priorities (rocks) |
Scoring: 25-30 strong (fine-tune) | 20-24 good (close gaps) | 15-19 average (significant work) | below 15 weak (consider an EOS Implementer).
| Mistake | Why It Fails | Fix |
|---|---|---|
| Skipping Level 10s | Weekly rhythm lost, issues pile up | Protect the meeting, never cancel |
| No scorecard | Managing by gut, constant surprises | Choose 5-15 weekly numbers |
| Wrong people kept | Drags the entire team down | People Analyzer, make the tough calls |
| V/TO not shared | Team doesn't know the vision | Share with the entire company |
For rock-specific mistakes (too many, too vague, business-as-usual, mid-quarter changes), see references/rocks.md — full nine-row table with fixes.
| Question | If No | Action |
|---|---|---|
| Does leadership agree on vision? | Misalignment | Complete the V/TO together |
| Right people in right seats? | Performance issues | People Analyzer on all seats |
| Managing from data weekly? | Reactive management | Build a weekly scorecard |
| Issues solved permanently? | Same problems repeat | IDS in Level 10s |
| Core processes documented? | Inconsistency | Document the top 5 processes |
| 90-day priorities set and tracked? | No traction | Set quarterly rocks |
For the complete system:
Gino Wickman is the creator of EOS and founder of EOS Worldwide, a community of certified Implementers. Traction has sold over 2 million copies, and EOS is used by more than 250,000 companies worldwide. His work focuses on the practical tools entrepreneurial leadership teams need to get real traction.
© wondelai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 9 other files (references) in traction-eos of wondelai/skills.
Open the folder on GitHubat commit c172996
Traction Eos next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Traction Eos this skillwondelai/skills | 2.4k | — | ~3.5k | Automated safety check: Pass | MIT | |
| Ab Testingcoreyhaines31/marketingskills | 54k | 3 repos | ~2.8k | Automated safety check: Pass | MIT | |
| AnalyticsNexus-JPF/note-companion | 870 | 7 repos | ~2.2k | Automated safety check: Pass | MIT | |
| Ab Test Setupfreekmurze/dotfiles | 1k | 15 repos | ~1.8k | Automated safety check: Pass | None | |
| Ad Test Designeraaron-he-zhu/aaron-marketing-skills | 2.9k | 2 repos | ~2.8k | Automated safety check: Pass | Apache-2.0 | |
| Meta Tags Optimizernowork-studio/notfair-plugin | 3.9k | 1 repos | ~2.7k | Automated safety check: Pass | MIT |
coreyhaines31/marketingskills
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program.
Nexus-JPF/note-companion
When the user wants to set up, improve, or audit analytics tracking and measurement.
freekmurze/dotfiles
When the user wants to plan, design, or implement an A/B test or experiment.
aaron-he-zhu/aaron-marketing-skills
A skill your agent uses when the user asks to "design an A/B test", "set up a creative/landing test", "run an incrementality test", or "is this result statistically and practically material?"…
nowork-studio/notfair-plugin
Writes and improves title tags, meta descriptions, Open Graph and Twitter card tags for click-through, with character counts and A/B test variants.
irinabuht12-oss/marketing-skills
Statistical significance calculator for A/B test results with sample size requirements, segment breakdowns, and hypothesis generation.
wondelai/skills
Navigate the technology adoption lifecycle from early adopters to mainstream market.
wondelai/skills
Apply foundational design principles: affordances, signifiers, constraints, feedback, and conceptual models.
wondelai/skills
Run a structured 5-day process to prototype, test, and validate product ideas with real users.
wondelai/skills
Design habit-forming product loops using the Hook Model (Trigger, Action, Variable Reward, Investment).
wondelai/skills
Diagnose and fix retention problems using behavior design (B=MAP).
wondelai/skills
Design products and pricing around validated willingness to pay, from Ramanujam & Tacke's "Monetizing Innovation".
Categories
Implement the Entrepreneurial Operating System (EOS) to align vision and execution across a company. Traction Eos is an agent skill from wondelai/skills. Implement the Entrepreneurial Operating System (EOS) to align vision and execution across a company.
Traction Eos fits situations like: the user mentions EOS; entrepreneurial Operating System; quarterly rocks; level 10 meetings.
Run `npx skills add wondelai/skills --skill traction-eos -a claude-code`. Or copy the skill folder (traction-eos in wondelai/skills) into .claude/skills/traction-eos in your project. Claude Code loads it when a task matches its description.
Run `npx skills add wondelai/skills --skill traction-eos -a codex`. Or copy the skill folder (traction-eos in wondelai/skills) into .agents/skills/traction-eos in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add wondelai/skills --skill traction-eos -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/traction-eos, .gemini/skills/traction-eos, .github/skills/traction-eos and .opencode/skills/traction-eos in your project.
SKILL.md names no scripts, command-line tools or credentials: Traction Eos is instructions for the agent only.
SKILL.md names 1 domain. As links in the text: amazon.com. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Traction Eos is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 3.5k tokens (SKILL.md is roughly 14k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 32k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Traction Eos: Ab Testing (coreyhaines31/marketingskills, 54k stars), Analytics (Nexus-JPF/note-companion, 870 stars), Ab Test Setup (freekmurze/dotfiles, 1k stars) and Ad Test Designer (aaron-he-zhu/aaron-marketing-skills, 2.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
wondelai (a GitHub organization) maintains it in wondelai/skills, which has 2,356 GitHub stars. The repository holds 61 skills in this directory. The repository was last updated on September 10, 2026.
Source: wondelai/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.