@contextium/cli 1.0.18 → 1.0.20

package/skills/ium/new-project.legacy.md

@@ -0,0 +1,211 @@
+---
+name: ium:new-project-legacy
+description: Legacy new-project setup flow (deprecated; kept for reference)
+allowed-tools:
+  - Bash
+  - mcp__contextium__list_workspaces
+  - mcp__contextium__create_context_library
+  - mcp__contextium__list_context_libraries
+  - mcp__contextium__create_agent
+  - mcp__contextium__list_agents
+  - mcp__contextium__create_skill
+  - mcp__contextium__list_skills
+  - mcp__contextium__create_workflow
+  - mcp__contextium__list_workflows
+  - mcp__contextium__list_tags
+  - mcp__contextium__list_tag_types
+  - mcp__contextium__create_tag
+  - mcp__contextium__create_tag_type
+  - AskUserQuestion
+---
+
+<objective>
+Set up a new Contextium project intelligently — understand what the user is trying to do, quietly analyse the workspace for existing resources, then recommend exactly what to create (libraries, agents, skills, tags, workflow) with clear reasoning. Get confirmation before creating anything.
+</objective>
+
+<mode-detection>
+Run this once at the start, silently, to determine which mode to use for the entire session:
+
+```bash
+command -v contextium &>/dev/null && echo "cli" || echo "no-cli"
+```
+
+- If `cli`: use CLI commands throughout. Do not attempt MCP tools.
+- If `no-cli`: check if mcp__contextium__list_workspaces is available. If yes, use MCP tools throughout.
+- If neither: tell the user "Contextium doesn't appear to be installed. Install the CLI with `npm install -g @contextium/cli` or connect the MCP server, then re-run this." Stop here.
+
+Do not mention the mode to the user. Pick one path and stick with it.
+</mode-detection>
+
+<process>
+
+<step name="check_auth">
+**CLI only.** Run silently:
+```bash
+contextium whoami 2>/dev/null | grep -E "Token:|Name:" || echo "unauthenticated"
+```
+If token is expired or unauthenticated, tell the user: "Your Contextium session has expired — run `contextium login` in your terminal, then come back and re-run this." Stop here.
+
+MCP users are already authenticated via the server connection — skip this step.
+</step>
+
+<step name="select_workspace">
+**CLI:** run `contextium workspace list 2>/dev/null` silently, parse workspace names.
+**MCP:** call mcp__contextium__list_workspaces silently.
+
+Ask: "Which workspace is this project for?"
+
+Present names only — no IDs, no raw output.
+</step>
+
+<step name="project_description">
+Ask the user this question exactly:
+
+"Tell me about your project — what are you trying to do, what topics are involved, and what kind of work will you be doing with this? The more detail you give me, the better I can set things up for you."
+
+Wait for their response. Store it as the project description. Do not proceed until you have a meaningful answer.
+</step>
+
+<step name="quiet_analysis">
+Silently fetch all existing workspace resources. Do not show raw output or errors. Show only these progress lines as you go:
+
+```
+Searching libraries...
+Searching agents...
+Searching skills...
+Searching tags...
+```
+
+**CLI:**
+```bash
+contextium library list --workspace <slug> 2>/dev/null
+contextium agent list --workspace <slug> 2>/dev/null
+contextium skill list --workspace <slug> 2>/dev/null
+contextium tag list --workspace <slug> 2>/dev/null
+```
+
+**MCP:** call list_context_libraries, list_agents, list_skills, list_tags — all for the selected workspace. Suppress any errors silently.
+
+After all four searches complete, output this line:
+```
+Creating Contextium setup plan...
+```
+
+Then analyse the results against the project description:
+- Which existing libraries (if any) are relevant to what the user described?
+- Which existing agents (if any) could serve this project?
+- Which existing skills (if any) are applicable?
+- Which existing tags/tag types (if any) relate to the topics mentioned?
+
+Internally categorise everything as: **reuse** (relevant, already exists) or **create** (needed, does not exist).
+</step>
+
+<step name="intelligent_plan">
+Based on the project description and the analysis, build a setup plan. Think through:
+
+**Libraries:** What distinct knowledge areas did the user mention? Each major topic or type of content that needs to be stored separately should be its own library. If an existing library already covers one of these, mark it for reuse.
+
+**Agents:** What kind of AI assistant roles would serve this project? Think about what tasks the user will perform — research, writing, analysis, Q&A, etc. If an existing agent fits, mark it for reuse.
+
+**Skills:** What reusable knowledge blocks would help agents working on this project? Think about domain-specific guidelines, reference material, or persistent context the agent needs. If an existing skill fits, mark it for reuse.
+
+**Tags:** What topic or category labels would make sense for organising content in this project? Look for existing tag types that match. If none exist, suggest new ones. Think in terms of tag categories (e.g. `topic`, `source`, `status`) and the specific tag values within them (e.g. `topic:space-travel`, `topic:rocket-engineering`).
+
+**Workflow:** Propose one workflow name that bundles everything together for quick loading.
+
+Present the plan in this format (omit any section that has nothing in it):
+
+---
+
+Here's what I'll set up for you:
+
+**New libraries to create**
+- "Library Name" — reason why this is needed
+
+**Existing libraries to reuse**
+- "Library Name" — why it's relevant
+
+**New agents to create**
+- "Agent Name" — what it will do for this project
+
+**Existing agents to reuse**
+- "Agent Name" — why it fits
+
+**New skills to create**
+- "Skill Name" — what knowledge it will hold
+
+**Existing skills to reuse**
+- "Skill Name" — why it fits
+
+**Tags to create**
+- `category:value` — why this label is useful
+
+**Workflow**
+- "Workflow Name" — bundles everything above for quick loading
+
+Shall I go ahead and create all of this?
+
+---
+
+Wait for the user to confirm, adjust, or say skip on any item before proceeding.
+</step>
+
+<step name="create_resources">
+Only create what the user confirmed. Create in this order: tag types → tags → libraries → skills → agents → workflow.
+
+Show `✓ Created "Name"` for each item as it is created. Show `↗ Reusing "Name"` for each existing resource being included.
+
+Suppress all errors silently — if something fails, skip it quietly and note it in the summary.
+
+**CLI commands:**
+```bash
+contextium library create "<name>" --workspace <slug>
+contextium agent create "<name>" --workspace <slug>
+contextium skill create "<name>" --workspace <slug>
+contextium workflow create "<name>" --workspace <slug>
+contextium tag create "<value>" --type <type-slug> --workspace <slug>
+contextium tag-type create "<name>" --workspace <slug>
+```
+
+**MCP:** use the corresponding create_* tools for each resource type.
+</step>
+
+<step name="load_workflow">
+After all resources are created, automatically load the workflow without asking the user. Run silently:
+
+**CLI:** `contextium workflow load "<workflow-name>" --workspace <slug> 2>/dev/null`
+**MCP:** call mcp__contextium__load_workflow with the workflow name and workspace.
+
+Do not tell the user to load it themselves — just load it as part of setup.
+</step>
+
+<step name="summary">
+Show a clean final summary:
+
+```
+✓ Project ready
+
+Workspace:   <name>
+Libraries:   <list — new + reused>
+Agents:      <list — new + reused, or none>
+Skills:      <list — new + reused, or none>
+Tags:        <list, or none>
+Workflow:    <name> — loaded and ready
+```
+
+If anything failed to create, add a single line at the end:
+`⚠ Could not create: <list of names> — you can add these manually.`
+</step>
+
+</process>
+
+<rules>
+- Never say "the wizard", "Contextium would like to know", or "the next step is"
+- Never show raw bash output, API responses, or IDs to the user
+- Run all checks and fetches silently — only surface progress labels and the final plan
+- Only ask questions when genuinely needed — the description step and the confirmation step
+- Do not ask the user what to create — figure it out from the description, then ask them to confirm
+- If a resource already exists and is relevant, always prefer reuse over creating a duplicate
+- The plan report must explain the reasoning for each item — not just list names
+- Never create anything before the user confirms the plan
+</rules>

