[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7C2EFT3ZPZSZMMZNEQ3PMVJ":3,"skill-same:01M7C2EFT3ZPZSZMMZNEQ3PMVJ":49},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7C2EFT3ZPZSZMMZNEQ3PMVJ","odoo-performance-tuner",null,"Expert guide for diagnosing and fixing Odoo performance issues: slow queries, worker configuration, memory limits, PostgreSQL tuning, and profiling tools.","YYC-Cube\u002FYYC3-Knowledge-Base","YYC-Cube","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F235006543?v=4","01M79J2PH4SWD2X0825X6PN748","yyc3","01M79J2PHVK3F6ZBYT8K2SCZCW",1,"MIT","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fplugins\u002Fantigravity-awesome-skills-claude\u002Fskills\u002Fodoo-performance-tuner\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: odoo-performance-tuner\ndescription: \"Expert guide for diagnosing and fixing Odoo performance issues: slow queries, worker configuration, memory limits, PostgreSQL tuning, and profiling tools.\"\nrisk: safe\nsource: \"self\"\n---\n\n# Odoo Performance Tuner\n\n## Overview\n\nThis skill helps diagnose and resolve Odoo performance problems — from slow page loads and database bottlenecks to worker misconfiguration and memory bloat. It covers PostgreSQL query tuning, Odoo worker settings, and built-in profiling tools.\n\n## When to Use This Skill\n\n- Odoo is slow in production (slow page loads, timeouts).\n- Getting `MemoryError` or `Worker timeout` errors in logs.\n- Diagnosing a slow database query using Odoo's profiler.\n- Tuning `odoo.conf` for a specific server spec.\n\n## How It Works\n\n1. **Activate**: Mention `@odoo-performance-tuner` and describe your performance issue.\n2. **Diagnose**: Share relevant log lines or config and receive a root cause analysis.\n3. **Fix**: Get exact configuration changes with explanations.\n\n## Examples\n\n### Example 1: Recommended Worker Configuration\n\n```ini\n# odoo.conf — tuned for a 4-core, 8GB RAM server\n\nworkers = 9                   # (CPU_cores × 2) + 1 — never set to 0 in production\nmax_cron_threads = 2          # background cron jobs; keep ≤ 2 to preserve user-facing capacity\nlimit_memory_soft = 1610612736  # 1.5 GB — worker is recycled gracefully after this\nlimit_memory_hard = 2147483648  # 2.0 GB — worker is killed immediately; prevents OOM crashes\nlimit_time_cpu = 600          # max CPU seconds per request\nlimit_time_real = 1200        # max wall-clock seconds per request\nlimit_request = 8192          # max requests before worker recycles (prevents memory leaks)\n```\n\n### Example 2: Find Slow Queries with PostgreSQL\n\n```sql\n-- Step 1: Enable pg_stat_statements extension (run once as postgres superuser)\nCREATE EXTENSION IF NOT EXISTS pg_stat_statements;\n\n-- Step 2: Also add to postgresql.conf and reload:\n-- shared_preload_libraries = 'pg_stat_statements'\n-- log_min_duration_statement = 1000   -- log queries taking > 1 second\n\n-- Step 3: Find the top 10 slowest average queries\nSELECT\n    LEFT(query, 100) AS query_snippet,\n    round(mean_exec_time::numeric, 2) AS avg_ms,\n    calls,\n    round(total_exec_time::numeric, 2) AS total_ms\nFROM pg_stat_statements\nORDER BY mean_exec_time DESC\nLIMIT 10;\n\n-- Step 4: Check for missing indexes causing full table scans\nSELECT schemaname, tablename, attname, n_distinct, correlation\nFROM pg_stats\nWHERE tablename = 'sale_order_line'\n  AND correlation \u003C 0.5   -- low correlation = poor index efficiency\nORDER BY n_distinct DESC;\n```\n\n### Example 3: Use Odoo's Built-In Profiler\n\n```text\nPrerequisites: Run Odoo with ?debug=1 in the URL to enable debug mode.\n\nMenu: Settings → Technical → Profiling\n\nSteps:\n  1. Click \"Enable Profiling\" — set a duration (e.g., 60 seconds)\n  2. Navigate to and reproduce the slow action\n  3. Return to Settings → Technical → Profiling → View Results\n\nWhat to look for:\n  - Total SQL queries > 100 on a single page  → N+1 query problem\n  - Single queries taking > 100ms             → missing DB index\n  - Same query repeated many times            → missing cache, use @ormcache\n  - Python time high but SQL low             → compute field inefficiency\n```\n\n## Best Practices\n\n- ✅ **Do:** Use `mapped()`, `filtered()`, and `sorted()` on in-memory recordsets — they don't trigger additional SQL.\n- ✅ **Do:** Add PostgreSQL B-tree indexes on columns frequently used in domain filters (`partner_id`, `state`, `date_order`).\n- ✅ **Do:** Enable Odoo's HTTP caching for static assets and put a CDN (Cloudflare, AWS CloudFront) in front of the website.\n- ✅ **Do:** Use `@tools.ormcache` decorator on methods pulled repeatedly with the same arguments.\n- ❌ **Don't:** Set `workers = 0` in production — single-threaded mode serializes all requests and blocks all users on any slow operation.\n- ❌ **Don't:** Ignore `limit_memory_soft` — workers exceeding it are recycled between requests; without the limit they grow unbounded and crash.\n- ❌ **Don't:** Directly manipulate `prefetch_ids` on recordsets — rely on Odoo's automatic batch prefetching, which activates by default.\n\n## Limitations\n\n- PostgreSQL tuning (`shared_buffers`, `work_mem`, `effective_cache_size`) is highly server-specific and not covered in depth here — use [PGTune](https:\u002F\u002Fpgtune.leopard.in.ua\u002F) as a starting baseline.\n- The built-in Odoo profiler only captures **Python + SQL** traces; JavaScript rendering performance requires browser DevTools.\n- **Odoo.sh** managed hosting restricts direct PostgreSQL and `odoo.conf` access — some tuning options are unavailable.\n- Does not cover **Redis-based session store** or **Celery task queue** optimizations, which are advanced patterns for very high-traffic instances.\n","# Odoo Performance Tuner\n\n## Overview\n\nThis skill helps diagnose and resolve Odoo performance problems — from slow page loads and database bottlenecks to worker misconfiguration and memory bloat. It covers PostgreSQL query tuning, Odoo worker settings, and built-in profiling tools.\n\n## When to Use This Skill\n\n- Odoo is slow in production (slow page loads, timeouts).\n- Getting `MemoryError` or `Worker timeout` errors in logs.\n- Diagnosing a slow database query using Odoo's profiler.\n- Tuning `odoo.conf` for a specific server spec.\n\n## How It Works\n\n1. **Activate**: Mention `@odoo-performance-tuner` and describe your performance issue.\n2. **Diagnose**: Share relevant log lines or config and receive a root cause analysis.\n3. **Fix**: Get exact configuration changes with explanations.\n\n## Examples\n\n### Example 1: Recommended Worker Configuration\n\n```ini\n# odoo.conf — tuned for a 4-core, 8GB RAM server\n\nworkers = 9                   # (CPU_cores × 2) + 1 — never set to 0 in production\nmax_cron_threads = 2          # background cron jobs; keep ≤ 2 to preserve user-facing capacity\nlimit_memory_soft = 1610612736  # 1.5 GB — worker is recycled gracefully after this\nlimit_memory_hard = 2147483648  # 2.0 GB — worker is killed immediately; prevents OOM crashes\nlimit_time_cpu = 600          # max CPU seconds per request\nlimit_time_real = 1200        # max wall-clock seconds per request\nlimit_request = 8192          # max requests before worker recycles (prevents memory leaks)\n```\n\n### Example 2: Find Slow Queries with PostgreSQL\n\n```sql\n-- Step 1: Enable pg_stat_statements extension (run once as postgres superuser)\nCREATE EXTENSION IF NOT EXISTS pg_stat_statements;\n\n-- Step 2: Also add to postgresql.conf and reload:\n-- shared_preload_libraries = 'pg_stat_statements'\n-- log_min_duration_statement = 1000   -- log queries taking > 1 second\n\n-- Step 3: Find the top 10 slowest average queries\nSELECT\n    LEFT(query, 100) AS query_snippet,\n    round(mean_exec_time::numeric, 2) AS avg_ms,\n    calls,\n    round(total_exec_time::numeric, 2) AS total_ms\nFROM pg_stat_statements\nORDER BY mean_exec_time DESC\nLIMIT 10;\n\n-- Step 4: Check for missing indexes causing full table scans\nSELECT schemaname, tablename, attname, n_distinct, correlation\nFROM pg_stats\nWHERE tablename = 'sale_order_line'\n  AND correlation \u003C 0.5   -- low correlation = poor index efficiency\nORDER BY n_distinct DESC;\n```\n\n### Example 3: Use Odoo's Built-In Profiler\n\n```text\nPrerequisites: Run Odoo with ?debug=1 in the URL to enable debug mode.\n\nMenu: Settings → Technical → Profiling\n\nSteps:\n  1. Click \"Enable Profiling\" — set a duration (e.g., 60 seconds)\n  2. Navigate to and reproduce the slow action\n  3. Return to Settings → Technical → Profiling → View Results\n\nWhat to look for:\n  - Total SQL queries > 100 on a single page  → N+1 query problem\n  - Single queries taking > 100ms             → missing DB index\n  - Same query repeated many times            → missing cache, use @ormcache\n  - Python time high but SQL low             → compute field inefficiency\n```\n\n## Best Practices\n\n- ✅ **Do:** Use `mapped()`, `filtered()`, and `sorted()` on in-memory recordsets — they don't trigger additional SQL.\n- ✅ **Do:** Add PostgreSQL B-tree indexes on columns frequently used in domain filters (`partner_id`, `state`, `date_order`).\n- ✅ **Do:** Enable Odoo's HTTP caching for static assets and put a CDN (Cloudflare, AWS CloudFront) in front of the website.\n- ✅ **Do:** Use `@tools.ormcache` decorator on methods pulled repeatedly with the same arguments.\n- ❌ **Don't:** Set `workers = 0` in production — single-threaded mode serializes all requests and blocks all users on any slow operation.\n- ❌ **Don't:** Ignore `limit_memory_soft` — workers exceeding it are recycled between requests; without the limit they grow unbounded and crash.\n- ❌ **Don't:** Directly manipulate `prefetch_ids` on recordsets — rely on Odoo's automatic batch prefetching, which activates by default.\n\n## Limitations\n\n- PostgreSQL tuning (`shared_buffers`, `work_mem`, `effective_cache_size`) is highly server-specific and not covered in depth here — use [PGTune](https:\u002F\u002Fpgtune.leopard.in.ua\u002F) as a starting baseline.\n- The built-in Odoo profiler only captures **Python + SQL** traces; JavaScript rendering performance requires browser DevTools.\n- **Odoo.sh** managed hosting restricts direct PostgreSQL and `odoo.conf` access — some tuning options are unavailable.\n- Does not cover **Redis-based session store** or **Celery task queue** optimizations, which are advanced patterns for very high-traffic instances.\n",{"name":5,"risk":24,"source":25,"description":7},"safe","self","main","87afe6ce96220accf50a345dea46784c8c9f210e","YYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fplugins\u002Fantigravity-awesome-skills-claude\u002Fskills\u002Fodoo-performance-tuner",0,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base","https:\u002F\u002Fkb.yyc3.top\u002F","https:\u002F\u002Fgithub.com\u002FYYC-Cube","万象归元于云枢 | 深栈智启新纪元","2026-11-10 10:37:32",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill odoo-performance-tuner",{"tool":41,"command":42},"bunx","bunx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill odoo-performance-tuner",{"tool":44,"command":45},"pnpm","pnpm dlx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill odoo-performance-tuner","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fplugins\u002Fantigravity-awesome-skills-claude\u002Fskills\u002Fodoo-performance-tuner\u002FSKILL.md",true,[],[50,57,64,71,78,85],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M7CTDWHERCXPQCP0K03A86AS","vercel-sandbox","Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include \"Vercel Sandbox browser\", \"microVM Chrome\", \"agent-browser in sandbox\", \"browser automation on Vercel\", or any task requiring Chrome in a Vercel Sandbox.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fvercel-sandbox\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M7CTD8D2BNJY54S65M47HEJA","slack","Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include \"check my Slack\", \"what channels have unreads\", \"send a message to\", \"search Slack for\", \"extract from Slack\", \"find who said\", or any task requiring programmatic Slack interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fslack\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7CTCSSB8ZP3Q58C3YZDZK1W","electron","Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include \"automate Slack app\", \"control VS Code\", \"interact with Discord app\", \"test this Electron app\", \"connect to desktop app\", or any task requiring automation of a native Electron application.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Felectron\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7CTCBJY76688V4DCZGWFHGQ","dogfood","Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to \"dogfood\", \"QA\", \"exploratory test\", \"find issues\", \"bug hunt\", \"test this app\u002Fsite\u002Fplatform\", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fdogfood\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7CTC4H0FFGVEAQR9PA4GA1A","agent-browser","Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to \"open a website\", \"fill out a form\", \"click a button\", \"take a screenshot\", \"scrape data from a page\", \"test this web app\", \"login to a site\", \"automate browser actions\", or any task requiring programmatic web interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fagent-browser\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7CTBKVFYBG78FDSABSDJTTQ","shadcn","Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn\u002Fui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for \"shadcn init\", \"create an app with --preset\", \"switch to --preset\", and for building a design system or applying a DESIGN.md or brand spec to shadcn\u002Fui.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-UI-界面组件\u002FYYC3-UI-界面组件-ui\u002Fskills\u002Fshadcn\u002FSKILL.md",[],[]]