[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73H4FVSSSVR8MPQ2ERZAS3A":3,"skill-same:01M73H4FVSSSVR8MPQ2ERZAS3A":59},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":37,"commitSha":38,"skillDirectory":39,"forksCount":40,"repositoryHtmlUrl":41,"repositoryHomepageUrl":6,"ownerHtmlUrl":42,"ownerBlogUrl":6,"ownerDescription":43,"updatedAt":44,"install":45,"resources":58},"01M73H4FVSSSVR8MPQ2ERZAS3A","team-builder",null,"Guides the Engagement Leader through building a new AI agent team for any consulting domain. Covers requirements interview, web benchmarking, current team diagnosis, proposal generation, and user approval gate. Outputs an approved proposal JSON for scripts\u002Fteam-builder.ts to execute. Triggered by: \"build new agent team\".","5throck\u002Fai-workspace-standards","5throck","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F10958964?v=4","01M73BFEH0V0VS483TW4JD49JW","01M73BFEJ5VQZJHJSFTVPAZGDM",25,"AGPL-3.0","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fcommon\u002F.gemini\u002Fskills\u002Fteam-builder\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: team-builder\ndescription: >\n  Guides the Engagement Leader through building a new AI agent team for any consulting domain.\n  Covers requirements interview, web benchmarking, current team diagnosis, proposal generation,\n  and user approval gate. Outputs an approved proposal JSON for scripts\u002Fteam-builder.ts to execute.\n  Triggered by: \"build new agent team\".\nversion: 1.2.0\nstatus: active\nscope: common\nowner: pm\nprerequisites: none\nlast_reviewed: 2026-11-08\nmetadata:\n  type: process\n  triggers:\n    - build new agent team\n    - create agent team\n    - agent team setup\n    - team builder\n---\n\n## Overview\n\nTwo-layer architecture:\n- **Skill Layer (Steps 1–5)**: AI-driven. Requirements interview, benchmarking, current team diagnosis, proposal generation, user approval gate.\n- **Script Layer (Steps 6–14)**: Executed by `scripts\u002Fteam-builder.ts` after user approves the proposal JSON.\n\nNever proceed to script execution without explicit user approval at Step 5.\n\n---\n\n## Step 1: Requirements Interview\n\nConduct a structured interview with the user. Collect all of the following before proceeding:\n\n| Question | Purpose |\n|----------|---------|\n| What is the primary domain\u002Fpurpose of the new team? | Scope benchmarking |\n| What types of projects will this team handle? | Team structure reference |\n| Expected team scale (number of agents)? | Budget\u002Ftier planning |\n| Required expertise areas? | Specialist identification |\n| Are there existing agents to retain, convert, or delete? | Change scope |\n| What quality\u002Fdelivery standards must the team meet? | Workflow design criteria |\n\nDo not proceed to Step 2 until all six questions are answered. Summarize requirements back to the user for confirmation before moving on.\n\n---\n\n## Step 2: Benchmarking\n\nUse web search tools to research industry-standard team structures matching the user's requirements.\n\n**Benchmarking quality criteria:**\n- Use at least 2 authoritative sources (McKinsey, BCG, Gartner, Forrester, industry associations, or peer-reviewed research)\n- For each reference team structure, document: team name\u002Fsource, roles and responsibilities, hierarchy, typical project types, known strengths\u002Fweaknesses\n- Evaluate fit against user requirements using a scoring matrix (1–5 per criterion)\n\n**Source validation checklist (verify each before citing):**\n1. Publication date within 5 years of current date\n2. Official organizational domain (e.g., mckinsey.com, gartner.com) or peer-reviewed journal with DOI\n3. Primary source preferred — if only a secondary citation is available, note the original source explicitly\n\n**Benchmarking deliverable format:**\n```\nReference Team A — [Source]\n  Roles: [list]\n  Hierarchy: [structure]\n  Fit score: [X\u002F5 per criterion]\n  Typical skills required: [list]\n\nReference Team B — [Source]\n  ...\n```\n\nSelect the best-fit reference (highest total score) and document the rationale.\n\n---\n\n## Step 3: Current Team State Diagnosis\n\nBefore proposing any changes, map the current team state by reading existing agent and skill files.\n\n1. **Agent inventory**: List all `agents\u002F*.md` files — name, formal_name, tier, phases, required_skills, status\n2. **Skill inventory**: List all `skills\u002F*\u002FSKILL.md` files — name, owner, status, prerequisites\n3. **Dependency map**: For each agent to be deleted or converted, identify:\n   - Skills it owns\n   - Agents it hands off to \u002F receives from\n   - Phases it participates in\n4. **Proactive skill transfer plan**: Before any deletion, assign each skill to a valid remaining or new agent\n\n---\n\n## Step 4: Proposal Generation\n\nGenerate a structured proposal document covering all planned changes.\n\n**Proposal must include:**\n\n### 4a. Team Comparison Table\n| | Current | Proposed | Change Type |\n|--|---------|----------|-------------|\n| Agent Name | existing role | new role | Create \u002F Convert \u002F Delete \u002F Keep |\n\n### 4b. Agent Change Details\nFor each change:\n- **Create**: name, formal_name, tier, phases, required_skills, rationale (linked to benchmarking)\n- **Convert**: current file → new file name, role changes, skills retained vs. replaced\n- **Delete**: agent name, skills to be transferred (with new owner), rationale\n\n### 4c. Skill Change Plan\n- Existing skills to reuse (unchanged)\n- Existing skills to modify (what changes and why)\n- New skills to create (name, owner, rationale)\n- Skill owner reassignments (from deleted\u002Fconverted agents)\n\n### 4d. Workflow Design\n- Phase definitions for the new team\n- Agent dispatch order\n- Handoff chain (handoff_to \u002F handoff_from per agent)\n\n### 4e. Benchmarking Evidence\n- Source(s) used, fit score, key rationale for team structure choices\n\n### 4f. Change History Entry\n- One-paragraph summary for `memory\u002FYYYY-MM-DD.md`\n\n---\n\n## Step 5: User Approval Gate ⛔ MANDATORY STOP\n\nPresent the full proposal to the user. Display:\n\n```\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\nTEAM BUILDER — PROPOSAL READY FOR REVIEW\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n[Display full proposal from Step 4]\n\nAgents to CREATE : N\nAgents to CONVERT: N\nAgents to DELETE : N\nSkills to CREATE : N\nSkills to REASSIGN: N\n\nTo execute: reply \"approve\"\nTo revise:  reply with specific change requests\nTo cancel:  reply \"cancel\"\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n```\n\n**DO NOT proceed to script execution until the user explicitly approves.**\n\nOn approval:\n1. Save proposal as `memory\u002Fteam-builder-proposal-YYYY-MM-DD.json` (JSON format matching the TeamBuilderProposal schema in scripts\u002Fteam-builder.ts)\n2. Instruct the user to run: `bun scripts\u002Fteam-builder.ts memory\u002Fteam-builder-proposal-YYYY-MM-DD.json`\n3. Do NOT run the script directly. Always wait for the user to execute the command above explicitly.\n\n---\n\n## Proposal JSON Schema\n\nThe saved JSON must conform to this structure:\n\n```json\n{\n  \"version\": \"1.0.0\",\n  \"timestamp\": \"YYYY-MM-DDTHH:mm:ssZ\",\n  \"teamName\": \"string\",\n  \"benchmarkSources\": [\"url or citation\"],\n  \"changes\": {\n    \"agentsToCreate\": [\n      {\n        \"name\": \"kebab-case-name\",\n        \"formalName\": \"Display Name\",\n        \"tier\": \"high|medium|low\",\n        \"color\": \"color-name\",\n        \"description\": \"one-line description\",\n        \"phases\": [\"1\", \"2\"],\n        \"handoffTo\": [\"agent-name\"],\n        \"handoffFrom\": [\"agent-name\"],\n        \"requiredSkills\": [\"skill-name\"],\n        \"rationale\": \"why this agent\"\n      }\n    ],\n    \"agentsToConvert\": [\n      {\n        \"currentFile\": \"current-name.md\",\n        \"newFile\": \"new-name.md\",\n        \"newFormalName\": \"New Display Name\",\n        \"roleChanges\": \"description of what changes\",\n        \"skillsRetained\": [\"skill-name\"],\n        \"skillsReplaced\": [\"old-skill -> new-skill\"]\n      }\n    ],\n    \"agentsToDelete\": [\n      {\n        \"name\": \"agent-name\",\n        \"skillsToTransfer\": [{ \"skill\": \"skill-name\", \"newOwner\": \"agent-name\" }],\n        \"rationale\": \"why deleting\"\n      }\n    ],\n    \"skillsToCreate\": [\n      {\n        \"name\": \"skill-name\",\n        \"owner\": \"agent-name\",\n        \"description\": \"description\",\n        \"prerequisites\": [\"skill-name\"]\n      }\n    ],\n    \"skillsToModify\": [\n      {\n        \"name\": \"skill-name\",\n        \"changes\": \"what to change\"\n      }\n    ],\n    \"skillsToReassign\": [\n      {\n        \"skill\": \"skill-name\",\n        \"fromOwner\": \"old-agent\",\n        \"toOwner\": \"new-agent\"\n      }\n    ],\n    \"workflowPhases\": [\n      {\n        \"phase\": 0,\n        \"name\": \"Phase Name\",\n        \"lead\": \"agent-name\",\n        \"supporting\": [\"agent-name\"]\n      }\n    ]\n  },\n  \"changeHistoryEntry\": \"one-paragraph summary\",\n  \"approvedBy\": \"user\",\n  \"approvedAt\": \"YYYY-MM-DDTHH:mm:ssZ\"\n}\n```\n\n---\n\n## Output Format\n\n- **Step 1**: Requirements summary table (confirmed by user)\n- **Step 2**: Benchmarking report with fit matrix\n- **Step 3**: Current team inventory + dependency map + proactive skill transfer plan\n- **Step 4**: Full proposal document (human-readable)\n- **Step 5**: Approval prompt + proposal JSON saved to `memory\u002F`\n\n---\n\n## Related Skills\n\n- `agent-lifecycle-manager` — for individual agent lifecycle operations\n- `skill-lifecycle-manager` — for individual skill lifecycle operations\n- `insight-synthesis` — for synthesizing benchmarking findings\n- `org-readiness-assessment` — if organizational readiness context is needed\n","## Overview\n\nTwo-layer architecture:\n- **Skill Layer (Steps 1–5)**: AI-driven. Requirements interview, benchmarking, current team diagnosis, proposal generation, user approval gate.\n- **Script Layer (Steps 6–14)**: Executed by `scripts\u002Fteam-builder.ts` after user approves the proposal JSON.\n\nNever proceed to script execution without explicit user approval at Step 5.\n\n---\n\n## Step 1: Requirements Interview\n\nConduct a structured interview with the user. Collect all of the following before proceeding:\n\n| Question | Purpose |\n|----------|---------|\n| What is the primary domain\u002Fpurpose of the new team? | Scope benchmarking |\n| What types of projects will this team handle? | Team structure reference |\n| Expected team scale (number of agents)? | Budget\u002Ftier planning |\n| Required expertise areas? | Specialist identification |\n| Are there existing agents to retain, convert, or delete? | Change scope |\n| What quality\u002Fdelivery standards must the team meet? | Workflow design criteria |\n\nDo not proceed to Step 2 until all six questions are answered. Summarize requirements back to the user for confirmation before moving on.\n\n---\n\n## Step 2: Benchmarking\n\nUse web search tools to research industry-standard team structures matching the user's requirements.\n\n**Benchmarking quality criteria:**\n- Use at least 2 authoritative sources (McKinsey, BCG, Gartner, Forrester, industry associations, or peer-reviewed research)\n- For each reference team structure, document: team name\u002Fsource, roles and responsibilities, hierarchy, typical project types, known strengths\u002Fweaknesses\n- Evaluate fit against user requirements using a scoring matrix (1–5 per criterion)\n\n**Source validation checklist (verify each before citing):**\n1. Publication date within 5 years of current date\n2. Official organizational domain (e.g., mckinsey.com, gartner.com) or peer-reviewed journal with DOI\n3. Primary source preferred — if only a secondary citation is available, note the original source explicitly\n\n**Benchmarking deliverable format:**\n```\nReference Team A — [Source]\n  Roles: [list]\n  Hierarchy: [structure]\n  Fit score: [X\u002F5 per criterion]\n  Typical skills required: [list]\n\nReference Team B — [Source]\n  ...\n```\n\nSelect the best-fit reference (highest total score) and document the rationale.\n\n---\n\n## Step 3: Current Team State Diagnosis\n\nBefore proposing any changes, map the current team state by reading existing agent and skill files.\n\n1. **Agent inventory**: List all `agents\u002F*.md` files — name, formal_name, tier, phases, required_skills, status\n2. **Skill inventory**: List all `skills\u002F*\u002FSKILL.md` files — name, owner, status, prerequisites\n3. **Dependency map**: For each agent to be deleted or converted, identify:\n   - Skills it owns\n   - Agents it hands off to \u002F receives from\n   - Phases it participates in\n4. **Proactive skill transfer plan**: Before any deletion, assign each skill to a valid remaining or new agent\n\n---\n\n## Step 4: Proposal Generation\n\nGenerate a structured proposal document covering all planned changes.\n\n**Proposal must include:**\n\n### 4a. Team Comparison Table\n| | Current | Proposed | Change Type |\n|--|---------|----------|-------------|\n| Agent Name | existing role | new role | Create \u002F Convert \u002F Delete \u002F Keep |\n\n### 4b. Agent Change Details\nFor each change:\n- **Create**: name, formal_name, tier, phases, required_skills, rationale (linked to benchmarking)\n- **Convert**: current file → new file name, role changes, skills retained vs. replaced\n- **Delete**: agent name, skills to be transferred (with new owner), rationale\n\n### 4c. Skill Change Plan\n- Existing skills to reuse (unchanged)\n- Existing skills to modify (what changes and why)\n- New skills to create (name, owner, rationale)\n- Skill owner reassignments (from deleted\u002Fconverted agents)\n\n### 4d. Workflow Design\n- Phase definitions for the new team\n- Agent dispatch order\n- Handoff chain (handoff_to \u002F handoff_from per agent)\n\n### 4e. Benchmarking Evidence\n- Source(s) used, fit score, key rationale for team structure choices\n\n### 4f. Change History Entry\n- One-paragraph summary for `memory\u002FYYYY-MM-DD.md`\n\n---\n\n## Step 5: User Approval Gate ⛔ MANDATORY STOP\n\nPresent the full proposal to the user. Display:\n\n```\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\nTEAM BUILDER — PROPOSAL READY FOR REVIEW\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n[Display full proposal from Step 4]\n\nAgents to CREATE : N\nAgents to CONVERT: N\nAgents to DELETE : N\nSkills to CREATE : N\nSkills to REASSIGN: N\n\nTo execute: reply \"approve\"\nTo revise:  reply with specific change requests\nTo cancel:  reply \"cancel\"\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n```\n\n**DO NOT proceed to script execution until the user explicitly approves.**\n\nOn approval:\n1. Save proposal as `memory\u002Fteam-builder-proposal-YYYY-MM-DD.json` (JSON format matching the TeamBuilderProposal schema in scripts\u002Fteam-builder.ts)\n2. Instruct the user to run: `bun scripts\u002Fteam-builder.ts memory\u002Fteam-builder-proposal-YYYY-MM-DD.json`\n3. Do NOT run the script directly. Always wait for the user to execute the command above explicitly.\n\n---\n\n## Proposal JSON Schema\n\nThe saved JSON must conform to this structure:\n\n```json\n{\n  \"version\": \"1.0.0\",\n  \"timestamp\": \"YYYY-MM-DDTHH:mm:ssZ\",\n  \"teamName\": \"string\",\n  \"benchmarkSources\": [\"url or citation\"],\n  \"changes\": {\n    \"agentsToCreate\": [\n      {\n        \"name\": \"kebab-case-name\",\n        \"formalName\": \"Display Name\",\n        \"tier\": \"high|medium|low\",\n        \"color\": \"color-name\",\n        \"description\": \"one-line description\",\n        \"phases\": [\"1\", \"2\"],\n        \"handoffTo\": [\"agent-name\"],\n        \"handoffFrom\": [\"agent-name\"],\n        \"requiredSkills\": [\"skill-name\"],\n        \"rationale\": \"why this agent\"\n      }\n    ],\n    \"agentsToConvert\": [\n      {\n        \"currentFile\": \"current-name.md\",\n        \"newFile\": \"new-name.md\",\n        \"newFormalName\": \"New Display Name\",\n        \"roleChanges\": \"description of what changes\",\n        \"skillsRetained\": [\"skill-name\"],\n        \"skillsReplaced\": [\"old-skill -> new-skill\"]\n      }\n    ],\n    \"agentsToDelete\": [\n      {\n        \"name\": \"agent-name\",\n        \"skillsToTransfer\": [{ \"skill\": \"skill-name\", \"newOwner\": \"agent-name\" }],\n        \"rationale\": \"why deleting\"\n      }\n    ],\n    \"skillsToCreate\": [\n      {\n        \"name\": \"skill-name\",\n        \"owner\": \"agent-name\",\n        \"description\": \"description\",\n        \"prerequisites\": [\"skill-name\"]\n      }\n    ],\n    \"skillsToModify\": [\n      {\n        \"name\": \"skill-name\",\n        \"changes\": \"what to change\"\n      }\n    ],\n    \"skillsToReassign\": [\n      {\n        \"skill\": \"skill-name\",\n        \"fromOwner\": \"old-agent\",\n        \"toOwner\": \"new-agent\"\n      }\n    ],\n    \"workflowPhases\": [\n      {\n        \"phase\": 0,\n        \"name\": \"Phase Name\",\n        \"lead\": \"agent-name\",\n        \"supporting\": [\"agent-name\"]\n      }\n    ]\n  },\n  \"changeHistoryEntry\": \"one-paragraph summary\",\n  \"approvedBy\": \"user\",\n  \"approvedAt\": \"YYYY-MM-DDTHH:mm:ssZ\"\n}\n```\n\n---\n\n## Output Format\n\n- **Step 1**: Requirements summary table (confirmed by user)\n- **Step 2**: Benchmarking report with fit matrix\n- **Step 3**: Current team inventory + dependency map + proactive skill transfer plan\n- **Step 4**: Full proposal document (human-readable)\n- **Step 5**: Approval prompt + proposal JSON saved to `memory\u002F`\n\n---\n\n## Related Skills\n\n- `agent-lifecycle-manager` — for individual agent lifecycle operations\n- `skill-lifecycle-manager` — for individual skill lifecycle operations\n- `insight-synthesis` — for synthesizing benchmarking findings\n- `org-readiness-assessment` — if organizational readiness context is needed\n",{"name":5,"owner":23,"scope":24,"status":25,"version":26,"metadata":27,"description":34,"last_reviewed":35,"prerequisites":36},"pm","common","active","1.2.0",{"type":28,"triggers":29},"process",[30,31,32,33],"build new agent team","create agent team","agent team setup","team builder","Guides the Engagement Leader through building a new AI agent team for any consulting domain. Covers requirements interview, web benchmarking, current team diagnosis, proposal generation, and user approval gate. Outputs an approved proposal JSON for scripts\u002Fteam-builder.ts to execute. Triggered by: \"build new agent team\".\n",1794096000000,"none","main","1162ccc568cf90c01b3886d6143cbfd851a37883","templates\u002Fcommon\u002F.gemini\u002Fskills\u002Fteam-builder",9,"https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards","https:\u002F\u002Fgithub.com\u002F5throck","Experienced in digital transformation, enterprise IT, startup acceleration, and business strategy. Focused on building practical systems that connect technolo","2026-11-14 21:22:34",{"source":8,"skillName":5,"commands":46,"prompt":56,"zipAvailable":57},[47,50,53],{"tool":48,"command":49},"npx","npx skills add 5throck\u002Fai-workspace-standards --skill team-builder",{"tool":51,"command":52},"bunx","bunx skills add 5throck\u002Fai-workspace-standards --skill team-builder",{"tool":54,"command":55},"pnpm","pnpm dlx skills add 5throck\u002Fai-workspace-standards --skill team-builder","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fcommon\u002F.gemini\u002Fskills\u002Fteam-builder\u002FSKILL.md",true,[],[60,68,73,78,83,88],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":67},"01M7BBJDYHJMGTJYSC37JVWY8S","i18n-layout","Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL\u002Fbidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF\u002FBOM issues surface.","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":69,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":67},"01M7BBJ9XHAAS1AVGKZZ841VBZ","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.hermes\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":74,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":67},"01M7BBJ5C3X8TKFKG5R9P9P49W","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.gemini\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":79,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":67},"01M7BBJ1B52X0QMJ2QVBMPJB37","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.codex\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":84,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":67},"01M7BBHX91BW2Q2R276MRX5AW3","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.claude\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":89,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":67},"01M7BBHQWGXPSFRWN1PRC2NMMV","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.agents\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[]]