Sign In

@contextium/cli

Package Overview
Dependencies
Maintainers
2
Versions
108
Alerts
File Explorer

Advanced tools

License
Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@contextium/cli - npm Package Compare versions

Comparing version
1.0.7
 to
1.0.8
+1
-1
package.json
{
"name": "@contextium/cli",
"version": "1.0.7",
"version": "1.0.8",
"description": "Command-line tool for managing Contextium documentation, agents, skills, and workflows — pipe context to AI coding assistants",

@@ -5,0 +5,0 @@ "keywords": [

+29
-0
skills/ium/contextium.md

@@ -52,4 +52,33 @@ ---

## File Routing — Writing Files When Contextium Is Connected
When the Contextium MCP is connected or the CLI is active, **any time a new file is about to be created**, intercept it with a routing question before writing:
> "Should this file go to a Contextium context library, or stay local?"
**If a workflow is loaded in this session:**
- Default to suggesting the most relevant library from the session context block
- Offer: `[1] Write to "<library name>" in Contextium [2] Keep local`
- If the user picks Contextium, use `mcp__contextium__create_file` or `contextium files create` CLI with the library ID from session context — do NOT write it locally
**If no workflow is loaded but the MCP/CLI is active:**
- Ask: "Should this go to Contextium? If yes, which library?"
- List available libraries only if the user says yes
- Otherwise write locally as normal
**Files that should NEVER be routed to Contextium — always write locally:**
- Rich text formats: `.docx`, `.doc`, `.pdf`, `.rtf`, `.odt`, `.pages`, `.pptx`, `.xlsx`, and any binary or formatted document
- Source code files (`.ts`, `.tsx`, `.js`, `.py`, etc.)
- Config files (`package.json`, `.env`, `tsconfig.json`, etc.)
- Git-tracked project files in general
**Files that SHOULD be offered for Contextium routing (plain text / non-rich text only):**
- Plain markdown (`.md`) that is NOT part of the project source (e.g. not `README.md`, `CLAUDE.md`)
- Plain text (`.txt`), YAML (`.yaml`/`.yml`), or JSON files used as documentation or notes
- Any plain-text file the user explicitly describes as "context", "reference", or "docs"
This rule applies to both the `Write` tool and any CLI `echo`/`cat` file creation.
## Silent Operation
All MCP tool calls and CLI commands must be silent — never show the user raw API responses, tool output, or intermediate results. Only surface the final answer.