[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75TQ56QVZX3Q680X89RT6FT":3,"skill-same:01M75TQ56QVZX3Q680X89RT6FT":45},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":44},"01M75TQ56QVZX3Q680X89RT6FT","report-incident",null,"Draft a terse GitHub issue for an incident in the Odoo dev suite (odoo-dev, odoo-orchestrator, dispatcher), with a current environment block and no private data. Files it only after you approve. Use when a tool or workflow failed.","Crpaxton4\u002Fdevcontainer-features","Crpaxton4","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F10190720?v=4","01M75TNGAF4N2K56AS0WDN38AM","Chris Paxton","01M75TNGB1E99BTJEGPXPQDRAB",0,"MIT","https:\u002F\u002Fgithub.com\u002FCrpaxton4\u002Fdevcontainer-features\u002Fblob\u002Fmain\u002Fplugins\u002Fodoo-orchestrator\u002Fskills\u002Freport-incident\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: report-incident\ndescription: \"Draft a terse GitHub issue for an incident in the Odoo dev suite (odoo-dev, odoo-orchestrator, dispatcher), with a current environment block and no private data. Files it only after you approve. Use when a tool or workflow failed.\"\nuser-invocable: true\n---\n\n# Report an incident\n\nTurn one incident into a GitHub issue in `Crpaxton4\u002Fdevcontainer-features`.\nThe argument is an optional description. When it is present, use it as the first draft of the Summary.\n\n## 1. Read the environment\n\nRun each command on its own. If a command fails, write `unknown` for that field.\n\n```\nodoo-dev --version\nclaude --version\nclaude plugin list\n```\n\n`claude plugin list` shows the installed plugin names and versions. Use only odoo-dev and odoo-orchestrator.\nThe version of this plugin is also in `${CLAUDE_PLUGIN_ROOT}\u002F.claude-plugin\u002Fplugin.json`.\n\nIf the incident is in the orchestrator or the dispatcher, also run these. `ODOO_ORCHESTRATOR_CHECKOUT` is the checkout that holds `stack\u002Fcompose.yaml`.\n\n```\ngit -C \"$ODOO_ORCHESTRATOR_CHECKOUT\" rev-parse --short HEAD\ngrep -m1 '^version' \"$ODOO_ORCHESTRATOR_CHECKOUT\u002Flibraries\u002Fdispatcher\u002Fpyproject.toml\"\n```\n\nBuild this block. Use `n\u002Fa` for `transport` when no Odoo call was involved.\n\n```\n\u003Cenvironment>\n\u003Csuite_version>odoo-dev \u003Cversion> (host), main at \u003Ccheckout commit or n\u002Fa>\u003C\u002Fsuite_version>\n\u003Cpython_version>\u003Cversion> (host)\u003C\u002Fpython_version>\n\u003Cclaude_code_version>\u003Cversion>\u003C\u002Fclaude_code_version>\n\u003Cplugins>odoo-dev \u003Cversion>, odoo-orchestrator \u003Cversion>\u003C\u002Fplugins>\n\u003Ctransport>\u003Cxmlrpc, jsonrpc or n\u002Fa>\u003C\u002Ftransport>\n\u003C\u002Fenvironment>\n```\n\nFor an orchestrator incident, add the dispatcher version to `suite_version`.\nGet the Python version from `python3 --version`.\n\n## 2. Draft the issue\n\nWrite the body with these sections, in this order. Keep it terse, for a reader who is an AI.\n\n1. **Summary**: 1-2 sentences.\n2. **Symptoms**: bullets of the errors or behavior you saw.\n3. **Environment**: the block from step 1, verbatim.\n4. **Steps to reproduce**: if they are known.\n5. **Context**: the relevant tool calls, responses or state from this session.\n\nWrite the title as `\u003Ccomponent>: \u003Cproblem stated as a fact>`.\n\n## 3. CRITICAL: privacy rules\n\nNEVER put any of these in the title or the body:\n\n- The Odoo server URL.\n- The database name.\n- A username, password or API key.\n- A customer name.\n- Any other identifying detail.\n\nBefore you show the draft, read it again and remove or generalize each match.\n\n## 4. Approve, then file\n\n1. Show the full draft (title and body) to the user.\n2. Wait. Do not file until the user approves. Apply the edits the user asks for and show it again.\n3. Write the body to a file with the Write tool, for example `\u002Ftmp\u002Freport-incident-body.md`.\n4. File the issue with the body file. Never pass the body inline: the shell truncates it at the first special character.\n\n```\ngh issue create -R Crpaxton4\u002Fdevcontainer-features --title \"\u003Ccomponent>: \u003Cproblem stated as a fact>\" --body-file \u003Cpath>\n```\n\n5. Give the user the issue URL that `gh` prints.\n","# Report an incident\n\nTurn one incident into a GitHub issue in `Crpaxton4\u002Fdevcontainer-features`.\nThe argument is an optional description. When it is present, use it as the first draft of the Summary.\n\n## 1. Read the environment\n\nRun each command on its own. If a command fails, write `unknown` for that field.\n\n```\nodoo-dev --version\nclaude --version\nclaude plugin list\n```\n\n`claude plugin list` shows the installed plugin names and versions. Use only odoo-dev and odoo-orchestrator.\nThe version of this plugin is also in `${CLAUDE_PLUGIN_ROOT}\u002F.claude-plugin\u002Fplugin.json`.\n\nIf the incident is in the orchestrator or the dispatcher, also run these. `ODOO_ORCHESTRATOR_CHECKOUT` is the checkout that holds `stack\u002Fcompose.yaml`.\n\n```\ngit -C \"$ODOO_ORCHESTRATOR_CHECKOUT\" rev-parse --short HEAD\ngrep -m1 '^version' \"$ODOO_ORCHESTRATOR_CHECKOUT\u002Flibraries\u002Fdispatcher\u002Fpyproject.toml\"\n```\n\nBuild this block. Use `n\u002Fa` for `transport` when no Odoo call was involved.\n\n```\n\u003Cenvironment>\n\u003Csuite_version>odoo-dev \u003Cversion> (host), main at \u003Ccheckout commit or n\u002Fa>\u003C\u002Fsuite_version>\n\u003Cpython_version>\u003Cversion> (host)\u003C\u002Fpython_version>\n\u003Cclaude_code_version>\u003Cversion>\u003C\u002Fclaude_code_version>\n\u003Cplugins>odoo-dev \u003Cversion>, odoo-orchestrator \u003Cversion>\u003C\u002Fplugins>\n\u003Ctransport>\u003Cxmlrpc, jsonrpc or n\u002Fa>\u003C\u002Ftransport>\n\u003C\u002Fenvironment>\n```\n\nFor an orchestrator incident, add the dispatcher version to `suite_version`.\nGet the Python version from `python3 --version`.\n\n## 2. Draft the issue\n\nWrite the body with these sections, in this order. Keep it terse, for a reader who is an AI.\n\n1. **Summary**: 1-2 sentences.\n2. **Symptoms**: bullets of the errors or behavior you saw.\n3. **Environment**: the block from step 1, verbatim.\n4. **Steps to reproduce**: if they are known.\n5. **Context**: the relevant tool calls, responses or state from this session.\n\nWrite the title as `\u003Ccomponent>: \u003Cproblem stated as a fact>`.\n\n## 3. CRITICAL: privacy rules\n\nNEVER put any of these in the title or the body:\n\n- The Odoo server URL.\n- The database name.\n- A username, password or API key.\n- A customer name.\n- Any other identifying detail.\n\nBefore you show the draft, read it again and remove or generalize each match.\n\n## 4. Approve, then file\n\n1. Show the full draft (title and body) to the user.\n2. Wait. Do not file until the user approves. Apply the edits the user asks for and show it again.\n3. Write the body to a file with the Write tool, for example `\u002Ftmp\u002Freport-incident-body.md`.\n4. File the issue with the body file. Never pass the body inline: the shell truncates it at the first special character.\n\n```\ngh issue create -R Crpaxton4\u002Fdevcontainer-features --title \"\u003Ccomponent>: \u003Cproblem stated as a fact>\" --body-file \u003Cpath>\n```\n\n5. Give the user the issue URL that `gh` prints.\n",{"name":5,"description":7,"user-invocable":24},true,"main","043a283d6e259355cd1601e000c45e1ee8ebd8bd","plugins\u002Fodoo-orchestrator\u002Fskills\u002Freport-incident","https:\u002F\u002Fgithub.com\u002FCrpaxton4\u002Fdevcontainer-features","https:\u002F\u002Fgithub.com\u002FCrpaxton4","Computer Science\r\nMiami University","2026-11-02 22:38:24",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":24},[34,37,40],{"tool":35,"command":36},"npx","npx skills add Crpaxton4\u002Fdevcontainer-features --skill report-incident",{"tool":38,"command":39},"bunx","bunx skills add Crpaxton4\u002Fdevcontainer-features --skill report-incident",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Crpaxton4\u002Fdevcontainer-features --skill report-incident","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FCrpaxton4\u002Fdevcontainer-features\u002Fblob\u002Fmain\u002Fplugins\u002Fodoo-orchestrator\u002Fskills\u002Freport-incident\u002FSKILL.md",[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M75TQ2RBNTA4EXJ4BQ3HRYXY","principles","Engineering principles indexed as one-liners: safety and correctness, design and architecture, composition and interfaces, code structure, performance, visibility. Use when writing new code, reviewing a diff, or justifying a design choice.","https:\u002F\u002Fgithub.com\u002FCrpaxton4\u002Fdevcontainer-features\u002Fblob\u002Fmain\u002Fplugins\u002Fodoo-dev\u002Fskills\u002Fprinciples\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M75TQ0DVV793EWKKFN26408W","odoo-upgrade","Plan and run code upgrades of custom Odoo modules between major versions (16.0→17.0→18.0→19.0). Use to migrate or port a module or addon, for breaking changes, a module inventory, or an upgrade estimate or plan.","https:\u002F\u002Fgithub.com\u002FCrpaxton4\u002Fdevcontainer-features\u002Fblob\u002Fmain\u002Fplugins\u002Fodoo-dev\u002Fskills\u002Fodoo-upgrade\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M75TPXTR66V72DA42QSDQDPM","odoo-upgrade-project","Human SOP for a whole Odoo upgrade project past the code port: staging database upgrade through upgrade.odoo.com, on-prem restore, cutover, go-live, support tickets and functional requirements. A planning reference.","https:\u002F\u002Fgithub.com\u002FCrpaxton4\u002Fdevcontainer-features\u002Fblob\u002Fmain\u002Fplugins\u002Fodoo-dev\u002Fskills\u002Fodoo-upgrade-project\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M75TPVQ93TAY7KDB6XYDTVMK","odoo-test-run","Run an Odoo module's unit tests and HttpCase browser tours on a throwaway database and return machine-checkable evidence: tests executed, tours executed, failure lines. Use before a PR, after a fix, or when a green run never said how many tests ran.","https:\u002F\u002Fgithub.com\u002FCrpaxton4\u002Fdevcontainer-features\u002Fblob\u002Fmain\u002Fplugins\u002Fodoo-dev\u002Fskills\u002Fodoo-test-run\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M75TPR5N29G38HDSCKYEC350","odoo-task-env","Stand up the working environment for one Odoo task: find work that already exists, create or reuse an isolated git worktree on the task branch, bring a runnable stack up. Use at the START of implementing any task, and whenever one is picked back up.","https:\u002F\u002Fgithub.com\u002FCrpaxton4\u002Fdevcontainer-features\u002Fblob\u002Fmain\u002Fplugins\u002Fodoo-dev\u002Fskills\u002Fodoo-task-env\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M75TPMTYNCC7BC4THX46B4R4","odoo-session-db","Give one session its own throwaway test database name, so two sessions on one task in one project cannot land on the same database. Use before odoo-dev:odoo-test-run whenever more than one session can work in the same project, and when a test database vanished mid-run.","https:\u002F\u002Fgithub.com\u002FCrpaxton4\u002Fdevcontainer-features\u002Fblob\u002Fmain\u002Fplugins\u002Fodoo-dev\u002Fskills\u002Fodoo-session-db\u002FSKILL.md",[],[]]