@markus-global/cli 0.5.0 → 0.5.2

package/templates/skills/markus-cli/skill.json

@@ -7,6 +7,12 @@
   "author": "markus",
   "category": "platform",
   "tags": ["cli", "platform", "management", "api"],
+  "i18n": {
+    "zh-CN": {
+      "displayName": "Markus 命令行",
+      "description": "通过 CLI 命令操作 Markus 平台的核心知识，是所有 markus-*-cli 技能的前置依赖。"
+    }
+  },
   "skill": {
     "skillFile": "SKILL.md",
     "alwaysOn": false

package/templates/skills/markus-hub-connector/skill.json

@@ -7,6 +7,12 @@
   "author": "markus",
   "category": "productivity",
   "tags": ["hub", "marketplace", "community", "share"],
+  "i18n": {
+    "zh-CN": {
+      "displayName": "Markus Hub 连接器",
+      "description": "在 Markus Hub 社区市场上搜索、下载和发布智能体/团队/技能"
+    }
+  },
   "skill": {
     "skillFile": "SKILL.md",
     "requiredPermissions": ["network"],

package/templates/skills/markus-project-cli/skill.json

@@ -7,6 +7,13 @@
   "author": "markus",
   "category": "platform",
   "tags": ["cli", "projects", "requirements", "deliverables", "reports"],
+  "hidden": true,
+  "i18n": {
+    "zh-CN": {
+      "displayName": "Markus 项目命令行",
+      "description": "通过 markus CLI 管理项目、需求、交付物、报告和代码审查。"
+    }
+  },
   "skill": {
     "skillFile": "SKILL.md",
     "alwaysOn": false

package/templates/skills/markus-skill-cli/skill.json

@@ -7,6 +7,13 @@
   "author": "markus",
   "category": "platform",
   "tags": ["cli", "skills", "registry"],
+  "hidden": true,
+  "i18n": {
+    "zh-CN": {
+      "displayName": "Markus 技能命令行",
+      "description": "通过 markus CLI 管理技能 — 列出、安装、卸载、搜索、脚手架。"
+    }
+  },
   "skill": {
     "skillFile": "SKILL.md",
     "alwaysOn": false

package/templates/skills/markus-team-cli/skill.json

@@ -7,6 +7,13 @@
   "author": "markus",
   "category": "platform",
   "tags": ["cli", "teams", "management"],
+  "hidden": true,
+  "i18n": {
+    "zh-CN": {
+      "displayName": "Markus 团队命令行",
+      "description": "通过 markus CLI 管理团队 — 创建、成员管理、生命周期、导出。"
+    }
+  },
   "skill": {
     "skillFile": "SKILL.md",
     "alwaysOn": false

package/templates/skills/self-evolution/skill.json

@@ -7,6 +7,12 @@
   "author": "markus",
   "category": "productivity",
   "tags": ["learning", "reflection", "memory", "self-improvement", "evolution"],
+  "i18n": {
+    "zh-CN": {
+      "displayName": "自我进化",
+      "description": "从经验中学习 — 捕获教训、演进 SOP、分享最佳实践技能，并逐步优化自身角色"
+    }
+  },
   "skill": {
     "skillFile": "SKILL.md",
     "alwaysOn": true

package/templates/skills/skill-building/skill.json

@@ -7,6 +7,12 @@
   "author": "markus",
   "category": "development",
   "tags": ["builder", "skill", "design", "manifest", "mcp"],
+  "i18n": {
+    "zh-CN": {
+      "displayName": "技能构建",
+      "description": "设计和创建智能体技能包 — 基于指令和基于 MCP 的技能、清单格式和 Markus 技能工件目录结构"
+    }
+  },
   "skill": {
     "skillFile": "SKILL.md"
   }

package/templates/skills/team-building/SKILL.md

@@ -18,6 +18,7 @@ This skill teaches you how to create Markus team packages — self-contained dir
 ```
 ~/.markus/builder-artifacts/teams/{team-name}/
 ├── team.json                    # Manifest (auto-created from your JSON output)
+├── README.md                    # Public-facing team overview for Hub/Builder (REQUIRED)
 ├── ANNOUNCEMENT.md              # Team announcement (you write via file_write)
 ├── NORMS.md                     # Working norms (you write via file_write)
 └── members/
@@ -106,16 +107,22 @@ After the JSON is saved, write each file individually using `file_write`. The ba
 
 **Write files in this order:**
 
-1. **ANNOUNCEMENT.md** — Team mission, member introduction, how the team works, key capabilities. At least 3 paragraphs.
+1. **README.md** (REQUIRED) — The public-facing overview displayed on Markus Hub and the Builder detail page. This is what users see first when browsing the team. Write 2-4 paragraphs covering:
+   - What this team does and what problem it solves
+   - Team composition overview (who the key members are)
+   - Key capabilities and workflow highlights
+   - Example use cases or when to deploy this team
 
-2. **NORMS.md** — Phase-based workflow documentation aligned with `team.workflow.phases`. This is critical for team effectiveness. Structure it as:
+2. **ANNOUNCEMENT.md** — Team mission, member introduction, how the team works, key capabilities. At least 3 paragraphs.
+
+3. **NORMS.md** — Phase-based workflow documentation aligned with `team.workflow.phases`. This is critical for team effectiveness. Structure it as:
    - A section for each workflow phase (e.g., "### 1. Plan", "### 2. Implement", "### 3. Review & Merge")
    - Each phase explains what happens, who is responsible, and which platform capabilities to use
    - Include file/module ownership rules if the team does parallel development
    - Include communication protocols (when to use `agent_send_message`, `agent_broadcast_status`)
    - Reference platform capabilities: `spawn_subagent`, `background_exec`, `shell_execute` (git/gh), worktree isolation, `deliverable_create`, etc.
 
-3. **Each member's ROLE.md** — Write one at a time. **Before writing, read the existing base role template** via `file_read` to understand the expected depth and conventions. Each ROLE.md should be at least 5 paragraphs, covering:
+4. **Each member's ROLE.md** — Write one at a time. **Before writing, read the existing base role template** via `file_read` to understand the expected depth and conventions. Each ROLE.md should be at least 5 paragraphs, covering:
    - Who this agent is (identity, personality)
    - Core expertise and responsibilities
    - **Workflow with platform capabilities** — when to use `spawn_subagent`, `background_exec`, `shell_execute`, etc.
@@ -125,20 +132,21 @@ After the JSON is saved, write each file individually using `file_write`. The ba
    - For reviewers: review-then-merge workflow (git merge or gh pr)
    - For managers: file ownership planning, dependency graphs, `spawn_subagent` for analysis
 
-4. **Each member's HEARTBEAT.md** (RECOMMENDED) — Defines what the agent proactively checks every ~30 minutes. Without this file, the agent is purely reactive and will only respond to direct messages. Write a role-specific checklist covering:
+5. **Each member's HEARTBEAT.md** (RECOMMENDED) — Defines what the agent proactively checks every ~30 minutes. Without this file, the agent is purely reactive and will only respond to direct messages. Write a role-specific checklist covering:
    - Check mailbox for new messages and respond to urgent items
    - Review assigned tasks — update progress, unblock if possible
    - Check team announcements and norms for updates
    - Role-specific patrol items (e.g., managers: check team task board and unblock members; developers: check build status and PR reviews; reviewers: check tasks awaiting review)
    - Scan recent channel messages for anything requiring attention
 
-5. **POLICIES.md** (optional) — For members that need specific constraints.
+6. **POLICIES.md** (optional) — For members that need specific constraints.
 
-6. **CONTEXT.md** (optional) — Additional domain context, references, or knowledge specific to a member.
+7. **CONTEXT.md** (optional) — Additional domain context, references, or knowledge specific to a member.
 
 **Example file_write calls:**
 
 ```
+file_write("~/.markus/builder-artifacts/teams/research-team/README.md", "# Research Team\n\nA collaborative AI research team that...\n\n## Team Composition\n- Research Director (manager)...\n- Senior Researcher (worker)...\n\n## Use Cases\n- Academic literature review and synthesis...")
 file_write("~/.markus/builder-artifacts/teams/research-team/ANNOUNCEMENT.md", "# Research Team — Team Announcement\n\n...")
 file_write("~/.markus/builder-artifacts/teams/research-team/NORMS.md", "# Research Team — Working Norms\n\n...")
 file_write("~/.markus/builder-artifacts/teams/research-team/members/research-director/ROLE.md", "# Research Director\n\nYou are **Research Director** — ...\n\n...")

package/templates/skills/team-building/skill.json

@@ -7,6 +7,12 @@
   "author": "markus",
   "category": "development",
   "tags": ["builder", "team", "design", "manifest"],
+  "i18n": {
+    "zh-CN": {
+      "displayName": "团队构建",
+      "description": "设计和创建 AI 团队包 — 清单格式、成员结构、目录布局和 Markus 团队工件部署"
+    }
+  },
   "skill": {
     "skillFile": "SKILL.md"
   }

package/templates/teams/content-team/team.json

@@ -8,6 +8,18 @@
   "category": "productivity",
   "tags": ["content", "writing", "marketing", "documentation", "creative", "editorial"],
   "icon": "edit",
+  "i18n": {
+    "zh-CN": {
+      "displayName": "内容创作团队",
+      "description": "以研究驱动的内容团队，具有结构化的流水线：调研 → 简报 → 草稿 → 编辑 → 发布。支持并行写作、事实核查和编辑审核。适用于文档项目、营销活动、技术写作和内容运营。",
+      "members": {
+        "Editor-in-Chief": "主编",
+        "Senior Writer": "高级作者",
+        "Technical Writer": "技术文档工程师",
+        "Research Analyst": "研究分析师"
+      }
+    }
+  },
   "team": {
     "members": [
       {

package/templates/teams/dev-squad/team.json

@@ -8,6 +8,19 @@
   "category": "development",
   "tags": ["development", "agile", "sprint", "feature", "software", "tdd", "code-review"],
   "icon": "users",
+  "i18n": {
+    "zh-CN": {
+      "displayName": "开发小队",
+      "description": "高效能开发团队，遵循计划 → 实现 → 审查 → 验证的工作流。支持并行实现、两阶段审查（代码 + QA）、依赖感知的任务调度。适用于功能冲刺、重构和生产级软件交付。",
+      "members": {
+        "Tech Lead": "技术负责人",
+        "Backend Developer": "后端开发",
+        "Frontend Developer": "前端开发",
+        "Code Reviewer": "代码审查员",
+        "QA Engineer": "QA 工程师"
+      }
+    }
+  },
   "team": {
     "members": [
       {

package/templates/teams/engineering-pod/team.json

@@ -8,6 +8,19 @@
   "category": "development",
   "tags": ["engineering", "full-stack", "architecture", "devops", "deployment", "multi-layer"],
   "icon": "server",
+  "i18n": {
+    "zh-CN": {
+      "displayName": "工程小组",
+      "description": "全功能工程团队，由架构师设计、多位开发者跨层并行实现（后端、前端、基础设施），配备专职审查员和 DevOps 工程师。适用于需要跨层协调、API 契约和生产部署的复杂多层项目。",
+      "members": {
+        "Architect": "架构师",
+        "Backend Engineer": "后端工程师",
+        "Frontend Engineer": "前端工程师",
+        "Infra Engineer": "基础设施工程师",
+        "Senior Reviewer": "高级审查员"
+      }
+    }
+  },
   "team": {
     "members": [
       {

package/templates/teams/research-lab/team.json

@@ -8,6 +8,18 @@
   "category": "research",
   "tags": ["research", "investigation", "debugging", "analysis", "competing-hypotheses", "audit"],
   "icon": "search",
+  "i18n": {
+    "zh-CN": {
+      "displayName": "研究实验室",
+      "description": "结构化研究团队，用于调查复杂问题：通过竞争性假设进行调试、技术评估、安全审计和深度分析。多位研究员并行探索不同角度，相互质疑发现，由综合分析师产出高质量交付物。",
+      "members": {
+        "Research Lead": "研究负责人",
+        "Researcher Alpha": "研究员 Alpha",
+        "Researcher Beta": "研究员 Beta",
+        "Synthesizer": "综合分析师"
+      }
+    }
+  },
   "team": {
     "members": [
       {

package/templates/teams/startup-team/team.json

@@ -8,6 +8,17 @@
   "category": "startup",
   "tags": ["startup", "lean", "mvp", "product", "growth", "iteration", "agile"],
   "icon": "zap",
+  "i18n": {
+    "zh-CN": {
+      "displayName": "创业全能团队",
+      "description": "精益创业团队，注重速度。产品经理驱动策略，全栈开发快速交付功能，增长负责人处理营销和数据分析。适用于 MVP 开发、快速迭代和增长实验。",
+      "members": {
+        "Product Manager": "产品经理",
+        "Full-Stack Developer": "全栈开发",
+        "Growth Lead": "增长负责人"
+      }
+    }
+  },
   "team": {
     "members": [
       {