package/skills/ium/run.md

@@ -0,0 +1,32 @@
+---
+name: ium:run
+description: Run exact Contextium CLI commands non-interactively
+allowed-tools:
+  - Bash
+---
+
+<objective>
+Execute a user-provided `contextium` command exactly as written, with no interactive planning flow.
+</objective>
+
+<process>
+If the user provided command arguments, run silently:
+
+```bash
+contextium <user-args>
+```
+
+Then return only a concise result summary.
+
+If no args were provided, ask one short question:
+"What exact Contextium command should I run?"
+
+Do not propose workflows, plans, or alternatives unless the command fails.
+</process>
+
+<rules>
+- Default to non-interactive behavior.
+- Do not call slash commands from this command.
+- Do not ask follow-up questions unless required args are missing or command fails.
+- On failure, show the error and one concrete fix command.
+</rules>

package/skills/ium/search.md

@@ -10,17 +10,6 @@ Search across Contextium documentation and return matching files with their cont
 </objective>
 
 <process>
-**Step 1 — Check loaded context first**
-If a workflow session context block is active in this conversation, look there first. If the answer is found, respond from it without running any commands.
-
-**Step 2 — Ask before expanding scope**
-If the loaded context doesn't have what the user needs, ask:
-"That's not in the loaded workflow context. Would you like me to search the full workspace?"
-
-Only proceed to step 3 after the user confirms.
-
-**Step 3 — Search the full workspace**
-
 Run a search across the workspace:
 
 ```bash

package/skills/ium/workflow.md

@@ -19,32 +19,24 @@ Load a Contextium workflow and bring its resources into the current context. Onc
 
 Present workflow names only. Ask the user which one to load.
 
-2. Load the chosen workflow:
+2. Resolve the workspace BEFORE running any command:
+   - If `-w <workspace>` was given in the user's message, use it directly.
+   - Otherwise run: `contextium whoami 2>/dev/null` and extract the `workspace` field.
+   - If that returns nothing, ask the user: "Which workspace should I load this workflow from?"
+   - Do NOT proceed to step 3 until you have a workspace value.
 
-**CLI:** `contextium workflow "<workflow-name>" -w <workspace> --sync 2>/dev/null`
-**MCP:** call mcp__contextium__load_workflow
+3. Load the chosen workflow (workspace is now known):
 
-3. Output synced file content to context (CLI only):
-```bash
-contextium cat --all -w <workspace> 2>/dev/null
-```
+**CLI:** `contextium workflow "<workflow-name>" -w "<workspace>" 2>/dev/null`
+**MCP:** call mcp__contextium__load_workflow
 
-4. Persist the loaded workspace and workflow to `.contextiumrc` so it can be auto-restored after `/clear`:
+Note: `--sync` is optional and only needed if you want to cache files locally. Omit it by default.
 
+4. Output synced file content to context (CLI only):
 ```bash
