[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7C27S47RT29W1MB55TCC9X0":3,"skill-same:01M7C27S47RT29W1MB55TCC9X0":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},"01M7C27S47RT29W1MB55TCC9X0","odoo-backup-strategy",null,"Complete Odoo backup and restore strategy: database dumps, filestore backup, automated scheduling, cloud storage upload, and tested restore procedures.","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-backup-strategy\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: odoo-backup-strategy\ndescription: \"Complete Odoo backup and restore strategy: database dumps, filestore backup, automated scheduling, cloud storage upload, and tested restore procedures.\"\nrisk: safe\nsource: \"self\"\n---\n\n# Odoo Backup Strategy\n\n## Overview\n\nA complete Odoo backup must include both the **PostgreSQL database** and the **filestore** (attachments, images). This skill covers manual and automated backup procedures, offsite storage, and the correct restore sequence to bring a down Odoo instance back online.\n\n## When to Use This Skill\n\n- Setting up a backup strategy for a production Odoo instance.\n- Automating daily backups with shell scripts and cron.\n- Restoring Odoo after a server failure or data corruption event.\n- Diagnosing a failed backup or corrupt restore.\n\n## How It Works\n\n1. **Activate**: Mention `@odoo-backup-strategy` and describe your server environment.\n2. **Generate**: Receive a complete backup script tailored to your setup.\n3. **Restore**: Get step-by-step restore instructions for any failure scenario.\n\n## Examples\n\n### Example 1: Manual Database + Filestore Backup\n\n```bash\n#!\u002Fbin\u002Fbash\n# backup_odoo.sh\n\nDATE=$(date +%Y%m%d_%H%M%S)\nDB_NAME=\"odoo\"\nDB_USER=\"odoo\"\nFILESTORE_PATH=\"\u002Fvar\u002Flib\u002Fodoo\u002F.local\u002Fshare\u002FOdoo\u002Ffilestore\u002F$DB_NAME\"\nBACKUP_DIR=\"\u002Fbackups\u002Fodoo\"\n\nmkdir -p \"$BACKUP_DIR\"\n\n# Step 1: Dump the database\npg_dump -U $DB_USER -Fc $DB_NAME > \"$BACKUP_DIR\u002Fdb_$DATE.dump\"\n\n# Step 2: Archive the filestore\ntar -czf \"$BACKUP_DIR\u002Ffilestore_$DATE.tar.gz\" -C \"$FILESTORE_PATH\" .\n\necho \"✅ Backup complete: db_$DATE.dump + filestore_$DATE.tar.gz\"\n```\n\n### Example 2: Automate with Cron (daily at 2 AM)\n\n```bash\n# Run: crontab -e\n# Add this line:\n0 2 * * * \u002Fopt\u002Fscripts\u002Fbackup_odoo.sh >> \u002Fvar\u002Flog\u002Fodoo_backup.log 2>&1\n```\n\n### Example 3: Upload to S3 (after backup)\n\n```bash\n# Add to backup script after tar command:\naws s3 cp \"$BACKUP_DIR\u002Fdb_$DATE.dump\"        s3:\u002F\u002Fmy-odoo-backups\u002Fdb\u002F\naws s3 cp \"$BACKUP_DIR\u002Ffilestore_$DATE.tar.gz\" s3:\u002F\u002Fmy-odoo-backups\u002Ffilestore\u002F\n\n# Optional: Delete local backups older than 7 days\nfind \"$BACKUP_DIR\" -type f -mtime +7 -delete\n```\n\n### Example 4: Full Restore Procedure\n\n```bash\n# Step 1: Stop Odoo\ndocker compose stop odoo  # or: systemctl stop odoo\n\n# Step 2: Recreate and restore the database\n# (--clean alone fails if the DB doesn't exist; drop and recreate first)\ndropdb -U odoo odoo 2>\u002Fdev\u002Fnull || true\ncreatedb -U odoo odoo\npg_restore -U odoo -d odoo db_YYYYMMDD_HHMMSS.dump\n\n# Step 3: Restore the filestore\nFILESTORE=\u002Fvar\u002Flib\u002Fodoo\u002F.local\u002Fshare\u002FOdoo\u002Ffilestore\u002Fodoo\nrm -rf \"$FILESTORE\"\u002F*\ntar -xzf filestore_YYYYMMDD_HHMMSS.tar.gz -C \"$FILESTORE\"\u002F\n\n# Step 4: Restart Odoo\ndocker compose start odoo\n\n# Step 5: Verify — open Odoo in the browser and check:\n#   - Can you log in?\n#   - Are recent records visible?\n#   - Are file attachments loading?\n```\n\n## Best Practices\n\n- ✅ **Do:** Test restores monthly in a staging environment — a backup you've never restored is not a backup.\n- ✅ **Do:** Follow the **3-2-1 rule**: 3 copies, 2 different media types, 1 offsite copy (e.g., S3 or a remote server).\n- ✅ **Do:** Back up **immediately before every Odoo upgrade** — this is your rollback point.\n- ✅ **Do:** Verify backup integrity: `pg_restore --list backup.dump` should complete without errors.\n- ❌ **Don't:** Back up only the database without the filestore — all attachments and images will be missing after a restore.\n- ❌ **Don't:** Store backups on the same disk or same server as Odoo — a disk or server failure destroys both.\n- ❌ **Don't:** Run `pg_restore --clean` against a non-existent database — always create the database first.\n\n## Limitations\n\n- Does not cover **Odoo.sh built-in backups** — Odoo.sh has its own backup system accessible from the dashboard.\n- This script assumes a **single-database** Odoo setup. Multi-database instances require looping over all databases.\n- Filestore path may differ between installations (Docker volume vs. bare-metal). Always verify the path with `odoo-bin shell` before running a restore.\n- Large filestores (100GB+) may require incremental backup tools like `rsync` or `restic` rather than full `tar.gz` archives.\n","# Odoo Backup Strategy\n\n## Overview\n\nA complete Odoo backup must include both the **PostgreSQL database** and the **filestore** (attachments, images). This skill covers manual and automated backup procedures, offsite storage, and the correct restore sequence to bring a down Odoo instance back online.\n\n## When to Use This Skill\n\n- Setting up a backup strategy for a production Odoo instance.\n- Automating daily backups with shell scripts and cron.\n- Restoring Odoo after a server failure or data corruption event.\n- Diagnosing a failed backup or corrupt restore.\n\n## How It Works\n\n1. **Activate**: Mention `@odoo-backup-strategy` and describe your server environment.\n2. **Generate**: Receive a complete backup script tailored to your setup.\n3. **Restore**: Get step-by-step restore instructions for any failure scenario.\n\n## Examples\n\n### Example 1: Manual Database + Filestore Backup\n\n```bash\n#!\u002Fbin\u002Fbash\n# backup_odoo.sh\n\nDATE=$(date +%Y%m%d_%H%M%S)\nDB_NAME=\"odoo\"\nDB_USER=\"odoo\"\nFILESTORE_PATH=\"\u002Fvar\u002Flib\u002Fodoo\u002F.local\u002Fshare\u002FOdoo\u002Ffilestore\u002F$DB_NAME\"\nBACKUP_DIR=\"\u002Fbackups\u002Fodoo\"\n\nmkdir -p \"$BACKUP_DIR\"\n\n# Step 1: Dump the database\npg_dump -U $DB_USER -Fc $DB_NAME > \"$BACKUP_DIR\u002Fdb_$DATE.dump\"\n\n# Step 2: Archive the filestore\ntar -czf \"$BACKUP_DIR\u002Ffilestore_$DATE.tar.gz\" -C \"$FILESTORE_PATH\" .\n\necho \"✅ Backup complete: db_$DATE.dump + filestore_$DATE.tar.gz\"\n```\n\n### Example 2: Automate with Cron (daily at 2 AM)\n\n```bash\n# Run: crontab -e\n# Add this line:\n0 2 * * * \u002Fopt\u002Fscripts\u002Fbackup_odoo.sh >> \u002Fvar\u002Flog\u002Fodoo_backup.log 2>&1\n```\n\n### Example 3: Upload to S3 (after backup)\n\n```bash\n# Add to backup script after tar command:\naws s3 cp \"$BACKUP_DIR\u002Fdb_$DATE.dump\"        s3:\u002F\u002Fmy-odoo-backups\u002Fdb\u002F\naws s3 cp \"$BACKUP_DIR\u002Ffilestore_$DATE.tar.gz\" s3:\u002F\u002Fmy-odoo-backups\u002Ffilestore\u002F\n\n# Optional: Delete local backups older than 7 days\nfind \"$BACKUP_DIR\" -type f -mtime +7 -delete\n```\n\n### Example 4: Full Restore Procedure\n\n```bash\n# Step 1: Stop Odoo\ndocker compose stop odoo  # or: systemctl stop odoo\n\n# Step 2: Recreate and restore the database\n# (--clean alone fails if the DB doesn't exist; drop and recreate first)\ndropdb -U odoo odoo 2>\u002Fdev\u002Fnull || true\ncreatedb -U odoo odoo\npg_restore -U odoo -d odoo db_YYYYMMDD_HHMMSS.dump\n\n# Step 3: Restore the filestore\nFILESTORE=\u002Fvar\u002Flib\u002Fodoo\u002F.local\u002Fshare\u002FOdoo\u002Ffilestore\u002Fodoo\nrm -rf \"$FILESTORE\"\u002F*\ntar -xzf filestore_YYYYMMDD_HHMMSS.tar.gz -C \"$FILESTORE\"\u002F\n\n# Step 4: Restart Odoo\ndocker compose start odoo\n\n# Step 5: Verify — open Odoo in the browser and check:\n#   - Can you log in?\n#   - Are recent records visible?\n#   - Are file attachments loading?\n```\n\n## Best Practices\n\n- ✅ **Do:** Test restores monthly in a staging environment — a backup you've never restored is not a backup.\n- ✅ **Do:** Follow the **3-2-1 rule**: 3 copies, 2 different media types, 1 offsite copy (e.g., S3 or a remote server).\n- ✅ **Do:** Back up **immediately before every Odoo upgrade** — this is your rollback point.\n- ✅ **Do:** Verify backup integrity: `pg_restore --list backup.dump` should complete without errors.\n- ❌ **Don't:** Back up only the database without the filestore — all attachments and images will be missing after a restore.\n- ❌ **Don't:** Store backups on the same disk or same server as Odoo — a disk or server failure destroys both.\n- ❌ **Don't:** Run `pg_restore --clean` against a non-existent database — always create the database first.\n\n## Limitations\n\n- Does not cover **Odoo.sh built-in backups** — Odoo.sh has its own backup system accessible from the dashboard.\n- This script assumes a **single-database** Odoo setup. Multi-database instances require looping over all databases.\n- Filestore path may differ between installations (Docker volume vs. bare-metal). Always verify the path with `odoo-bin shell` before running a restore.\n- Large filestores (100GB+) may require incremental backup tools like `rsync` or `restic` rather than full `tar.gz` archives.\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-backup-strategy",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-backup-strategy",{"tool":41,"command":42},"bunx","bunx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill odoo-backup-strategy",{"tool":44,"command":45},"pnpm","pnpm dlx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill odoo-backup-strategy","安装技能，技能地址：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-backup-strategy\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",[],[]]