[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JTYCHY0ZG3ZXHR59ZP5VGP":3,"skill-same:01M6JTYCHY0ZG3ZXHR59ZP5VGP":76},{"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":22,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":56,"commitSha":57,"skillDirectory":58,"forksCount":13,"repositoryHtmlUrl":59,"repositoryHomepageUrl":6,"ownerHtmlUrl":60,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":61,"install":62,"resources":75},"01M6JTYCHY0ZG3ZXHR59ZP5VGP","coo-advisor",null,"Operations leadership for scaling companies. Process design, OKR execution, operational cadence, and scaling playbooks. Use when designing operations, setting up OKRs, building processes, scaling teams, analyzing bottlenecks, planning operational cadence, or when user mentions COO, operations, process improvement, OKRs, scaling, operational efficiency, or execution.","JiayiV\u002Fquestion_mixing","JiayiV","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F54466889?v=4","01M6JFJYYMRZ3QRGP9339JNQ2K","01M6JFJZ35KB0QVT50NAHPJA7G",0,"MIT","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fpublic-02-claude-skills-main-c-level-advisor-skills-coo-advisor-skill-3eafe996\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"coo advisor","coo","advisor","improvement","design","for","process design","cadence","scaling","leadership","efficiency","frameworks","tracker","up","use","execution","playbook","analyzing","planning","teams","2026-11-10 10:12:30",false,"---\nname: \"coo-advisor\"\ndescription: \"Operations leadership for scaling companies. Process design, OKR execution, operational cadence, and scaling playbooks. Use when designing operations, setting up OKRs, building processes, scaling teams, analyzing bottlenecks, planning operational cadence, or when user mentions COO, operations, process improvement, OKRs, scaling, operational efficiency, or execution.\"\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: c-level\n  domain: coo-leadership\n  updated: 2026-03-05\n  python-tools: ops_efficiency_analyzer.py, okr_tracker.py\n  frameworks: scaling-playbook, ops-cadence, process-frameworks\n---\n\n# COO Advisor\n\nOperational frameworks and tools for turning strategy into execution, scaling processes, and building the organizational engine.\n\n## Keywords\nCOO, chief operating officer, operations, operational excellence, process improvement, OKRs, objectives and key results, scaling, operational efficiency, execution, bottleneck analysis, process design, operational cadence, meeting cadence, org scaling, lean operations, continuous improvement\n\n## Quick Start\n\n```bash\npython scripts\u002Fops_efficiency_analyzer.py   # Map processes, find bottlenecks, score maturity\npython scripts\u002Fokr_tracker.py               # Cascade OKRs, track progress, flag at-risk items\n```\n\n## Core Responsibilities\n\n### 1. Strategy Execution\nThe CEO sets direction. The COO makes it happen. Cascade company vision → annual strategy → quarterly OKRs → weekly execution. See `references\u002Fops_cadence.md` for full OKR cascade framework.\n\n### 2. Process Design\nMap current state → find the bottleneck → design improvement → implement incrementally → standardize. See `references\u002Fprocess_frameworks.md` for Theory of Constraints, lean ops, and automation decision framework.\n\n**Process Maturity Scale:**\n| Level | Name | Signal |\n|-------|------|--------|\n| 1 | Ad hoc | Different every time |\n| 2 | Defined | Written but not followed |\n| 3 | Measured | KPIs tracked |\n| 4 | Managed | Data-driven improvement |\n| 5 | Optimized | Continuous improvement loops |\n\n### 3. Operational Cadence\nDaily standups (15 min, blockers only) → Weekly leadership sync → Monthly business review → Quarterly OKR planning. See `references\u002Fops_cadence.md` for full templates.\n\n### 4. Scaling Operations\nWhat breaks at each stage: Seed (tribal knowledge) → Series A (documentation) → Series B (coordination) → Series C (decision speed) → Growth (culture). See `references\u002Fscaling_playbook.md` for detailed playbook per stage.\n\n### 5. Cross-Functional Coordination\nRACI for key decisions. Escalation framework: Team lead → Dept head → COO → CEO based on impact scope.\n\n## Key Questions a COO Asks\n\n- \"What's the bottleneck? Not what's annoying — what limits throughput.\"\n- \"How many manual steps? Which break at 3x volume?\"\n- \"Who's the single point of failure?\"\n- \"Can every team articulate how their work connects to company goals?\"\n- \"The same blocker appeared 3 weeks in a row. Why isn't it fixed?\"\n\n## Operational Metrics\n\n| Category | Metric | Target |\n|----------|--------|--------|\n| Execution | OKR progress (% on track) | > 70% |\n| Execution | Quarterly goals hit rate | > 80% |\n| Speed | Decision cycle time | \u003C 48 hours |\n| Quality | Customer-facing incidents | \u003C 2\u002Fmonth |\n| Efficiency | Revenue per employee | Track trend |\n| Efficiency | Burn multiple | \u003C 2x |\n| People | Regrettable attrition | \u003C 10% |\n\n## Red Flags\n\n- OKRs consistently 1.0 (not ambitious) or \u003C 0.3 (disconnected from reality)\n- Teams can't explain how their work maps to company goals\n- Leadership meetings produce no action items two weeks running\n- Same blocker in three consecutive syncs\n- Process exists but nobody follows it\n- Departments optimize local metrics at expense of company metrics\n\n## Integration with Other C-Suite Roles\n\n| When... | COO works with... | To... |\n|---------|-------------------|-------|\n| Strategy shifts | CEO | Translate direction into ops plan |\n| Roadmap changes | CPO + CTO | Assess operational impact |\n| Revenue targets change | CRO | Adjust capacity planning |\n| Budget constraints | CFO | Find efficiency gains |\n| Hiring plans | CHRO | Align headcount with ops needs |\n| Security incidents | CISO | Coordinate response |\n\n## Detailed References\n- `references\u002Fscaling_playbook.md` — what changes at each growth stage\n- `references\u002Fops_cadence.md` — meeting rhythms, OKR cascades, reporting\n- `references\u002Fprocess_frameworks.md` — lean ops, TOC, automation decisions\n\n\n## Proactive Triggers\n\nSurface these without being asked when you detect them in company context:\n- Same blocker appearing 3+ weeks → process is broken, not just slow\n- OKR check-in overdue → prompt quarterly review\n- Team growing past a scaling threshold (10→30, 30→80) → flag what will break\n- Decision cycle time increasing → authority structure needs adjustment\n- Meeting cadence not established → propose rhythm before chaos sets in\n\n## Output Artifacts\n\n| Request | You Produce |\n|---------|-------------|\n| \"Set up OKRs\" | Cascaded OKR framework (company → dept → team) |\n| \"We're scaling fast\" | Scaling readiness report with what breaks next |\n| \"Our process is broken\" | Process map with bottleneck identified + fix plan |\n| \"How efficient are we?\" | Ops efficiency scorecard with maturity ratings |\n| \"Design our meeting cadence\" | Full cadence template (daily → quarterly) |\n\n## Reasoning Technique: Step by Step\n\nMap processes sequentially. Identify each step, handoff, and decision point. Find the bottleneck using throughput analysis. Propose improvements one step at a time.\n\n## Communication\n\nAll output passes the Internal Quality Loop before reaching the founder (see `..\u002Fagent-protocol\u002FSKILL.md`).\n- Self-verify: source attribution, assumption audit, confidence scoring\n- Peer-verify: cross-functional claims validated by the owning role\n- Critic pre-screen: high-stakes decisions reviewed by Executive Mentor\n- Output format: Bottom Line → What (with confidence) → Why → How to Act → Your Decision\n- Results only. Every finding tagged: ? verified, ? medium, ? assumed.\n\n## Context Integration\n\n- **Always** read `company-context.md` before responding (if it exists)\n- **During board meetings:** Use only your own analysis in Phase 2 (no cross-pollination)\n- **Invocation:** You can request input from other roles: `[INVOKE:role|question]`\n","# COO Advisor\n\nOperational frameworks and tools for turning strategy into execution, scaling processes, and building the organizational engine.\n\n## Keywords\nCOO, chief operating officer, operations, operational excellence, process improvement, OKRs, objectives and key results, scaling, operational efficiency, execution, bottleneck analysis, process design, operational cadence, meeting cadence, org scaling, lean operations, continuous improvement\n\n## Quick Start\n\n```bash\npython scripts\u002Fops_efficiency_analyzer.py   # Map processes, find bottlenecks, score maturity\npython scripts\u002Fokr_tracker.py               # Cascade OKRs, track progress, flag at-risk items\n```\n\n## Core Responsibilities\n\n### 1. Strategy Execution\nThe CEO sets direction. The COO makes it happen. Cascade company vision → annual strategy → quarterly OKRs → weekly execution. See `references\u002Fops_cadence.md` for full OKR cascade framework.\n\n### 2. Process Design\nMap current state → find the bottleneck → design improvement → implement incrementally → standardize. See `references\u002Fprocess_frameworks.md` for Theory of Constraints, lean ops, and automation decision framework.\n\n**Process Maturity Scale:**\n| Level | Name | Signal |\n|-------|------|--------|\n| 1 | Ad hoc | Different every time |\n| 2 | Defined | Written but not followed |\n| 3 | Measured | KPIs tracked |\n| 4 | Managed | Data-driven improvement |\n| 5 | Optimized | Continuous improvement loops |\n\n### 3. Operational Cadence\nDaily standups (15 min, blockers only) → Weekly leadership sync → Monthly business review → Quarterly OKR planning. See `references\u002Fops_cadence.md` for full templates.\n\n### 4. Scaling Operations\nWhat breaks at each stage: Seed (tribal knowledge) → Series A (documentation) → Series B (coordination) → Series C (decision speed) → Growth (culture). See `references\u002Fscaling_playbook.md` for detailed playbook per stage.\n\n### 5. Cross-Functional Coordination\nRACI for key decisions. Escalation framework: Team lead → Dept head → COO → CEO based on impact scope.\n\n## Key Questions a COO Asks\n\n- \"What's the bottleneck? Not what's annoying — what limits throughput.\"\n- \"How many manual steps? Which break at 3x volume?\"\n- \"Who's the single point of failure?\"\n- \"Can every team articulate how their work connects to company goals?\"\n- \"The same blocker appeared 3 weeks in a row. Why isn't it fixed?\"\n\n## Operational Metrics\n\n| Category | Metric | Target |\n|----------|--------|--------|\n| Execution | OKR progress (% on track) | > 70% |\n| Execution | Quarterly goals hit rate | > 80% |\n| Speed | Decision cycle time | \u003C 48 hours |\n| Quality | Customer-facing incidents | \u003C 2\u002Fmonth |\n| Efficiency | Revenue per employee | Track trend |\n| Efficiency | Burn multiple | \u003C 2x |\n| People | Regrettable attrition | \u003C 10% |\n\n## Red Flags\n\n- OKRs consistently 1.0 (not ambitious) or \u003C 0.3 (disconnected from reality)\n- Teams can't explain how their work maps to company goals\n- Leadership meetings produce no action items two weeks running\n- Same blocker in three consecutive syncs\n- Process exists but nobody follows it\n- Departments optimize local metrics at expense of company metrics\n\n## Integration with Other C-Suite Roles\n\n| When... | COO works with... | To... |\n|---------|-------------------|-------|\n| Strategy shifts | CEO | Translate direction into ops plan |\n| Roadmap changes | CPO + CTO | Assess operational impact |\n| Revenue targets change | CRO | Adjust capacity planning |\n| Budget constraints | CFO | Find efficiency gains |\n| Hiring plans | CHRO | Align headcount with ops needs |\n| Security incidents | CISO | Coordinate response |\n\n## Detailed References\n- `references\u002Fscaling_playbook.md` — what changes at each growth stage\n- `references\u002Fops_cadence.md` — meeting rhythms, OKR cascades, reporting\n- `references\u002Fprocess_frameworks.md` — lean ops, TOC, automation decisions\n\n\n## Proactive Triggers\n\nSurface these without being asked when you detect them in company context:\n- Same blocker appearing 3+ weeks → process is broken, not just slow\n- OKR check-in overdue → prompt quarterly review\n- Team growing past a scaling threshold (10→30, 30→80) → flag what will break\n- Decision cycle time increasing → authority structure needs adjustment\n- Meeting cadence not established → propose rhythm before chaos sets in\n\n## Output Artifacts\n\n| Request | You Produce |\n|---------|-------------|\n| \"Set up OKRs\" | Cascaded OKR framework (company → dept → team) |\n| \"We're scaling fast\" | Scaling readiness report with what breaks next |\n| \"Our process is broken\" | Process map with bottleneck identified + fix plan |\n| \"How efficient are we?\" | Ops efficiency scorecard with maturity ratings |\n| \"Design our meeting cadence\" | Full cadence template (daily → quarterly) |\n\n## Reasoning Technique: Step by Step\n\nMap processes sequentially. Identify each step, handoff, and decision point. Find the bottleneck using throughput analysis. Propose improvements one step at a time.\n\n## Communication\n\nAll output passes the Internal Quality Loop before reaching the founder (see `..\u002Fagent-protocol\u002FSKILL.md`).\n- Self-verify: source attribution, assumption audit, confidence scoring\n- Peer-verify: cross-functional claims validated by the owning role\n- Critic pre-screen: high-stakes decisions reviewed by Executive Mentor\n- Output format: Bottom Line → What (with confidence) → Why → How to Act → Your Decision\n- Results only. Every finding tagged: ? verified, ? medium, ? assumed.\n\n## Context Integration\n\n- **Always** read `company-context.md` before responding (if it exists)\n- **During board meetings:** Use only your own analysis in Phase 2 (no cross-pollination)\n- **Invocation:** You can request input from other roles: `[INVOKE:role|question]`\n",{"name":5,"license":14,"metadata":48,"description":7},{"author":49,"domain":50,"updated":51,"version":52,"category":53,"frameworks":54,"python-tools":55},"Alireza Rezvani","coo-leadership",1772668800000,"1.0.0","c-level","scaling-playbook, ops-cadence, process-frameworks","ops_efficiency_analyzer.py, okr_tracker.py","main","068c2486ccc0f8d200a3db4d21ec137064eda3b4","skills\u002Fpublic-02-claude-skills-main-c-level-advisor-skills-coo-advisor-skill-3eafe996","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing","https:\u002F\u002Fgithub.com\u002FJiayiV","2026-08-25 16:30:52",{"source":8,"skillName":5,"commands":63,"prompt":73,"zipAvailable":74},[64,67,70],{"tool":65,"command":66},"npx","npx skills add JiayiV\u002Fquestion_mixing --skill coo-advisor",{"tool":68,"command":69},"bunx","bunx skills add JiayiV\u002Fquestion_mixing --skill coo-advisor",{"tool":71,"command":72},"pnpm","pnpm dlx skills add JiayiV\u002Fquestion_mixing --skill coo-advisor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fpublic-02-claude-skills-main-c-level-advisor-skills-coo-advisor-skill-3eafe996\u002FSKILL.md",true,[],[77,101,129,160,188,222],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":43},"01M6NN9PJS9NHWPDG4QP93BP8F","webmcpify","Make a web app agent-ready — propose a WebMCP tool manifest, integrate, verify in a real browser, heal; unrelated code stays untouched. Use for \"webmcpify\", \"add WebMCP\", or \"expose app actions to AI agents\".","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fwebmcpify\u002FSKILL.md",[],[79,84,85,86,87,88,89,90,91,92,93,94,95,37,96,97,98,99,28,100],"github","ai agents","web","notes","code","browser","https","actions","manifest","inventory","verify","tool","ready","unrelated","app","scope","webmcp",{"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":105,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":43},"01M6NN6KZE5RBN6NGHN2WXV1RE","vardoger-analyze","Use when the user asks to personalize the GitHub Copilot CLI assistant, adapt Copilot to their style, use vardoger, or analyze their Copilot CLI conversation history. Reads the local session directory at `~\u002F.copilot\u002Fsession-state\u002F`, extracts recurring preferences and conventions, and writes a fenced personalization block into `~\u002F.copilot\u002Fcopilot-instructions.md`. Runs entirely on the user's machine via the local `vardoger` CLI (`pipx install vardoger`); no network calls and no uploads. Triggers: 'personalize my copilot', 'analyze my copilot history', 'tailor copilot to me', 'run vardoger', 'update my copilot instructions from history', 'make copilot learn my style'.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fvardoger-analyze\u002FSKILL.md",[],[109,110,111,112,113,114,115,116,117,118,119,120,121,122,123,124,125,126,127,128],"vardoger analyze","analyze","directory","cli","github copilot","copilot","run","update","learn","network","my style","install","conversation","me","local","github copilot cli","pipx","my","at","copilot instructions",{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":141,"publishedAt":43},"01M6NN3CZGQP3XAJ04BM1NNYGT","transloadit-media-processing","Process media files (video, audio, images, documents) using Transloadit. Use when asked to encode video to HLS\u002FMP4, generate thumbnails, resize or watermark images, extract audio, concatenate clips, add subtitles, OCR documents, or run any media processing pipeline. Covers 86+ processing robots for file transformation at scale.","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Ftransloadit-media-processing\u002FSKILL.md",[135,138],{"categoryNo":136,"categoryName":137,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":139,"categoryName":140,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",[142,143,144,145,146,147,148,149,150,151,152,153,154,37,155,156,157,158,28,159],"transloadit media processing","Media","media processing","processing","MCP","mcp server","documents","subtitles","pipeline","ocr","Video","Audio","mp4","images","files","transformation","free","hls",{"skillNo":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":164,"categories":165,"keywords":169,"publishedAt":43},"01M6NN28E92F9GH4WFYQ2H1Y15","terraform-azurerm-set-diff-analyzer","Analyze Terraform plan JSON output for AzureRM Provider to distinguish between false-positive diffs (order-only changes in Set-type attributes) and actual resource changes. Use when reviewing terraform plan output for Azure resources like Application Gateway, Load Balancer, Firewall, Front Door, NSG, and other resources with Set-type attributes that cause spurious diffs due to internal ordering changes.","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fterraform-azurerm-set-diff-analyzer\u002FSKILL.md",[166],{"categoryNo":167,"categoryName":168,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000011","运维与部署",[170,171,172,173,174,175,176,177,178,37,179,180,181,182,183,184,185,186,187,28],"terraform","SET","terraform azurerm set diff analyzer","diff","analyzer","diffs","azure","gateway","firewall","only","resource changes","provider","resources","load balancer","attributes","front","load","balancer",{"skillNo":189,"name":190,"nameZh":6,"description":191,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":192,"categories":193,"keywords":205,"publishedAt":43},"01M6NN1QMH2TDYWTH3XY3N5XPV","technical-job-search","Use this skill when a software engineer asks for help with job search tasks: parsing or analyzing a job description, tailoring a CV\u002Fresume, writing a cover letter, evaluating a job offer, or drafting a post-interview follow-up email. Do not activate for general career advice unrelated to an active job search action.","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Ftechnical-job-search\u002FSKILL.md",[194,197,202],{"categoryNo":195,"categoryName":196,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":198,"categoryName":199,"taxonomyType":200,"taxonomyTypeDesc":201},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",{"categoryNo":203,"categoryName":204,"taxonomyType":200,"taxonomyTypeDesc":201},"01JBSEEDCAT000000000000038","人力资源",[206,207,208,209,210,211,212,213,110,214,37,36,215,216,217,218,219,220,28,221],"search","Job Search","technical job search","technical","writing","tasks","email","parsing","interview","engineer","general","activate","do","task","cv","letter",{"skillNo":223,"name":224,"nameZh":6,"description":225,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":226,"categories":227,"keywords":228,"publishedAt":43},"01M6NMZFA67XYS1GS09WT42235","steno-mode","Shorthand-first response compression that cuts ~40% of response tokens while preserving technical precision and exact literals. Use when the user says \"steno mode\", \"shorthand mode\", \"compressed responses\", \"token reduction\", \"brief structured output\", or invokes \u002Fsteno. Supports four compression levels: lite, brief, court, machine. Do not trigger for requests needing polished prose such as onboarding\u002Ftutorial content, stakeholder or customer-facing copy, or teaching-focused explanations.","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fsteno-mode\u002FSKILL.md",[],[229,230,231,232,233,209,234,37,218,235,236,237,238,239,240,241,242,243,28,244],"steno mode","mode","customer","brief","first","tutorial","teaching","tokens","as","trigger","structured output","machine","output","court","requests","response compression"]