[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73CRC8104DCBYVST2CHKJQ5":3,"skill-same:01M73CRC8104DCBYVST2CHKJQ5":86},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":6,"updatedAt":33,"install":34,"resources":47},"01M73CRC8104DCBYVST2CHKJQ5","traction-eos",null,"Implement the Entrepreneurial Operating System (EOS) to align vision and execution across a company. Use when the user mentions \"EOS\", \"V\u002FTO\", \"quarterly rocks\", \"Level 10 meetings\", \"accountability chart\", \"IDS process\", \"Entrepreneurial Operating System\", or \"business operating system\". Also trigger when a growing company needs meeting structure, goal-setting frameworks, or a systematic approach to solving recurring organizational issues. Covers the six EOS components: Vision, People, Data, Issues, Process, Traction. For team motivation design, see drive-motivation. For lean experimentation, see lean-startup.","roohe\u002Fagentic-super-skills","roohe","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F99054084?v=4","01M734WCDFP6RZVT5CNM00QR26","01M734WCE4BD0T4NZS5PCV9V5F",10,"MIT","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Ftraction-eos\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: traction-eos\ndescription: 'Implement the Entrepreneurial Operating System (EOS) to align vision and execution across a company. Use when the user mentions \"EOS\", \"V\u002FTO\", \"quarterly rocks\", \"Level 10 meetings\", \"accountability chart\", \"IDS process\", \"Entrepreneurial Operating System\", or \"business operating system\". Also trigger when a growing company needs meeting structure, goal-setting frameworks, or a systematic approach to solving recurring organizational issues. Covers the six EOS components: Vision, People, Data, Issues, Process, Traction. For team motivation design, see drive-motivation. For lean experimentation, see lean-startup.'\nlicense: MIT\nmetadata:\n  author: wondelai\n  version: \"1.1.0\"\n---\n\n# Entrepreneurial Operating System (EOS)\n\nA 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.\n\n## Core Principle\n\n**Most businesses suffer from the same core issues: people, vision, traction.** EOS provides a simple, complete operating system that strengthens the Six Key Components of any organization.\n\n**The foundation:** Great vision without traction is hallucination. Traction without vision is aimless. EOS connects the two through a practical, weekly operating rhythm.\n\n## Scoring\n\n**Goal: 10\u002F10.** When evaluating or implementing business processes, rate 0-10 based on EOS component strength. A 10\u002F10 means all six components are strong, meetings are productive, and quarterly rocks are consistently achieved; lower scores indicate gaps. Always provide current score and improvements to reach 10\u002F10.\n\n## The Six Key Components\n\n```\nVision → People → Data → Issues → Process → Traction\n```\n\nEvery business is built on these six components. EOS strengthens all six.\n\n### 1. Vision Component\n\n**Question:** Does everyone in the organization know where you're going and how you plan to get there?\n\n**Tool: Vision\u002FTraction Organizer (V\u002FTO)**\n\nThe V\u002FTO answers eight questions on two pages:\n\n| Question | What It Defines | Example |\n|----------|----------------|---------|\n| **Core Values** | 3-7 non-negotiable beliefs | \"Own it\", \"Do the right thing\", \"Grow or die\" |\n| **Core Focus** | Purpose\u002Fcause\u002Fpassion + niche | \"Simplify small business\" + \"Cloud accounting\" |\n| **10-Year Target** | Big, hairy, audacious goal | \"$100M revenue\" or \"10,000 customers\" |\n| **Marketing Strategy** | Target market, 3 uniques, proven process, guarantee | Who you serve, why you're different |\n| **3-Year Picture** | What company looks like in 3 years | Revenue, profit, headcount, key metrics |\n| **1-Year Plan** | Revenue, profit, measurables, goals | Specific targets for this year |\n| **Quarterly Rocks** | 3-7 priorities for this quarter | The most important things to accomplish in 90 days |\n| **Issues List** | All unresolved obstacles | Problems, ideas, opportunities to discuss |\n\n**Process:**\n1. Leadership team completes V\u002FTO together (2-day off-site)\n2. Share with entire organization\n3. Review quarterly\n4. Update annually\n\n**Key insight:** If leadership team can't agree on V\u002FTO, you have a bigger problem. Alignment comes first.\n\nSee: [references\u002Fvto.md](references\u002Fvto.md) for V\u002FTO templates and exercises.\n\n### 2. People Component\n\n**Question:** Do you have the right people in the right seats?\n\n**Tool: Accountability Chart**\n\nNot an org chart—an accountability chart. Defines the structure and who owns what.\n\n**Structure:**\n```\nVisionary ←→ Integrator\n              ├── Sales\u002FMarketing\n              ├── Operations\n              └── Finance\n```\n\n**Two key roles:**\n- **Visionary:** Big ideas, culture, key relationships, creative problem solving\n- **Integrator:** Runs business day-to-day, manages team, executes vision, resolves conflicts\n\n**Rule:** One person per seat. No shared accountability.\n\n**Tool: People Analyzer**\n\nEvaluate every person on two dimensions:\n\n**1. Right Person (core values fit)**\n\n| Core Value | + (most of the time) | +\u002F- (sometimes) | - (rarely) |\n|-----------|---------------------|-----------------|------------|\n| Own it | + | | |\n| Do the right thing | | +\u002F- | |\n| Grow or die | + | | |\n\n**Standard:** Must be \"+\" on all core values. One \"+\u002F-\" is a conversation. Any \"-\" is wrong person.\n\n**2. Right Seat (GWC)**\n- **G**et it: Understands the role\n- **W**ant it: Genuinely wants the role\n- **C**apacity: Has the mental, physical, emotional capacity\n\n**Must be \"yes\" on all three.** If missing any one, wrong seat.\n\n**The formula:** Right People + Right Seats = A-players\n\n**People decisions:**\n- Right person, right seat → Keep and invest in\n- Right person, wrong seat → Move to right seat\n- Wrong person, right seat → Coaching\u002Fexit (hardest call)\n- Wrong person, wrong seat → Exit immediately\n\nSee: [references\u002Fpeople.md](references\u002Fpeople.md) for accountability chart and people analyzer templates.\n\n### 3. Data Component\n\n**Question:** Are you managing based on objective data, or subjective opinions?\n\n**Tool: Scorecard**\n\nA weekly report card of 5-15 numbers that tell you how the business is doing.\n\n**Scorecard rules:**\n- Activity-based metrics (leading indicators), not results (lagging)\n- Weekly numbers (monthly is too slow)\n- Every number has an owner\n- Every number has a goal\n- Red\u002Fgreen: on track or off track\n\n**Example Scorecard:**\n\n| Metric | Owner | Goal | W1 | W2 | W3 | W4 |\n|--------|-------|------|----|----|----|----|\n| Revenue | Sales Lead | $50K\u002Fwk | ✓ | ✓ | ✗ | ✓ |\n| New Leads | Marketing | 100\u002Fwk | ✓ | ✗ | ✓ | ✓ |\n| Demos Completed | Sales | 20\u002Fwk | ✗ | ✓ | ✓ | ✓ |\n| Customer NPS | Support | >50 | ✓ | ✓ | ✓ | ✓ |\n| Cash Balance | Finance | >$200K | ✓ | ✓ | ✓ | ✓ |\n\n**Benefits:**\n- Spot problems 2-4 weeks earlier\n- Reduce \"gut feeling\" management\n- Create accountability without micromanagement\n- Everyone knows the score\n\n**Metric selection:** If you had to go on vacation for 4 weeks, what 5-15 numbers would tell you how the business is doing?\n\nSee: [references\u002Fdata.md](references\u002Fdata.md) for scorecard templates and metric selection.\n\n### 4. Issues Component\n\n**Question:** Are you identifying, discussing, and solving issues quickly?\n\n**Tool: Issues Solving Track (IDS)**\n\n**I**dentify → **D**iscuss → **S**olve\n\n**Step 1: Identify**\n- What's the real issue? (Not the symptom)\n- Ask \"Why?\" until you reach root cause\n- State the issue in one sentence\n\n**Step 2: Discuss**\n- Everyone gets input (not equal time)\n- Tangents are stopped\n- Focus on the ONE issue\n- Time-boxed (usually 5-15 minutes)\n\n**Step 3: Solve**\n- Decision is made\n- Action items are assigned (who + what + when)\n- Move to next issue\n\n**Three types of issues:**\n\n| Type | Examples | Action |\n|------|----------|--------|\n| **Problems** | Customer churn, team conflict, system outage | IDS → solve |\n| **Ideas** | New feature, process change, market opportunity | IDS → decide (yes\u002Fno\u002Flater) |\n| **Obstacles** | Blocking a rock, resource constraint, dependency | IDS → remove or escalate |\n\n**Issues list rules:**\n- Everyone can add issues\n- Prioritize: most important first\n- Not all issues get solved every meeting\n- Unsolved issues carry forward\n\n**Common IDS mistakes:**\n- Discussing symptoms, not root cause\n- Rehashing same issue every week\n- No clear action items\n- Too much discussion, not enough solving\n\nSee: [references\u002Fissues.md](references\u002Fissues.md) for IDS facilitation guides.\n\n### 5. Process Component\n\n**Question:** Have you documented and consistently followed your core processes?\n\n**Tool: Core Process Documentation**\n\n**The 20\u002F80 rule:** Document 20% of your processes to get 80% consistency.\n\n**Identify core processes:**\n- HR process (hiring, onboarding, reviews)\n- Sales process (lead → close)\n- Operations process (delivery, fulfillment)\n- Customer service process (support → resolution)\n- Finance process (invoicing, collections)\n\n**Documentation format:**\n1. Name the process\n2. List 5-20 major steps\n3. Add just enough detail (not a 50-page manual)\n4. Make it visual where possible\n\n**Example: Sales Process \"The Closer\"**\n1. Qualify lead (BANT: Budget, Authority, Need, Timeline)\n2. Discovery call (30 min, use question guide)\n3. Demo (customize to their pain points)\n4. Proposal (send within 24 hours)\n5. Follow up (3 touches in 7 days)\n6. Close or disqualify\n\n**Followed By All (FBA):**\n- Document it\n- Train on it\n- Measure compliance\n- Update quarterly\n\nSee: [references\u002Fprocess.md](references\u002Fprocess.md) for process documentation templates.\n\n### 6. Traction Component\n\n**Question:** Are you executing on your vision every day?\n\n**Two tools: Rocks and Level 10 Meetings**\n\n#### Rocks (Quarterly Priorities)\n\n**Definition:** The 3-7 most important things to accomplish in the next 90 days.\n\n**Why 90 days?**\n- Long enough to accomplish something meaningful\n- Short enough to maintain urgency\n- Natural human rhythm for focus\n\n**Rock-setting process:**\n1. Review V\u002FTO (vision, 3-year, 1-year)\n2. Brainstorm: \"What must get done this quarter to stay on track?\"\n3. Narrow to 3-7 company rocks\n4. Assign each rock to one owner\n5. Each leadership member also has 3-7 individual rocks\n6. Share with entire organization\n7. Track weekly\n\n**SMART rocks:**\n- **S**pecific: \"Launch new pricing page\" not \"improve pricing\"\n- **M**easurable: Clear completion criteria\n- **A**chievable: Can be done in 90 days\n- **R**ealistic: Given current resources\n- **T**ime-bound: Due end of quarter\n\n**Rock scoring:**\n- **Done** = checked off (no partial credit)\n- **Not done** = carried forward or dropped\n- **Goal:** 80%+ completion rate\n\n**Anti-patterns:**\n- Too many rocks (>7) → Focus is diluted\n- Rocks too vague → Can't tell if done\n- No owner → Nobody accountable\n- All rocks are \"business as usual\" → Not moving the needle\n\nSee: [references\u002Frocks.md](references\u002Frocks.md) for rock-setting exercises.\n\n#### Level 10 Meeting (Weekly Leadership Meeting)\n\n**The most important meeting in EOS.** Runs every week, same day, same time, same agenda.\n\n**Duration:** 90 minutes, never longer.\n\n**Agenda:**\n\n| Time | Section | Purpose |\n|------|---------|---------|\n| 5 min | **Segue** | Good news (personal and professional) |\n| 5 min | **Scorecard** | Review weekly numbers |\n| 5 min | **Rock Review** | On track \u002F Off track for each rock |\n| 5 min | **Customer\u002FEmployee Headlines** | Quick updates |\n| 5 min | **To-Do List** | Review last week's to-dos (done or not done) |\n| 60 min | **IDS** | Identify, Discuss, Solve issues |\n| 5 min | **Conclude** | Recap to-dos, rate meeting 1-10 |\n\n**Level 10 meeting rules:**\n- Starts on time, ends on time (non-negotiable)\n- Same day, same time every week\n- No phones\u002Flaptops (except for agenda)\n- IDS gets 60 of 90 minutes (most important part)\n- Rate meeting 1-10 at end (target: 8+)\n- If below 8, discuss what to improve\n\n**Why \"Level 10\"?**\n- Every meeting is rated 1-10 by participants\n- Goal is to consistently achieve 10\u002F10\n\n**To-Do rules:**\n- 7-day action items only\n- Each has owner and due date\n- Done = 100% complete\n- 90%+ completion rate is target\n\nSee: [references\u002Flevel-10.md](references\u002Flevel-10.md) for meeting facilitation guides.\n\n## EOS Implementation Timeline\n\n**Typical rollout: 2 years to full implementation**\n\n| Phase | Timeline | Focus |\n|-------|----------|-------|\n| **Focus Day** | Day 1 (8 hours) | Accountability chart, rocks, scorecard, Level 10 |\n| **Vision Building Day 1** | Month 1 | V\u002FTO: core values, core focus, 10-year target |\n| **Vision Building Day 2** | Month 2 | V\u002FTO: marketing strategy, 3-year, 1-year, rocks |\n| **Quarterly Sessions** | Every 90 days | Review rocks, set new rocks, IDS major issues |\n| **Annual Planning** | Yearly | Full V\u002FTO review, set 1-year plan, Q1 rocks |\n\n**Self-implementation vs. EOS Implementer:**\n- Self: Read the book, follow the tools (free, slower)\n- EOS Implementer: Certified facilitator guides the process (faster, expensive)\n\n## Organizational Checkup\n\nRate your company 1-5 on each statement:\n\n| Component | Statement | Score (1-5) |\n|-----------|-----------|-------------|\n| **Vision** | Leadership team is on the same page with where we're going and how to get there | |\n| **People** | We have the right people in the right seats | |\n| **Data** | We manage from a weekly scorecard of 5-15 numbers | |\n| **Issues** | We solve issues quickly and permanently | |\n| **Process** | Core processes are documented and followed by all | |\n| **Traction** | We set and achieve 90-day priorities (rocks) | |\n\n**Scoring:**\n- 25-30: Strong (maintain and fine-tune)\n- 20-24: Good (close gaps)\n- 15-19: Average (significant work needed)\n- Below 15: Weak (consider EOS implementer)\n\n## Common Mistakes\n\n| Mistake | Why It Fails | Fix |\n|---------|-------------|------|\n| **Skipping Level 10s** | Lose weekly rhythm, issues pile up | Protect meeting, never cancel |\n| **Too many rocks** | No focus, nothing gets done | Max 7 company rocks, 3-7 per person |\n| **Vague rocks** | Can't tell if done | Write SMART rocks with clear criteria |\n| **No scorecard** | Managing by gut, surprises | Choose 5-15 weekly numbers |\n| **Wrong people kept** | Drags entire team down | Use People Analyzer, make tough calls |\n| **V\u002FTO not shared** | Team doesn't know the vision | Share with entire company |\n\n## Quick Diagnostic\n\nAudit any business:\n\n| Question | If No | Action |\n|----------|-------|--------|\n| Does leadership agree on vision? | Misalignment | Complete V\u002FTO together |\n| Right people in right seats? | Performance issues | People Analyzer on all seats |\n| Managing from data weekly? | Reactive management | Build weekly scorecard |\n| Issues solved permanently? | Same problems repeat | Implement IDS in Level 10s |\n| Core processes documented? | Inconsistency | Document top 5 processes |\n| 90-day priorities set and tracked? | No traction | Set quarterly rocks |\n\n## Reference Files\n\n- [vto.md](references\u002Fvto.md): Vision\u002FTraction Organizer templates, eight questions\n- [people.md](references\u002Fpeople.md): Accountability chart, People Analyzer, GWC\n- [data.md](references\u002Fdata.md): Scorecard templates, metric selection\n- [issues.md](references\u002Fissues.md): IDS process, facilitation, issue types\n- [process.md](references\u002Fprocess.md): Core process documentation templates\n- [rocks.md](references\u002Frocks.md): Rock-setting exercises, SMART rocks\n- [level-10.md](references\u002Flevel-10.md): Meeting agenda, facilitation, rating\n- [implementation.md](references\u002Fimplementation.md): EOS rollout timeline, self-implementation guide\n- [case-studies.md](references\u002Fcase-studies.md): Companies that implemented EOS successfully\n\n## Further Reading\n\nThis skill is based on the Entrepreneurial Operating System developed by Gino Wickman. For the complete system:\n\n- [*\"Traction: Get a Grip on Your Business\"*](https:\u002F\u002Fwww.amazon.com\u002FTraction-Get-Grip-Your-Business\u002Fdp\u002F1936661837?tag=wondelai00-20) by Gino Wickman\n- [*\"Get a Grip\"*](https:\u002F\u002Fwww.amazon.com\u002FGet-Grip-Entrepreneurial-Fable-Business\u002Fdp\u002F1939529824?tag=wondelai00-20) by Gino Wickman & Mike Paton (EOS as a business fable)\n- [*\"Rocket Fuel\"*](https:\u002F\u002Fwww.amazon.com\u002FRocket-Fuel-Essential-Combination-Business\u002Fdp\u002F1941631150?tag=wondelai00-20) by Gino Wickman & Mark C. Winters (Visionary + Integrator relationship)\n\n## About the Author\n\n**Gino Wickman** is the creator of EOS (Entrepreneurial Operating System) and founder of EOS Worldwide, a community of certified EOS Implementers who help companies implement the system. Wickman has worked with thousands of entrepreneurial leadership teams and has helped them get real traction. *Traction* has sold over 2 million copies and EOS is used by over 250,000 companies worldwide. His work focuses on the practical tools needed to run an entrepreneurial company.\n","# Entrepreneurial Operating System (EOS)\n\nA 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.\n\n## Core Principle\n\n**Most businesses suffer from the same core issues: people, vision, traction.** EOS provides a simple, complete operating system that strengthens the Six Key Components of any organization.\n\n**The foundation:** Great vision without traction is hallucination. Traction without vision is aimless. EOS connects the two through a practical, weekly operating rhythm.\n\n## Scoring\n\n**Goal: 10\u002F10.** When evaluating or implementing business processes, rate 0-10 based on EOS component strength. A 10\u002F10 means all six components are strong, meetings are productive, and quarterly rocks are consistently achieved; lower scores indicate gaps. Always provide current score and improvements to reach 10\u002F10.\n\n## The Six Key Components\n\n```\nVision → People → Data → Issues → Process → Traction\n```\n\nEvery business is built on these six components. EOS strengthens all six.\n\n### 1. Vision Component\n\n**Question:** Does everyone in the organization know where you're going and how you plan to get there?\n\n**Tool: Vision\u002FTraction Organizer (V\u002FTO)**\n\nThe V\u002FTO answers eight questions on two pages:\n\n| Question | What It Defines | Example |\n|----------|----------------|---------|\n| **Core Values** | 3-7 non-negotiable beliefs | \"Own it\", \"Do the right thing\", \"Grow or die\" |\n| **Core Focus** | Purpose\u002Fcause\u002Fpassion + niche | \"Simplify small business\" + \"Cloud accounting\" |\n| **10-Year Target** | Big, hairy, audacious goal | \"$100M revenue\" or \"10,000 customers\" |\n| **Marketing Strategy** | Target market, 3 uniques, proven process, guarantee | Who you serve, why you're different |\n| **3-Year Picture** | What company looks like in 3 years | Revenue, profit, headcount, key metrics |\n| **1-Year Plan** | Revenue, profit, measurables, goals | Specific targets for this year |\n| **Quarterly Rocks** | 3-7 priorities for this quarter | The most important things to accomplish in 90 days |\n| **Issues List** | All unresolved obstacles | Problems, ideas, opportunities to discuss |\n\n**Process:**\n1. Leadership team completes V\u002FTO together (2-day off-site)\n2. Share with entire organization\n3. Review quarterly\n4. Update annually\n\n**Key insight:** If leadership team can't agree on V\u002FTO, you have a bigger problem. Alignment comes first.\n\nSee: [references\u002Fvto.md](references\u002Fvto.md) for V\u002FTO templates and exercises.\n\n### 2. People Component\n\n**Question:** Do you have the right people in the right seats?\n\n**Tool: Accountability Chart**\n\nNot an org chart—an accountability chart. Defines the structure and who owns what.\n\n**Structure:**\n```\nVisionary ←→ Integrator\n              ├── Sales\u002FMarketing\n              ├── Operations\n              └── Finance\n```\n\n**Two key roles:**\n- **Visionary:** Big ideas, culture, key relationships, creative problem solving\n- **Integrator:** Runs business day-to-day, manages team, executes vision, resolves conflicts\n\n**Rule:** One person per seat. No shared accountability.\n\n**Tool: People Analyzer**\n\nEvaluate every person on two dimensions:\n\n**1. Right Person (core values fit)**\n\n| Core Value | + (most of the time) | +\u002F- (sometimes) | - (rarely) |\n|-----------|---------------------|-----------------|------------|\n| Own it | + | | |\n| Do the right thing | | +\u002F- | |\n| Grow or die | + | | |\n\n**Standard:** Must be \"+\" on all core values. One \"+\u002F-\" is a conversation. Any \"-\" is wrong person.\n\n**2. Right Seat (GWC)**\n- **G**et it: Understands the role\n- **W**ant it: Genuinely wants the role\n- **C**apacity: Has the mental, physical, emotional capacity\n\n**Must be \"yes\" on all three.** If missing any one, wrong seat.\n\n**The formula:** Right People + Right Seats = A-players\n\n**People decisions:**\n- Right person, right seat → Keep and invest in\n- Right person, wrong seat → Move to right seat\n- Wrong person, right seat → Coaching\u002Fexit (hardest call)\n- Wrong person, wrong seat → Exit immediately\n\nSee: [references\u002Fpeople.md](references\u002Fpeople.md) for accountability chart and people analyzer templates.\n\n### 3. Data Component\n\n**Question:** Are you managing based on objective data, or subjective opinions?\n\n**Tool: Scorecard**\n\nA weekly report card of 5-15 numbers that tell you how the business is doing.\n\n**Scorecard rules:**\n- Activity-based metrics (leading indicators), not results (lagging)\n- Weekly numbers (monthly is too slow)\n- Every number has an owner\n- Every number has a goal\n- Red\u002Fgreen: on track or off track\n\n**Example Scorecard:**\n\n| Metric | Owner | Goal | W1 | W2 | W3 | W4 |\n|--------|-------|------|----|----|----|----|\n| Revenue | Sales Lead | $50K\u002Fwk | ✓ | ✓ | ✗ | ✓ |\n| New Leads | Marketing | 100\u002Fwk | ✓ | ✗ | ✓ | ✓ |\n| Demos Completed | Sales | 20\u002Fwk | ✗ | ✓ | ✓ | ✓ |\n| Customer NPS | Support | >50 | ✓ | ✓ | ✓ | ✓ |\n| Cash Balance | Finance | >$200K | ✓ | ✓ | ✓ | ✓ |\n\n**Benefits:**\n- Spot problems 2-4 weeks earlier\n- Reduce \"gut feeling\" management\n- Create accountability without micromanagement\n- Everyone knows the score\n\n**Metric selection:** If you had to go on vacation for 4 weeks, what 5-15 numbers would tell you how the business is doing?\n\nSee: [references\u002Fdata.md](references\u002Fdata.md) for scorecard templates and metric selection.\n\n### 4. Issues Component\n\n**Question:** Are you identifying, discussing, and solving issues quickly?\n\n**Tool: Issues Solving Track (IDS)**\n\n**I**dentify → **D**iscuss → **S**olve\n\n**Step 1: Identify**\n- What's the real issue? (Not the symptom)\n- Ask \"Why?\" until you reach root cause\n- State the issue in one sentence\n\n**Step 2: Discuss**\n- Everyone gets input (not equal time)\n- Tangents are stopped\n- Focus on the ONE issue\n- Time-boxed (usually 5-15 minutes)\n\n**Step 3: Solve**\n- Decision is made\n- Action items are assigned (who + what + when)\n- Move to next issue\n\n**Three types of issues:**\n\n| Type | Examples | Action |\n|------|----------|--------|\n| **Problems** | Customer churn, team conflict, system outage | IDS → solve |\n| **Ideas** | New feature, process change, market opportunity | IDS → decide (yes\u002Fno\u002Flater) |\n| **Obstacles** | Blocking a rock, resource constraint, dependency | IDS → remove or escalate |\n\n**Issues list rules:**\n- Everyone can add issues\n- Prioritize: most important first\n- Not all issues get solved every meeting\n- Unsolved issues carry forward\n\n**Common IDS mistakes:**\n- Discussing symptoms, not root cause\n- Rehashing same issue every week\n- No clear action items\n- Too much discussion, not enough solving\n\nSee: [references\u002Fissues.md](references\u002Fissues.md) for IDS facilitation guides.\n\n### 5. Process Component\n\n**Question:** Have you documented and consistently followed your core processes?\n\n**Tool: Core Process Documentation**\n\n**The 20\u002F80 rule:** Document 20% of your processes to get 80% consistency.\n\n**Identify core processes:**\n- HR process (hiring, onboarding, reviews)\n- Sales process (lead → close)\n- Operations process (delivery, fulfillment)\n- Customer service process (support → resolution)\n- Finance process (invoicing, collections)\n\n**Documentation format:**\n1. Name the process\n2. List 5-20 major steps\n3. Add just enough detail (not a 50-page manual)\n4. Make it visual where possible\n\n**Example: Sales Process \"The Closer\"**\n1. Qualify lead (BANT: Budget, Authority, Need, Timeline)\n2. Discovery call (30 min, use question guide)\n3. Demo (customize to their pain points)\n4. Proposal (send within 24 hours)\n5. Follow up (3 touches in 7 days)\n6. Close or disqualify\n\n**Followed By All (FBA):**\n- Document it\n- Train on it\n- Measure compliance\n- Update quarterly\n\nSee: [references\u002Fprocess.md](references\u002Fprocess.md) for process documentation templates.\n\n### 6. Traction Component\n\n**Question:** Are you executing on your vision every day?\n\n**Two tools: Rocks and Level 10 Meetings**\n\n#### Rocks (Quarterly Priorities)\n\n**Definition:** The 3-7 most important things to accomplish in the next 90 days.\n\n**Why 90 days?**\n- Long enough to accomplish something meaningful\n- Short enough to maintain urgency\n- Natural human rhythm for focus\n\n**Rock-setting process:**\n1. Review V\u002FTO (vision, 3-year, 1-year)\n2. Brainstorm: \"What must get done this quarter to stay on track?\"\n3. Narrow to 3-7 company rocks\n4. Assign each rock to one owner\n5. Each leadership member also has 3-7 individual rocks\n6. Share with entire organization\n7. Track weekly\n\n**SMART rocks:**\n- **S**pecific: \"Launch new pricing page\" not \"improve pricing\"\n- **M**easurable: Clear completion criteria\n- **A**chievable: Can be done in 90 days\n- **R**ealistic: Given current resources\n- **T**ime-bound: Due end of quarter\n\n**Rock scoring:**\n- **Done** = checked off (no partial credit)\n- **Not done** = carried forward or dropped\n- **Goal:** 80%+ completion rate\n\n**Anti-patterns:**\n- Too many rocks (>7) → Focus is diluted\n- Rocks too vague → Can't tell if done\n- No owner → Nobody accountable\n- All rocks are \"business as usual\" → Not moving the needle\n\nSee: [references\u002Frocks.md](references\u002Frocks.md) for rock-setting exercises.\n\n#### Level 10 Meeting (Weekly Leadership Meeting)\n\n**The most important meeting in EOS.** Runs every week, same day, same time, same agenda.\n\n**Duration:** 90 minutes, never longer.\n\n**Agenda:**\n\n| Time | Section | Purpose |\n|------|---------|---------|\n| 5 min | **Segue** | Good news (personal and professional) |\n| 5 min | **Scorecard** | Review weekly numbers |\n| 5 min | **Rock Review** | On track \u002F Off track for each rock |\n| 5 min | **Customer\u002FEmployee Headlines** | Quick updates |\n| 5 min | **To-Do List** | Review last week's to-dos (done or not done) |\n| 60 min | **IDS** | Identify, Discuss, Solve issues |\n| 5 min | **Conclude** | Recap to-dos, rate meeting 1-10 |\n\n**Level 10 meeting rules:**\n- Starts on time, ends on time (non-negotiable)\n- Same day, same time every week\n- No phones\u002Flaptops (except for agenda)\n- IDS gets 60 of 90 minutes (most important part)\n- Rate meeting 1-10 at end (target: 8+)\n- If below 8, discuss what to improve\n\n**Why \"Level 10\"?**\n- Every meeting is rated 1-10 by participants\n- Goal is to consistently achieve 10\u002F10\n\n**To-Do rules:**\n- 7-day action items only\n- Each has owner and due date\n- Done = 100% complete\n- 90%+ completion rate is target\n\nSee: [references\u002Flevel-10.md](references\u002Flevel-10.md) for meeting facilitation guides.\n\n## EOS Implementation Timeline\n\n**Typical rollout: 2 years to full implementation**\n\n| Phase | Timeline | Focus |\n|-------|----------|-------|\n| **Focus Day** | Day 1 (8 hours) | Accountability chart, rocks, scorecard, Level 10 |\n| **Vision Building Day 1** | Month 1 | V\u002FTO: core values, core focus, 10-year target |\n| **Vision Building Day 2** | Month 2 | V\u002FTO: marketing strategy, 3-year, 1-year, rocks |\n| **Quarterly Sessions** | Every 90 days | Review rocks, set new rocks, IDS major issues |\n| **Annual Planning** | Yearly | Full V\u002FTO review, set 1-year plan, Q1 rocks |\n\n**Self-implementation vs. EOS Implementer:**\n- Self: Read the book, follow the tools (free, slower)\n- EOS Implementer: Certified facilitator guides the process (faster, expensive)\n\n## Organizational Checkup\n\nRate your company 1-5 on each statement:\n\n| Component | Statement | Score (1-5) |\n|-----------|-----------|-------------|\n| **Vision** | Leadership team is on the same page with where we're going and how to get there | |\n| **People** | We have the right people in the right seats | |\n| **Data** | We manage from a weekly scorecard of 5-15 numbers | |\n| **Issues** | We solve issues quickly and permanently | |\n| **Process** | Core processes are documented and followed by all | |\n| **Traction** | We set and achieve 90-day priorities (rocks) | |\n\n**Scoring:**\n- 25-30: Strong (maintain and fine-tune)\n- 20-24: Good (close gaps)\n- 15-19: Average (significant work needed)\n- Below 15: Weak (consider EOS implementer)\n\n## Common Mistakes\n\n| Mistake | Why It Fails | Fix |\n|---------|-------------|------|\n| **Skipping Level 10s** | Lose weekly rhythm, issues pile up | Protect meeting, never cancel |\n| **Too many rocks** | No focus, nothing gets done | Max 7 company rocks, 3-7 per person |\n| **Vague rocks** | Can't tell if done | Write SMART rocks with clear criteria |\n| **No scorecard** | Managing by gut, surprises | Choose 5-15 weekly numbers |\n| **Wrong people kept** | Drags entire team down | Use People Analyzer, make tough calls |\n| **V\u002FTO not shared** | Team doesn't know the vision | Share with entire company |\n\n## Quick Diagnostic\n\nAudit any business:\n\n| Question | If No | Action |\n|----------|-------|--------|\n| Does leadership agree on vision? | Misalignment | Complete V\u002FTO together |\n| Right people in right seats? | Performance issues | People Analyzer on all seats |\n| Managing from data weekly? | Reactive management | Build weekly scorecard |\n| Issues solved permanently? | Same problems repeat | Implement IDS in Level 10s |\n| Core processes documented? | Inconsistency | Document top 5 processes |\n| 90-day priorities set and tracked? | No traction | Set quarterly rocks |\n\n## Reference Files\n\n- [vto.md](references\u002Fvto.md): Vision\u002FTraction Organizer templates, eight questions\n- [people.md](references\u002Fpeople.md): Accountability chart, People Analyzer, GWC\n- [data.md](references\u002Fdata.md): Scorecard templates, metric selection\n- [issues.md](references\u002Fissues.md): IDS process, facilitation, issue types\n- [process.md](references\u002Fprocess.md): Core process documentation templates\n- [rocks.md](references\u002Frocks.md): Rock-setting exercises, SMART rocks\n- [level-10.md](references\u002Flevel-10.md): Meeting agenda, facilitation, rating\n- [implementation.md](references\u002Fimplementation.md): EOS rollout timeline, self-implementation guide\n- [case-studies.md](references\u002Fcase-studies.md): Companies that implemented EOS successfully\n\n## Further Reading\n\nThis skill is based on the Entrepreneurial Operating System developed by Gino Wickman. For the complete system:\n\n- [*\"Traction: Get a Grip on Your Business\"*](https:\u002F\u002Fwww.amazon.com\u002FTraction-Get-Grip-Your-Business\u002Fdp\u002F1936661837?tag=wondelai00-20) by Gino Wickman\n- [*\"Get a Grip\"*](https:\u002F\u002Fwww.amazon.com\u002FGet-Grip-Entrepreneurial-Fable-Business\u002Fdp\u002F1939529824?tag=wondelai00-20) by Gino Wickman & Mike Paton (EOS as a business fable)\n- [*\"Rocket Fuel\"*](https:\u002F\u002Fwww.amazon.com\u002FRocket-Fuel-Essential-Combination-Business\u002Fdp\u002F1941631150?tag=wondelai00-20) by Gino Wickman & Mark C. Winters (Visionary + Integrator relationship)\n\n## About the Author\n\n**Gino Wickman** is the creator of EOS (Entrepreneurial Operating System) and founder of EOS Worldwide, a community of certified EOS Implementers who help companies implement the system. Wickman has worked with thousands of entrepreneurial leadership teams and has helped them get real traction. *Traction* has sold over 2 million copies and EOS is used by over 250,000 companies worldwide. His work focuses on the practical tools needed to run an entrepreneurial company.\n",{"name":5,"license":14,"metadata":23,"description":7},{"author":24,"version":25},"wondelai","1.1.0","master","f483e54f3ad5f202a77d45f2e57f8d970b71195f","skills_library\u002Ftraction-eos",2,"https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills","https:\u002F\u002Fgithub.com\u002Froohe","yoou.link","2026-05-19 15:56:07",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add roohe\u002Fagentic-super-skills --skill traction-eos",{"tool":40,"command":41},"bunx","bunx skills add roohe\u002Fagentic-super-skills --skill traction-eos",{"tool":43,"command":44},"pnpm","pnpm dlx skills add roohe\u002Fagentic-super-skills --skill traction-eos","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Ftraction-eos\u002FSKILL.md",true,[48,54,58,62,66,70,74,78,82],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"references\u002Fcase-studies.md","REFERENCE","参考文档",18493,"https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Ftraction-eos\u002Freferences\u002Fcase-studies.md",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Fdata.md",12783,"https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Ftraction-eos\u002Freferences\u002Fdata.md",{"path":59,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Fimplementation.md",15501,"https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Ftraction-eos\u002Freferences\u002Fimplementation.md",{"path":63,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":64,"sourceHtmlUrl":65},"references\u002Fissues.md",14137,"https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Ftraction-eos\u002Freferences\u002Fissues.md",{"path":67,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Flevel-10.md",13552,"https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Ftraction-eos\u002Freferences\u002Flevel-10.md",{"path":71,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Fpeople.md",13330,"https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Ftraction-eos\u002Freferences\u002Fpeople.md",{"path":75,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Fprocess.md",13666,"https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Ftraction-eos\u002Freferences\u002Fprocess.md",{"path":79,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Frocks.md",12971,"https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Ftraction-eos\u002Freferences\u002Frocks.md",{"path":83,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Fvto.md",14569,"https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Ftraction-eos\u002Freferences\u002Fvto.md",[87,94,101,108,115,122],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":18},"01M73D865CZME2FCMKA4PQM348","zarr-python","Chunked N-D arrays for cloud storage. Compressed arrays, parallel I\u002FO, S3\u002FGCS integration, NumPy\u002FDask\u002FXarray compatible, for large-scale scientific computing pipelines.","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fzarr-python\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":18},"01M73D7Z64J4ABWZJD7P44XBBF","youtube-downloader","Download and process YouTube content for research. Use when: downloading competitor videos for analysis; extracting audio for podcasts; getting transcripts for content repurposing; archiving webinars; research content curation","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fyoutube-downloader\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":18},"01M73D7K8778TGZV3GJFR3703D","yc-pitch-deck","Create a compelling startup pitch deck that follows the structure proven to raise billions from top investors. Master the YC and Sequoia formats that get founders funded. Use when: **Fundraising** to create investor pitch decks; **YC application** to structure your narrative; **Demo Day prep** to craft your 2-minute pitch; **Angel investors** to communicate your opportunity; **Partnership pitches** to structure compelling asks","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fyc-pitch-deck\u002FSKILL.md",[],[],{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":18},"01M73D70KJSE0E8Z28YMNNRT04","x-twitter-scraper","Use when the user needs X (Twitter) data or confirmation-gated X actions through Xquik: tweet search, user lookup, follower extraction, media download, monitoring, webhooks, MCP, SDKs, posting, likes, DMs, and profile updates. Requires a Xquik API key. Never ask for X login material.","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fx-twitter-scraper\u002FSKILL.md",[],[],{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":18},"01M73D6ED01GV077R7K4NZNFZJ","write-vignette","Create R package vignettes using R Markdown or Quarto. Covers vignette setup, YAML configuration, code chunk options, building and testing, and CRAN requirements for vignettes. Use when adding a Getting Started tutorial, documenting complex workflows spanning multiple functions, creating domain-specific guides, or when CRAN submission requires user-facing documentation beyond function help pages.","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fwrite-vignette\u002FSKILL.md",[],[],{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":18},"01M73D69YJR0BK3NFHE0CYG3EF","write-validation-documentation","Write IQ\u002FOQ\u002FPQ validation documentation for computerized systems in regulated environments. Covers protocols, reports, test scripts, deviation handling, and approval workflows. Use when validating R or other software for regulated use, preparing for a regulatory audit, documenting qualification of computing environments, or creating and updating validation protocols and reports for new or re-qualified systems.","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fwrite-validation-documentation\u002FSKILL.md",[],[]]