[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MXDSCSH3YDQ33P1K3HWTQJ":3,"skill-same:01M6MXDSCSH3YDQ33P1K3HWTQJ":48},{"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":22,"linkOnly":23,"markdownContent":24,"markdownBody":25,"frontMatter":26,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":33,"install":34,"resources":47},"01M6MXDSCSH3YDQ33P1K3HWTQJ","deployment-executor",null,"OpenLogos deployment-executor 方法论 Skill","miniidealab\u002Fopenlogos","miniidealab","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F4251156?v=4","01M6MX6BM454XESZCRPBQQHKRT","FredHuang","01M6MX6BR4417H4QA658D4GW9X",581,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fminiidealab\u002Fopenlogos\u002Fblob\u002Fmaster\u002Flogos\u002Fchanges\u002Farchive\u002F20260829-2333-release-0-14-1-local\u002Fdeployment-artifacts-20260830T0554Z\u002Fcandidate-unpack\u002Fpackage\u002Fqoder-plugin-template\u002Fskills\u002Fdeployment-executor\u002FSKILL.md",[],[19,20,21],"deployment","executor","deployment executor","2026-11-10 10:12:30",false,"---\nname: \"deployment-executor\"\ndescription: \"OpenLogos deployment-executor 方法论 Skill\"\n---\n# Skill: Deployment Executor\n\n> 在 `openlogos verify` 通过后，按已合并的部署方案执行经人类明确确认的部署任务，并引导运行 `openlogos smoke`。该 Skill 只在部署执行阶段使用。\n\n## 触发条件\n\n- 用户明确要求执行部署\n- 用户说“按部署方案部署”“执行当前提案的部署任务”“部署到 staging \u002F production”\n- 当前提案 `tasks.md` 存在 `[deploy]` section\n- Initial 阶段 verify 通过后需要部署到目标环境\n\n## 前置依赖\n\n1. 用户明确授权部署\n2. `logos\u002Fresources\u002Fprd\u002F3-technical-plan\u002F3-deployment\u002F` 中存在部署方案\n3. 当前提案已 `VERIFY_PASS`\n4. 当前提案 `tasks.md` 中存在 `[deploy]` section\n5. 部署所需命令、环境变量和回滚策略已在部署方案中声明\n\n如果任一条件不满足，停止并说明缺少哪一项。\n\n## 部署授权来源（change-flow-redesign）\n\n> 插入到「前置依赖」之后。本节修订「前置依赖」第 1 条与「禁止行为」第 1 条对\"部署必须用户明确授权 \u002F 禁止自动部署\"的绝对表述，明确在无人值守模式下的**受限授权来源**。\n\n部署执行的授权可来自以下两者之一：\n\n1. **默认 \u002F 手动模式（半自动）**：用户明确授权部署（前置依赖原义；生产环境强烈建议走此路径）。半自动下部署执行、`openlogos smoke` 等仍逐次须人类明确授权，行为**完全不变**。\n2. **无人值守 `openlogos next --auto` 模式（全自动 \u002F standing 授权）**：`--auto` 的含义被重定义为一次性的 **standing run-scoped 授权**——用户选择 `--auto` 即在本次运行域内一次性授权全链路自动到底。本次 `next --auto` 响应对 deliver 入口门（`deliver-entry`，`skippable:true`）输出 **`gate_auto_passed === true`** 时，即构成对**本次**部署的放行依据（部署目标可能是测试环境而非生产）。\n\n全自动 `--auto` 下，同一 standing 授权也覆盖\"代码已绿后的盖章 \u002F 发布\"动作：部署完成后的 `openlogos smoke`、以及更下游的 `git push`（`plugin\u002Fbin\u002Fguard-check` 的安全白名单本就放行 `git push`，**无需任何 marker \u002F guard 改动**，全自动下纯由指令文本授权）均可经此授权自动执行，无需逐次人类再确认；可跳门每次放行向 `GATE_AUTO_PASSED` 追加一行审计。\n\n受限约束（必须遵守）：\n- 授权依据是**本次 `--auto` 响应的 `gate_auto_passed === true`**这一 live 决策，**不是** `GATE_AUTO_PASSED` 文件的存在；**历史审计行不构成对后续部署 \u002F smoke \u002F push 的授权**（与默认 `next` 忽略 `GATE_AUTO_PASSED` 一致）。\n- 仍须满足其它前置依赖（`VERIFY_PASS`、部署方案、`[deploy]` section、部署决策无冲突）。\n- 仍禁止：跳过部署方案凭经验执行、部署失败后写 `DEPLOY_DONE`、手写 `DEPLOY_DONE`、**跳过需要的 smoke**（全自动只是把 smoke 的\"授权\"前置到用户选择 `--auto`，并不允许略过 smoke 本身）。\n- **硬红线不受 `--auto` 影响**：代码未收敛 \u002F 未绿（`gate:implement:loop-exhausted`）在任何模式下都绝不自动放行，自动放行只发生在\"代码已绿\"之后。\n- 部署完成后仍调用 `openlogos deploy-done` 受控落标，不手写 marker。\n\n> 据此，「前置依赖」第 1 条「用户明确授权部署」在 `--auto` 下由「本次响应 `gate_auto_passed=true`」满足；「禁止行为」第 1 条「未经用户明确确认自动部署」的\"明确确认\"在 `--auto` 下等价于用户选择 `--auto` + 本次放行，而非凭 AI 自行决定。\n\n## 核心能力\n\n1. 读取部署方案和当前提案部署任务\n2. 将部署任务拆解为可执行步骤\n3. 在关键命令前说明目的、影响环境和回滚点\n4. 执行部署命令并记录结果\n5. 生成部署报告\n6. 写入部署完成标记\n7. 引导用户运行 `openlogos smoke`\n\n## 执行步骤\n\n### Step 1: 确认授权\n\n部署是人类确认点。必须看到用户明确表达，例如：\n\n- `执行部署`\n- `部署到 staging`\n- `按部署方案部署`\n\n不能因为用户说“继续”“按流程走完”而自动部署。\n\n### Step 2: 读取部署上下文\n\n必须读取：\n\n- `logos\u002Fresources\u002Fprd\u002F3-technical-plan\u002F3-deployment\u002F*.md`\n- 当前提案 `proposal.md`\n- 当前提案 `tasks.md` 的 `[deploy]` section\n- 已合并后的相关主规格\n\n### Step 3: 执行前检查\n\n检查：\n\n- 当前是否 `VERIFY_PASS`\n- 是否存在未完成代码任务\n- 部署目标环境是否明确\n- 回滚策略是否可执行\n- 必要环境变量和密钥是否已由用户确认\n- smoke 测试命令是否配置或已有替代说明\n\n### Step 4: 执行部署\n\n按部署方案逐项执行。\n\n每个关键命令前必须说明：\n\n- 命令目的\n- 影响环境\n- 失败后的中止或回滚方式\n\n不得执行部署方案中没有定义的命令。\n\n### Step 5: 生成部署报告\n\n写入：\n\n`logos\u002Fresources\u002Fverify\u002Fdeployment-report.md`\n\n报告包含：\n\n- 部署时间\n- 目标环境\n- 执行命令摘要\n- 迁移结果\n- 服务启动结果\n- 回滚点\n- 未解决风险\n\n### Step 6: 写入部署完成标记\n\n部署成功后：\n\n- 确认 `logos\u002Fresources\u002Fverify\u002Fdeployment-report.md` 已写入并记录目标环境、执行命令摘要、回滚点和未解决风险\n- 执行受控命令写入部署完成状态：\n\n```bash\nopenlogos deploy-done\n```\n\n如有目标环境：\n\n```bash\nopenlogos deploy-done --env staging\n```\n\n`openlogos deploy-done` 负责：\n\n- 勾选当前提案 `tasks.md` 中的 `[deploy]` 任务\n- 写入 `logos\u002Fchanges\u002F\u003Cslug>\u002FDEPLOY_DONE`\n- 清理过期的 `SMOKE_PASS` \u002F `SMOKE_FAIL`\n- 输出下一步 smoke 或 archive 建议\n\n部署失败时：\n\n- 不得执行 `openlogos deploy-done`\n- 不得手写 `DEPLOY_DONE`\n- 输出失败点和回滚建议\n- 以 `logos\u002Fresources\u002Fverify\u002Fdeployment-report.md` 记录失败摘要\n\n### Step 7: 引导 smoke\n\n部署完成后提示用户明确授权运行：\n\n```bash\nopenlogos smoke\n```\n\n如有目标环境：\n\n```bash\nopenlogos smoke --env staging\n```\n\n**半自动 \u002F 手动模式**：AI 不得自动运行 `openlogos smoke`，除非用户明确授权。\n\n**全自动 `openlogos next --auto` 模式**：`smoke` 属\"代码已绿后的盖章\"动作，由用户选择 `--auto` 的 standing 授权覆盖，可经编排器凭本次 `next --auto` 响应的 `gate_auto_passed=true` 自动执行（放行时写 `GATE_AUTO_PASSED` 审计），无需逐次人类再确认；唯部署 \u002F 代码本身未绿时不在此列。\n\n## 禁止行为\n\n- 未经用户明确确认自动部署\n- 跳过部署方案，凭经验执行命令\n- 自动执行涉及生产、远程服务器、密钥、发布、域名或数据迁移的命令\n- 部署失败后执行 `openlogos deploy-done`\n- 手写 `logos\u002Fchanges\u002F\u003Cslug>\u002FDEPLOY_DONE` 作为推荐路径\n- 部署后直接 archive，跳过需要的 `openlogos smoke`\n\n## 推荐提示词\n\n- `按部署方案部署到 staging`\n- `执行当前提案的部署任务`\n- `部署完成后帮我准备 smoke 命令`\n","# Skill: Deployment Executor\n\n> 在 `openlogos verify` 通过后，按已合并的部署方案执行经人类明确确认的部署任务，并引导运行 `openlogos smoke`。该 Skill 只在部署执行阶段使用。\n\n## 触发条件\n\n- 用户明确要求执行部署\n- 用户说“按部署方案部署”“执行当前提案的部署任务”“部署到 staging \u002F production”\n- 当前提案 `tasks.md` 存在 `[deploy]` section\n- Initial 阶段 verify 通过后需要部署到目标环境\n\n## 前置依赖\n\n1. 用户明确授权部署\n2. `logos\u002Fresources\u002Fprd\u002F3-technical-plan\u002F3-deployment\u002F` 中存在部署方案\n3. 当前提案已 `VERIFY_PASS`\n4. 当前提案 `tasks.md` 中存在 `[deploy]` section\n5. 部署所需命令、环境变量和回滚策略已在部署方案中声明\n\n如果任一条件不满足，停止并说明缺少哪一项。\n\n## 部署授权来源（change-flow-redesign）\n\n> 插入到「前置依赖」之后。本节修订「前置依赖」第 1 条与「禁止行为」第 1 条对\"部署必须用户明确授权 \u002F 禁止自动部署\"的绝对表述，明确在无人值守模式下的**受限授权来源**。\n\n部署执行的授权可来自以下两者之一：\n\n1. **默认 \u002F 手动模式（半自动）**：用户明确授权部署（前置依赖原义；生产环境强烈建议走此路径）。半自动下部署执行、`openlogos smoke` 等仍逐次须人类明确授权，行为**完全不变**。\n2. **无人值守 `openlogos next --auto` 模式（全自动 \u002F standing 授权）**：`--auto` 的含义被重定义为一次性的 **standing run-scoped 授权**——用户选择 `--auto` 即在本次运行域内一次性授权全链路自动到底。本次 `next --auto` 响应对 deliver 入口门（`deliver-entry`，`skippable:true`）输出 **`gate_auto_passed === true`** 时，即构成对**本次**部署的放行依据（部署目标可能是测试环境而非生产）。\n\n全自动 `--auto` 下，同一 standing 授权也覆盖\"代码已绿后的盖章 \u002F 发布\"动作：部署完成后的 `openlogos smoke`、以及更下游的 `git push`（`plugin\u002Fbin\u002Fguard-check` 的安全白名单本就放行 `git push`，**无需任何 marker \u002F guard 改动**，全自动下纯由指令文本授权）均可经此授权自动执行，无需逐次人类再确认；可跳门每次放行向 `GATE_AUTO_PASSED` 追加一行审计。\n\n受限约束（必须遵守）：\n- 授权依据是**本次 `--auto` 响应的 `gate_auto_passed === true`**这一 live 决策，**不是** `GATE_AUTO_PASSED` 文件的存在；**历史审计行不构成对后续部署 \u002F smoke \u002F push 的授权**（与默认 `next` 忽略 `GATE_AUTO_PASSED` 一致）。\n- 仍须满足其它前置依赖（`VERIFY_PASS`、部署方案、`[deploy]` section、部署决策无冲突）。\n- 仍禁止：跳过部署方案凭经验执行、部署失败后写 `DEPLOY_DONE`、手写 `DEPLOY_DONE`、**跳过需要的 smoke**（全自动只是把 smoke 的\"授权\"前置到用户选择 `--auto`，并不允许略过 smoke 本身）。\n- **硬红线不受 `--auto` 影响**：代码未收敛 \u002F 未绿（`gate:implement:loop-exhausted`）在任何模式下都绝不自动放行，自动放行只发生在\"代码已绿\"之后。\n- 部署完成后仍调用 `openlogos deploy-done` 受控落标，不手写 marker。\n\n> 据此，「前置依赖」第 1 条「用户明确授权部署」在 `--auto` 下由「本次响应 `gate_auto_passed=true`」满足；「禁止行为」第 1 条「未经用户明确确认自动部署」的\"明确确认\"在 `--auto` 下等价于用户选择 `--auto` + 本次放行，而非凭 AI 自行决定。\n\n## 核心能力\n\n1. 读取部署方案和当前提案部署任务\n2. 将部署任务拆解为可执行步骤\n3. 在关键命令前说明目的、影响环境和回滚点\n4. 执行部署命令并记录结果\n5. 生成部署报告\n6. 写入部署完成标记\n7. 引导用户运行 `openlogos smoke`\n\n## 执行步骤\n\n### Step 1: 确认授权\n\n部署是人类确认点。必须看到用户明确表达，例如：\n\n- `执行部署`\n- `部署到 staging`\n- `按部署方案部署`\n\n不能因为用户说“继续”“按流程走完”而自动部署。\n\n### Step 2: 读取部署上下文\n\n必须读取：\n\n- `logos\u002Fresources\u002Fprd\u002F3-technical-plan\u002F3-deployment\u002F*.md`\n- 当前提案 `proposal.md`\n- 当前提案 `tasks.md` 的 `[deploy]` section\n- 已合并后的相关主规格\n\n### Step 3: 执行前检查\n\n检查：\n\n- 当前是否 `VERIFY_PASS`\n- 是否存在未完成代码任务\n- 部署目标环境是否明确\n- 回滚策略是否可执行\n- 必要环境变量和密钥是否已由用户确认\n- smoke 测试命令是否配置或已有替代说明\n\n### Step 4: 执行部署\n\n按部署方案逐项执行。\n\n每个关键命令前必须说明：\n\n- 命令目的\n- 影响环境\n- 失败后的中止或回滚方式\n\n不得执行部署方案中没有定义的命令。\n\n### Step 5: 生成部署报告\n\n写入：\n\n`logos\u002Fresources\u002Fverify\u002Fdeployment-report.md`\n\n报告包含：\n\n- 部署时间\n- 目标环境\n- 执行命令摘要\n- 迁移结果\n- 服务启动结果\n- 回滚点\n- 未解决风险\n\n### Step 6: 写入部署完成标记\n\n部署成功后：\n\n- 确认 `logos\u002Fresources\u002Fverify\u002Fdeployment-report.md` 已写入并记录目标环境、执行命令摘要、回滚点和未解决风险\n- 执行受控命令写入部署完成状态：\n\n```bash\nopenlogos deploy-done\n```\n\n如有目标环境：\n\n```bash\nopenlogos deploy-done --env staging\n```\n\n`openlogos deploy-done` 负责：\n\n- 勾选当前提案 `tasks.md` 中的 `[deploy]` 任务\n- 写入 `logos\u002Fchanges\u002F\u003Cslug>\u002FDEPLOY_DONE`\n- 清理过期的 `SMOKE_PASS` \u002F `SMOKE_FAIL`\n- 输出下一步 smoke 或 archive 建议\n\n部署失败时：\n\n- 不得执行 `openlogos deploy-done`\n- 不得手写 `DEPLOY_DONE`\n- 输出失败点和回滚建议\n- 以 `logos\u002Fresources\u002Fverify\u002Fdeployment-report.md` 记录失败摘要\n\n### Step 7: 引导 smoke\n\n部署完成后提示用户明确授权运行：\n\n```bash\nopenlogos smoke\n```\n\n如有目标环境：\n\n```bash\nopenlogos smoke --env staging\n```\n\n**半自动 \u002F 手动模式**：AI 不得自动运行 `openlogos smoke`，除非用户明确授权。\n\n**全自动 `openlogos next --auto` 模式**：`smoke` 属\"代码已绿后的盖章\"动作，由用户选择 `--auto` 的 standing 授权覆盖，可经编排器凭本次 `next --auto` 响应的 `gate_auto_passed=true` 自动执行（放行时写 `GATE_AUTO_PASSED` 审计），无需逐次人类再确认；唯部署 \u002F 代码本身未绿时不在此列。\n\n## 禁止行为\n\n- 未经用户明确确认自动部署\n- 跳过部署方案，凭经验执行命令\n- 自动执行涉及生产、远程服务器、密钥、发布、域名或数据迁移的命令\n- 部署失败后执行 `openlogos deploy-done`\n- 手写 `logos\u002Fchanges\u002F\u003Cslug>\u002FDEPLOY_DONE` 作为推荐路径\n- 部署后直接 archive，跳过需要的 `openlogos smoke`\n\n## 推荐提示词\n\n- `按部署方案部署到 staging`\n- `执行当前提案的部署任务`\n- `部署完成后帮我准备 smoke 命令`\n",{"name":5,"description":7},"master","abf55fdedadaeb660f928aa7258b9ec35d4ab003","logos\u002Fchanges\u002Farchive\u002F20260829-2333-release-0-14-1-local\u002Fdeployment-artifacts-20260830T0554Z\u002Fcandidate-unpack\u002Fpackage\u002Fqoder-plugin-template\u002Fskills\u002Fdeployment-executor",10,"https:\u002F\u002Fgithub.com\u002Fminiidealab\u002Fopenlogos","https:\u002F\u002Fgithub.com\u002Fminiidealab","2026-10-18 11:36:11",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add miniidealab\u002Fopenlogos --skill deployment-executor",{"tool":40,"command":41},"bunx","bunx skills add miniidealab\u002Fopenlogos --skill deployment-executor",{"tool":43,"command":44},"pnpm","pnpm dlx skills add miniidealab\u002Fopenlogos --skill deployment-executor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fminiidealab\u002Fopenlogos\u002Fblob\u002Fmaster\u002Flogos\u002Fchanges\u002Farchive\u002F20260829-2333-release-0-14-1-local\u002Fdeployment-artifacts-20260830T0554Z\u002Fcandidate-unpack\u002Fpackage\u002Fqoder-plugin-template\u002Fskills\u002Fdeployment-executor\u002FSKILL.md",true,[],[49,95,107,116,124,133],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":74,"publishedAt":22},"01M6MXX45142DGRFD9ZYPT5YC9","ui-ux-pro-max","UI\u002FUX design intelligence. 67 styles, 96 palettes, 57 font pairings, 25 charts, 13 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn\u002Fui). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI\u002FUX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient. Integrations: shadcn\u002Fui MCP for component search and examples.","https:\u002F\u002Fgithub.com\u002Fminiidealab\u002Fopenlogos\u002Fblob\u002Fmaster\u002Fskills\u002Fui-ux-pro-max\u002FSKILL.md",[55,60,63,66,71],{"categoryNo":56,"categoryName":57,"taxonomyType":58,"taxonomyTypeDesc":59},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",{"categoryNo":61,"categoryName":62,"taxonomyType":58,"taxonomyTypeDesc":59},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":64,"categoryName":65,"taxonomyType":58,"taxonomyTypeDesc":59},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":67,"categoryName":68,"taxonomyType":69,"taxonomyTypeDesc":70},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",{"categoryNo":72,"categoryName":73,"taxonomyType":69,"taxonomyTypeDesc":70},"01JBSEEDCAT000000000000033","数据分析师",[75,76,77,78,79,80,81,82,83,84,85,86,87,88,89,90,91,92,93,94],"ui ux","pro","max","ui ux pro max","ui","ux","projects","mode","card","app","tsx","fix","improve","Tailwind","Charts","Animation","design","actions","MCP","search",{"skillNo":96,"name":97,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":103,"publishedAt":22},"01M6MXWY8HJV93BBR8FPNJXAMV","test-writer","https:\u002F\u002Fgithub.com\u002Fminiidealab\u002Fopenlogos\u002Fblob\u002Fmaster\u002Fskills\u002Ftest-writer\u002FSKILL.md",[100],{"categoryNo":101,"categoryName":102,"taxonomyType":58,"taxonomyTypeDesc":59},"01JBSEEDCAT000000000000008","测试与质量",[104,105,106],"writer","test writer","test",{"skillNo":108,"name":109,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":113,"publishedAt":22},"01M6MXWSAMN9AD3T8F6N099ZGY","test-orchestrator","https:\u002F\u002Fgithub.com\u002Fminiidealab\u002Fopenlogos\u002Fblob\u002Fmaster\u002Fskills\u002Ftest-orchestrator\u002FSKILL.md",[112],{"categoryNo":101,"categoryName":102,"taxonomyType":58,"taxonomyTypeDesc":59},[114,115,106],"orchestrator","test orchestrator",{"skillNo":117,"name":118,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":22},"01M6MXWN29FY7K9ASMFRSPWQCN","slice-planner","https:\u002F\u002Fgithub.com\u002Fminiidealab\u002Fopenlogos\u002Fblob\u002Fmaster\u002Fskills\u002Fslice-planner\u002FSKILL.md",[],[122,123],"slice planner","planner",{"skillNo":125,"name":126,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":22},"01M6MXWFR1C1V66NSRTAM1FZPR","scenario-architect","https:\u002F\u002Fgithub.com\u002Fminiidealab\u002Fopenlogos\u002Fblob\u002Fmaster\u002Fskills\u002Fscenario-architect\u002FSKILL.md",[],[130,131,132],"architect","scenario","scenario architect",{"skillNo":134,"name":135,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":138,"publishedAt":22},"01M6MXWD6ZCGPT4FDT580S8K96","project-init","https:\u002F\u002Fgithub.com\u002Fminiidealab\u002Fopenlogos\u002Fblob\u002Fmaster\u002Fskills\u002Fproject-init\u002FSKILL.md",[],[139,140,141],"project init","init","project"]