@markus-global/cli 0.4.16 → 0.4.18

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (20) hide show
  1. package/dist/commands/start.js +36 -1
  2. package/dist/commands/start.js.map +1 -1
  3. package/dist/commands/task.js +4 -4
  4. package/dist/commands/task.js.map +1 -1
  5. package/dist/markus.mjs +1380 -10893
  6. package/dist/web-ui/assets/index-BWQnbwYf.css +1 -0
  7. package/dist/web-ui/assets/index-DKzBhzes.js +63 -0
  8. package/dist/web-ui/index.html +2 -2
  9. package/package.json +1 -1
  10. package/templates/roles/secretary/ROLE.md +16 -5
  11. package/templates/skills/agent-building/SKILL.md +3 -1
  12. package/templates/skills/markus-admin-cli/SKILL.md +2 -0
  13. package/templates/skills/markus-agent-cli/SKILL.md +2 -0
  14. package/templates/skills/markus-project-cli/SKILL.md +2 -0
  15. package/templates/skills/markus-skill-cli/SKILL.md +2 -0
  16. package/templates/skills/markus-team-cli/SKILL.md +2 -0
  17. package/templates/skills/skill-building/SKILL.md +3 -1
  18. package/templates/skills/team-building/SKILL.md +3 -1
  19. package/dist/web-ui/assets/index-CFSDM4KA.js +0 -63
  20. package/dist/web-ui/assets/index-Cy6aUDKr.css +0 -1
package/dist/web-ui/index.html CHANGED
@@ -11,8 +11,8 @@
11
11
  <script>
12
12
  (function(){var t=localStorage.getItem('markus-theme');if(t&&t!=='system')document.documentElement.classList.add(t)})();
13
13
  </script>
14
- <script type="module" crossorigin src="/assets/index-CFSDM4KA.js"></script>
15
- <link rel="stylesheet" crossorigin href="/assets/index-Cy6aUDKr.css">
14
+ <script type="module" crossorigin src="/assets/index-DKzBhzes.js"></script>
15
+ <link rel="stylesheet" crossorigin href="/assets/index-BWQnbwYf.css">
16
16
  </head>
17
17
  <body>
18
18
  <div id="root"></div>
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@markus-global/cli",
3
- "version": "0.4.16",
3
+ "version": "0.4.18",
4
4
  "description": "Markus — AI Digital Workforce Platform",
5
5
  "type": "module",
6
6
  "license": "AGPL-3.0-or-later",
package/templates/roles/secretary/ROLE.md CHANGED
@@ -35,18 +35,29 @@ You are a **protected system agent** — you cannot be deleted. You persist acro
35
35
 
36
36
  You are the primary builder and talent manager. You have building skills (agent-building, team-building, skill-building) and access to hiring/installation tools. **Hiring is a process, not a command** — creating the agent is step 1; onboarding is what makes them productive.
37
37
 
38
+ #### Team Creation Best Practices
39
+
40
+ When the owner asks to create a team, **always create the team first, then hire agents into it**. Never do it the other way around.
41
+
42
+ - **CORRECT approach**: Create team → Hire agents into that team → Onboard
43
+ - **WRONG approach**: Create agents first → Try to group them into a team later (or worse, leave them in the default team)
44
+ - **ALSO WRONG**: Just hire a bunch of agents without creating a dedicated team — this clutters the default team
45
+
46
+ The team is the organizational unit. Creating it first ensures agents are properly scoped, the team has a clear purpose, and the sidebar shows a clean structure for the owner.
47
+
38
48
  #### Hiring Workflow (the complete process)
39
49
 
40
50
  1. **Assess need**: Understand what role/skills are required. Check existing team (`team_list`, `team_status`) to avoid redundancy.
41
- 2. **Source the right agent**: Browse builtin templates (`team_list_templates`), search Markus Hub (`hub_search`), or design a custom agent using your building skills.
42
- 3. **Create**: `team_hire_agent` (from template), `hub_install` (from Hub), or building skill + `builder_install` (custom artifact).
43
- 4. **Onboard/Train** — Critical step:
51
+ 2. **Create the team first**: If the work belongs in a new team, create the team before hiring any agents. Use `team_create` or the team-building skill for more complex setups.
52
+ 3. **Source the right agents**: Browse builtin templates (`team_list_templates`), search Markus Hub (`hub_search`), or design custom agents using your building skills.
53
+ 4. **Hire into the team**: `team_hire_agent` (from template, specify the team), `hub_install` (from Hub), or building skill + `builder_install` (custom artifact). Always assign agents to the correct team.
54
+ 5. **Onboard/Train** — Critical step:
44
55
  - Send a welcome message (`agent_send_message`) with: who you are, team context, current project status, key conventions
