@contextium/cli 1.0.5 → 1.0.6

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@contextium/cli",
-  "version": "1.0.5",
+  "version": "1.0.6",
   "description": "Command-line tool for managing Contextium documentation, agents, skills, and workflows — pipe context to AI coding assistants",
   "keywords": [
     "contextium",

package/skills/ium/workflow.md

@@ -3,28 +3,63 @@ name: ium:workflow
 description: Load a Contextium workflow and sync its resources into context — bundles agents, skills, and libraries for a project
 allowed-tools:
   - Bash
+  - mcp__contextium__load_workflow
+  - mcp__contextium__list_workflows
 ---
 
 <objective>
-Load a Contextium workflow and bring its resources into the current context. Workflows bundle agents, skills, and context libraries together for a specific project.
+Load a Contextium workflow and bring its resources into the current context. Once loaded, output a structured session context block so Claude never needs to re-list or re-check workspace resources during this session.
 </objective>
 
 <process>
-1. List available workflows so the user can pick one:
+1. If no workflow name was specified, list available workflows so the user can pick one. Do this silently — do not show raw output:
+
+**CLI:** `contextium workflows list -w <workspace> 2>/dev/null`
+**MCP:** call mcp__contextium__list_workflows
+
+Present workflow names only. Ask the user which one to load.
+
+2. Load the chosen workflow:
+
+**CLI:** `contextium workflow "<workflow-name>" -w <workspace> --sync 2>/dev/null`
+**MCP:** call mcp__contextium__load_workflow
+
+3. Output synced file content to context (CLI only):
 ```bash
-contextium workflows list -w <workspace>
+contextium cat --all -w <workspace> 2>/dev/null
 ```
 
-2. Load the chosen workflow and sync its files:
-```bash
-contextium workflow "<workflow-name>" -w <workspace> --sync
+4. 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:
+
 ```
+--- WORKFLOW SESSION CONTEXT ---
+Workflow:   <name>
+Workspace:  <name> (id: <id>)
 
-3. Output the synced content to context:
-```bash
-contextium cat --all -w <workspace>
+Libraries:
+  - "<name>" (id: <id>)
+  - "<name>" (id: <id>)
+
+Agents:
+  - "<name>" (id: <id>)
+
+Skills:
+  - "<name>" (id: <id>)
+--- END SESSION CONTEXT ---
+
+Workflow loaded. What would you like to do?
 ```
 
-If the user specifies a workflow name directly in their message, skip step 1 and load it immediately.
+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>
+Once the session context block has been output, these rules apply for the rest of the conversation:
+
+- Do NOT call list_workflows, list_context_libraries, list_agents, list_skills, list_files, or any other listing tool again unless the user explicitly asks to see a list
+- Use the IDs from the session context block directly when creating files, searching, or referencing resources
+- 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
+</session-rules>