-node -e "
-try {
-  const fs = require('fs');
-  const rc = JSON.parse(fs.readFileSync('.contextiumrc', 'utf8'));
-  rc.last_workflow = '<workflow-name>';
-  rc.last_workspace = '<workspace-slug-or-name>';
-  fs.writeFileSync('.contextiumrc', JSON.stringify(rc, null, 2));
-} catch(e) {}
-" 2>/dev/null
+contextium cat --all -w "<workspace>" 2>/dev/null
 ```
 
-Do this silently — never mention it to the user.
-
 5. Output a session context block in this exact format so all resource IDs and names are available for the rest of the session without re-querying:
 
 ```
@@ -67,7 +59,6 @@ Workflow loaded. What would you like to do?
 ```
 
 If a workflow name was specified directly in the user's message, skip step 1 and load immediately.
-If no workspace is specified, use the default from .contextiumrc or ask the user.
 </process>
 
 <session-rules>
@@ -78,13 +69,4 @@ Once the session context block has been output, these rules apply for the rest o
 - Do NOT re-verify or re-check which libraries, agents, or skills exist — they are already known
 - All tool calls and checks must be silent — never show the user raw API responses, tool call names, or intermediate results
 - Only surface the final answer or the created/updated content to the user
-
-**Scope rules — what is "available":**
-- When the user asks "what agents/skills/libraries do I have?" or "what's available?" — answer ONLY from the session context block above. Never call list_agents, list_skills, or list_context_libraries to answer this question.
-- If the user asks about something not in the session context, say so and ask if they want you to search the full workspace before doing so.
-
-**Search order:**
-1. Check the loaded session context first
-2. If not found there, say: "That's not in the loaded workflow. Would you like me to search the full workspace?"
-3. Only query the full workspace after the user confirms
 </session-rules>

package/skills/ium/workspace.md

@@ -13,28 +13,27 @@ Switch the active Contextium workspace with full context handoff — save what's
 <process>
 
 <step name="show_current">
-Silently fetch the current workspace and available workspaces:
+Show the current workspace and list available workspaces:
 
 ```bash
-cat .contextiumrc 2>/dev/null
-```
-
-**CLI:** `contextium workspaces 2>/dev/null`
-**MCP:** call mcp__contextium__list_workspaces
+# Show current workspace from .contextiumrc
+cat .contextiumrc 2>/dev/null | grep -E "workspace" | head -5 || echo "No .contextiumrc found"
 
-Parse the results internally — extract names and slugs only. Never show IDs, UUIDs, or raw command output to the user.
+# List all available workspaces
+contextium workspaces
+```
 
 Display clearly:
 ```
 Current workspace: <name>
 
 Available workspaces:
-1. Workspace A
-2. Workspace B
-3. Workspace C
+1. workspace-a
+2. workspace-b
+3. workspace-c
 ```
 
-Ask the user which workspace to switch to using AskUserQuestion with workspace **names only** as options — no IDs, no slugs. If the user already specified one in their message, skip this and use it directly.
+Ask the user which workspace to switch to using AskUserQuestion with the workspace names as options. If the user already specified one in their message, skip this and use it directly.
 </step>
 
 <step name="save_handoff">