45
56
  - Share relevant project info: active repositories, current requirements, coding standards
46
57
  - Point them to team norms and announcements
47
58
  - If the team has existing patterns or past decisions, share context from `memory_search`
48
- 5. **Assign initial work**: Create tasks (`task_create`) immediately so the new agent has concrete deliverables. Start with a well-scoped task to evaluate quality.
49
- 6. **Monitor early performance**: During subsequent heartbeats, pay attention to new hires — are they producing quality work? Do they need guidance? Correct early and record lessons.
59
+ 6. **Assign initial work**: Create tasks (`task_create`) immediately so the new agent has concrete deliverables. Start with a well-scoped task to evaluate quality.
60
+ 7. **Monitor early performance**: During subsequent heartbeats, pay attention to new hires — are they producing quality work? Do they need guidance? Correct early and record lessons.
50
61
 
51
62
  #### Custom Creation (using building skills)
52
63
 
package/templates/skills/agent-building/SKILL.md CHANGED
@@ -124,10 +124,12 @@ If an agent needs to be cautious with certain tools, write that into `POLICIES.m
124
124
 
125
125
  ## After Creation
126
126
 
127
+ > **CRITICAL**: Creating an artifact is NOT the same as installing/deploying it. Creating writes files to `builder-artifacts/`; installing deploys a live agent that consumes resources and joins the org. **NEVER auto-install.** Only install when the user explicitly says "install", "deploy", or "hire". This applies to ALL modes (chat, task, A2A).
128
+
127
129
  Once all files are written, tell the user:
128
130
 
129
131
  1. **The agent has been created and saved** — summarize what was created (name, purpose, key skills).
130
- 2. **Go to the Builder page** to manage the agent: install it to deploy, share it to Markus Hub, or delete it.
132
+ 2. **Ready to install** — the user can install from the Builder page, or ask you to install it (you would use `builder_install`). Do NOT install unless asked.
131
133
  3. **To modify or improve** this agent (e.g., update the role, change skills, adjust policies), just continue the conversation here — describe what you want to change and I'll update the files directly.
132
134
 
133
135
  ## Rules
package/templates/skills/markus-admin-cli/SKILL.md CHANGED
@@ -5,6 +5,8 @@ description: System administration via markus CLI — system controls, audit, us
5
5
 
6
6
  # System Administration via CLI
7
7
 
8
+ > **NOTE**: Most admin CLI commands have no built-in tool equivalent — CLI is the primary interface for system administration. Use `builder_install`/`builder_list` for artifact management when available.
9
+
8
10
  Administrative operations through `shell_execute` with `markus admin` commands. Always use `--json` for parseable output.
9
11
 
10
12
  ## System Controls
package/templates/skills/markus-agent-cli/SKILL.md CHANGED
@@ -5,6 +5,8 @@ description: Manage agents via markus CLI — lifecycle, messaging, config, memo
5
5
 
6
6
  # Agent Management via CLI
7
7
 
8
+ > **IMPORTANT**: Prefer built-in tools (`team_hire_agent`, `builder_install`, `agent_send_message`, `task_create`, `task_assign`, `memory_save`, etc.) over CLI commands. Only use CLI when no built-in tool provides the needed operation (e.g., `agent delete`, `agent config`, `agent role-sync`).
9
+
8
10
  Operate agents through `shell_execute` with `markus agent` commands. Always use `--json` for parseable output.
9
11
 
10
12
  ## Quick examples
package/templates/skills/markus-project-cli/SKILL.md CHANGED
@@ -5,6 +5,8 @@ description: Manage projects, tasks, requirements, deliverables, reports, review
5
5
 
6
6
  # Project & Task Management via CLI
7
7
 
8
+ > **IMPORTANT**: Prefer built-in tools (`task_create`, `task_update`, `task_list`, `task_assign`, `task_comment`, `requirement_propose`, `requirement_list`, `deliverable_create`, `deliverable_search`, etc.) over CLI commands. Only use CLI when no built-in tool provides the needed operation (e.g., `task approve`, `task revision`, `project create/delete`, `report generate`).
9
+
8
10
  Operate projects, tasks, requirements, deliverables, reports, reviews, and approvals through `shell_execute` with `markus` commands. Always use `--json` for parseable output.
9
11
 
10
12
  ## Projects
package/templates/skills/markus-skill-cli/SKILL.md CHANGED
@@ -5,6 +5,8 @@ description: Manage skills via markus CLI — list, install, uninstall, search,
5
5
 
6
6
  # Skill Management via CLI
7
7
 
8
+ > **IMPORTANT**: Prefer built-in tools (`discover_tools` for listing/activating/installing skills) over CLI commands. Only use CLI when no built-in tool provides the needed operation (e.g., `skill uninstall`, `skill init`).
9
+
8
10
  Operate the skill registry through `shell_execute` with `markus skill` commands. Always use `--json` for parseable output.
9
11
 
10
12
  ## Quick examples
package/templates/skills/markus-team-cli/SKILL.md CHANGED
@@ -5,6 +5,8 @@ description: Manage teams via markus CLI — create, members, lifecycle, export.
5
5
 
6
6
  # Team Management via CLI
7
7
 
8
+ > **IMPORTANT**: Prefer built-in tools (`team_hire_agent`, `builder_install`, `team_list`, `team_status`, `agent_send_message`, etc.) over CLI commands. Only use CLI when no built-in tool provides the needed operation (e.g., `team delete`, `team export`, `team pause/resume`).
9
+
8
10
  Operate teams through `shell_execute` with `markus team` commands. Always use `--json` for parseable output.
9
11
 
10
12
  ## Quick examples
package/templates/skills/skill-building/SKILL.md CHANGED
@@ -145,10 +145,12 @@ file_write("~/.markus/builder-artifacts/skills/git-changelog/README.md", "# Git
145
145
 
146
146
  ## After Creation
147
147
 
148
+ > **CRITICAL**: Creating an artifact is NOT the same as installing/deploying it. Creating writes files to `builder-artifacts/`; installing makes the skill available to agents in the live org. **NEVER auto-install.** Only install when the user explicitly asks. This applies to ALL modes (chat, task, A2A).
149
+
148
150
  Once all files are written, tell the user:
149
151
 
150
152
  1. **The skill has been created and saved** — summarize what was created (name, purpose, what agents can do with it).
151
- 2. **Go to the Builder page** to manage the skill: install it to make it available to agents, share it to Markus Hub, or delete it.
153
+ 2. **Ready to install** — the user can install from the Builder page, or ask you to install it (you would use `builder_install`). Do NOT install unless asked.
152
154
  3. **To modify or improve** this skill (e.g., add more instructions, update examples, fix edge cases), just continue the conversation here — describe what you want to change and I'll update the files directly.
153
155
 
154
156
  ## Guidelines
package/templates/skills/team-building/SKILL.md CHANGED
@@ -160,10 +160,12 @@ file_write("~/.markus/builder-artifacts/teams/research-team/members/senior-resea
160
160
 
161
161
  ## After Creation
162
162
 
163
+ > **CRITICAL**: Creating an artifact is NOT the same as installing/deploying it. Creating writes files to `builder-artifacts/`; installing deploys live agents that consume resources and join the org. **NEVER auto-install.** Only install when the user explicitly says "install", "deploy", or "hire". This applies to ALL modes (chat, task, A2A).
164
+
163
165
  Once all files are written, tell the user:
164
166
 
165
167
  1. **The team has been created and saved** — summarize the team composition (name, members, their roles).
166
- 2. **Go to the Builder page** to manage the team: install it to deploy all members, share it to Markus Hub, or delete it.
168
+ 2. **Ready to install** — the user can install from the Builder page, or ask you to install it (you would use `builder_install`). Do NOT install unless asked.
167
169
  3. **To modify or improve** this team (e.g., add new members, update roles, change team norms), just continue the conversation here — describe what you want to change and I'll update the files directly.
168
170
 
169
171
  ## Rules